Have you seen this post from a while back?
This seems to talk aout similar issues and there seems some confusion/success in creating a new profile for the yoke using preset manager - something about the mappings are not being saved properly. This might be worth you looking at if you’ve not already?
EDIT: there is also reference to something called CH Control Manager - not sure what that is though - it might be a calibration tool perhaps?
I did see that post yes thank you,
It’s mostly people that failed to map it to the axis controls. I am absolutely sure that the mappings are on the correct axis’ and saved properly.
CH Control Manager Software is simply a calibration tool as you suspected. I did check in many software (including this one) that my yoke is calibrated properly and the axis’ works. In fact, even Microsoft Flight Simulator correctly gets the inputs from my yoke as I can see the correct movements in the sensitivity tab.
Hallelujah, I got it.
You have to delete the input, then confirm (not try to reassign while it’s already assigned).
THEN pick the axis (e.g. throttle 1 axis) from the big list of unassigned input again and assign the axis using the lever. Now it magically works.
I can’t believe this was it… It makes no sense. I tried to de-map and reassign but I just didn’t save it on blank before. Oh well thank you so much
If confirmed, please mark the reply that solved your problem as “Solved/Solution” by using the three dots menu on the reply. This will help future searches by readers. Thanks!
Ah yes! This is like the issue with the Bravo axis 2 not being recognised properly. A glitch, but very annoying! Glad you got it sorted - I was stumped!
Thanks for making this post! I have the same exact controller and I was pretty annoyed until I found this. It works now for me too!
Guys, creating new blank profile was the solution I learned from here. Thank you. It works.
Krangerich; Great catch. I created my Flight Sim Forum account this morning when I recognized this behavior from the early days (20 years ago) of testing the programming of the first in a series of products that my company manufactured. In that product, the software required users to validate the clearing of a configuration setting, before they could enter a new setting for the same control. We corrected that to a setting overwrite concept before the product was released. I have USB CH pedals and a USB CH Yoke and the default assignments were present when I plugged them in. It’s interesting that the defaults for my CH Pedals worked fine, but the defaults for the CH Yoke did not, even though the default axis names were the same as the ones I eventually selected. I cleared the first assignment in the existing yoke profile, then validated it and when asked, gave the profile a new name “CH Yoke Cleared Profile”. I then cleared each assignment, validated it and went on to the next control and repeated the clear and validate process. Somewhere in another article an author stated that FS sometimes improperly scanned axis controls, so when I made the new assignments, I too selected the control name from the list and then validated it. Interestingly, when you select the input from the list, the input name appears in both the selected and scanned text boxes. The control scan function does recognize and properly assign switches, so it can be used for assigning all of the switch controls.
FWIW I have this issue with my Honeycomb Bravo and none of the above suggestions have worked.
I know this is an old thread, but having he same issue with the Bravo controller, none of the above solutions have taken care of the issue. Anyone else still having this issue?
Same problem here with a vJoy/Joystick Gremlin setup. Works fine with every other game/sim. Under the sensitivity settings I see all my axis’ moving correctly. When I try and assign them to flight controls the bar under the control assignment doesn’t move. Tried refreshing control profiles, clearing and validating then re-assigning and re-validating but nothing works.