mattgw86 Posted 15 hours ago Posted 15 hours ago I’m having a bizarre issue with my rudder pedals (rhino ffb modded crosswinds). When I first start DCS, everything works fine, whether I’m in the F18, F14, A10, or F4. After some amount of time, I haven’t figured out if it’s linked to time, changing mission, or changing module, the rudder pedals stop responding in the jet. They still move normally on the Adjust Controls screen, but no response in game. what’s strange is if I load a helicopter mission, the pedals work perfectly fine and never cut out. If I go back to a jet mission, no rudders. Back to a helicopter, pedals work fine. things I’ve tried- unplugging and plugging in the pedals, unplugging the VPForce controller and binding the MFG pedals (the crosswinds are normally plugged in either way for the brake axis, but the rudder axis is not bound). Also, the brake axis never cuts out. The issue also persists after I exit DCS and open it back. At this point, I’ve all but ruled out a hardware issue since the controls menu and the configurator show accurate movement. It also wouldn’t make sense for it to be hardware related since the pedals work in helicopters, but not jets. has anyone else seen an issue like this? I’m stumped…
Number481 Posted 15 minutes ago Posted 15 minutes ago (edited) 15 hours ago, mattgw86 said: I’m having a bizarre issue with my rudder pedals (rhino ffb modded crosswinds)..... This will have nothing to do with the game or bindings. Try disabling the pedal trim feature in TelemFFB. When enabled, the pedal position is sent to the game from TelemFFB via the API (so it can fake trim movement without the game seeing the axis movement from the trim). If something like windows defender or other AV is blocking that UDP communication between TelemFFB and the socket that gets created by the export script, the axis won't update properly in the game. You can reach out on the VPforce discord for more help Edited 11 minutes ago by Number481
Recommended Posts