Issues with G27

I'm having an issue with my Logitech G27 whereby while the calibration software shows the pedals and wheel functioning properly (shifter doesn't appear in calibration software), the pedals and steering wheel function in Next Car Game but not BeamNG, and the shifter doesn't function whatsoever, although the buttons on the shifter work in Next Car Game (I don't use them in BeamNG, so I didn't check).

Using the app in BeamNG to see how the game sees the pedals, it sees the third bar from the left as always fully depressed (unless I use the arrow keys, then it returns to zero), and the other pedals as never depressed.

Less than a month ago, my shifter stopped finding gears correctly, but I resolved that by just opening it up, cleaning it a little bit (although, the potentiometers weren't noticeably dirty) and putting it back together. I tried doing the same thing with the pedals but that didn't work. I may get some canned air if not also acetone to do some real cleaning if you guys think that would help.

EDIT: Sort of got pedals working. Seems as though something wiped my bindings in BeamNG. Pedals are sticking at 50% when not pressed, but the clutch pedal isn't being detected in the game at all. I bound the top-left and top-right red buttons on the wheel to the respective turn signals, but hitting any three left buttons or any three right buttons seems to point to the top-left and top-right binding. The shifter doesn't seem to work either still. The game doesn't see any of the "buttons" being pressed when I go into gear.

 

I am having this same issue. Currently trying to diagnose it, but the menu with the control options does show most of the things functioning how they should, but the car does nothing. Would really like to see if this can get fixed.

 

I don't know about you, but for me I can't seem to name an event that could have caused it, because I came back from a week of working out-of-state, and my problems just appeared. I had played in the game just fine in 5.6.1 before, so I am not under the impression that it is on BeamNG's end, but I am not sure what could be the cause here.

 

Actually I had similar issue, and I checked profiler and it looked like my PC recognized G25 as DFGT without a real reason, so probably Win10 auto update messed something. Then I just deleted profiler, installed newest one and everything started to work as before.