[DCS BUG] Rudder pedals 'RZ' binding issue

Hello great people at HeatBlur!!!

First of all: WOOOOOOOOOOOOOW what an amazing great module you guys have created!

Keep up your great work and dedication.

So far I have one issue that's making flying a little bit harder.

I can not bind my MFG Crosswind rudder pedals because the whole binding of 'RUDDER' column is RED.

It worked fine the first moment I flew, was nicely bound but suddenly it stopped working and showed RED in the control options.

None of my other DCS modules have the issues and my rudder pedals work everywhere.

There's a thread with numerous people experiencing similar issues.

The fixes they have proposed do not work for me.

Do you have a solution for me, and possibly some others as well?

Thanks for any response.

Same problem here, Viper RX slaw pedals. All modules work fine, but not f14.

Sent from my SM-G965U using Tapatalk

We're using the slaw pedals on the team (more than 1) and they are working fine here (our main FM engineer build the Tomcat on slaw pedals). Sometimes after a DCS update, the inputs can get borked a bit. I know this is a very unpleasant suggestion, but what usually does the trick for me is to deleted the config inputs (backup just in case it does not work), and the rebuild them.

I will try that iron Mike, thank you

Sent from my SM-G965U using Tapatalk

I really hope it works!

No such luck IronMike :(

Attaching pics showing other modules without issues and the F14 still showing rudder binding problem after deleting configs and rebinding.

I really don't think this is a problem on my end. I really want to fly the F14 again.

Dropbox to screenshots

https://www.dropbox.com/sh/bhn76r6pxivot5e/AABPmC-Gr1AESFFcAb_sKsP6a?dl=0

OK, sorry to hear that. It is really weird, but despite only being an issue in the F14, I cannot promise that this is something on our side and that we can do something about it. We will take a second look though, to see if we can. My apologies for any inconveniences.

PS: If you use Warthog as your stick, there was an issue that if DLC is bound to the ministick on the throttle, some inputs didnt work. When users rebound it to something else it worked again. Maybe you can try that, too, if that is the case.

I will try that and report back. Thanks for the suggestion!

Got it working! Not sure exactly what it was, but something with my modifier key that I had setup on my Warthog Joystick (paddle button had a conflict). After deleting configs again, and this time setting up rudders before anything else. All is working well. Thanks for your patience IronMike. I had almost given up waiting for a new patch to change something. Your last msg sent me back to try one more time. So glad I did!!!

Oh, this makes me very happy as well! So glad it worked, and so good to know it was the modifier. Could you tell me please which one exactly and what stick/ throttle or keyboard button? This might help others who have the same issue in the future. Thank you!

Hi,

I eventually got it fixed after an update and deleting the config file.

I do not use modifiers so that was not the issue on my end.

Thanks for replying HB.

Had the same problem with 2 other modules at different times and it was always fixed with a dcs repair for me.

I had the paddle on my TM warthog joystick (joystick button 4) set as modifier. But I have it set that way again. It just worked after I deleted the config files and started over, setting rudder pedals up first before reassigning the modifier. It possibly may have worked w/out having to delete the config files first if I deleted the modifier, then setup the rudder pedals. Then reassigned the modifier. But I'm not sure.

Hey folks, I'm having the exact same issue - did a total reinstall of DCS to try and fix it. All seemed well until I rebound all my controls, and the red colouring over rudder appeared again. Now I have to reset rudder to default controls every time I start the game. I'm not sure how to find any conflicts - I can't see any? How do I check if there are any modifiers?

FIXED! Turns out my Honeycomb Alpha flight controls were causing the conflict, and there was no way to stop this other than unplugging this controller.