I recently bought a CH Products Flight Sim Yoke and I have been trying to configure it and have been trying to fiddle with controls for such a long while with no progress and I’m so done I would be thankful if someone can help me.
The Axis’ -both ailerons (x) and elevator (y) axis and all three throttle axis’ are recognized by my windows 10 system (checked on joystick configuration) and also by flight simulator 2020’s sensitivity configuration menu. But when I map the joystick axis’ to primary control surfaces they don’t move at all
The “Joystick L-Axis X” type of controls don’t work at all, but “Joystick L-Axis X- and X+” are recognized as buttons.
When the axis control “Joystick L/R-Axis X/Y/Z” is selected the control stays stationary when I’m actually moving my yoke… The x/y/z- and x/y/z+ movements are recognized as if they are buttons, just not recognized in the whole axis while any other app or sensitivity tab recognizes the movement as if it
is an axis.
When I try to move the yoke for it to recognize the axis, it doesn’t recognize the whole axis “Joystick L/R-Axis X/Y/Z” but instead, a button as “Joystick L/R-Axis X-,+/Y-,+/Z-,+”
I have videos but I can’t post links or attachments.
The sim sometimes doesn’t detect the analog axis when you move them while trying to bind them. And instead recognise the far end of the axis which is the X- and X+.
If you’re having trouble with trying to get the X Y Z to be detected. Just manually assigning them by choosing them from the drop-down menu. You don’t have to press or move the yoke to assign it. Just look below the empty field, open the drop down menu, and choose the Joystick L-Axis X.
Once you stored that, you should see a bar underneath the axis that you assigned. When you move the yoke, the bar should either empty or fill smoothly according to your movement. Try it out.
Thanks for your input, however, mapping is not the issue. I have already mapped the whole axis’ to the corresponding controls.
For example, the elevator axis is mapped to “Joystick L-Axis Y” and there is a bar filled exactly to the halfway point.
But when I actually move my yoke in Y-axis (move the yoke forward and back), this bar doesn’t move at all. (However, I know my computer recognizes the movement correctly because when I move my yoke in this axis the “Joystick L-Axis Y” movement is recognized in the windows 10 joystick configuration tool and also Microsoft flight simulator sensitivity tab.
The movement is simply not recognized only in the bar after I map it.
So the Joystick L-Axis Y dot is moving when you move it on the sensitivity curve… But it doesn’t move in the bar underneath the elevator axis? that’s really weird…
Have you tried restarting the binding by resetting all your controls into a blank profile? I’m worried there’s something feeding the sim that brings your elevator axis to neutral. And I mean, resetting all your controls for mouse, keyboard, everything to a blank profile with nothing being bound.
Yeah that is exactly what happens and it is extremely weird, I have scoured the web for similar problems but no one had it like me.
I haven’t tried resetting all my controls into a blank profile, I don’t see how that would fix my issue. But my yoke came with default controls and I have tried resetting it back to default controls and re-mapping (though I don’t even need to remap throttle-mixture-propeller and primary flight control inputs because they are already mapped to what I want them to be mapped to) but I did try clearing the mappings and re-adding them, which didn’t fix my problem.
I was also using logitech extreme 3d pro joystick before, that controller didn’t have this issue, nor does my logitech/saitek rudder controls, they just worked outside the box with the axis’ working correctly.
What I’m trying to say is, to help you eliminate anything that might have compromised or affected the behaviour of the controls. This means, disconnecting any other devices that you have that might have caused this.
I’m not saying to reset them to default. I meant, set them to a blank profile without any controls bound. So the only thing that should only work is your mouse clicks and your Yoke. Even Your yoke should start with a blank profile so it doesn’t have an internal conflicting commands.
Working out-of-the-box the box is usually something to be aware of. I always take it with a grain of salt. The reason being is that working out-of-the-box means it’s configured by the manufacturer in a lab somewhere. which means it’s created in a fully controlled environment. Practically, each and everyone and their PCs are unique. There are different combinations of hardware, software, etc. And then people’s preferences are difference, and different interpretations on how to use them.
So for me, whenever I receive a new joystick or a new controller. The first thing I do, is to clear all bindings and start to manually bind them from scratch. That way, I can make sure I have full control over what my joystick does, and how to do them, while also eliminating “bloat” or redundant or conflicting bindings. But that’s just me.
I’ve just tried disconnecting any and every other control device recognized (basically my keyboard and mouse) I have tried blanking their controls as well, I even connected my old previous controllers like my old Logitech stick and unbound all controls in that before disconnecting it.
Unfortunately, it didn’t help.
The only thing I know is that it’s a software issue definitely caused my MSFS2020, I tried many joystick test applications and they all recognize all of the movement axis’ correctly.
Yeah, that’s weird… I dunno what else there is to it… Maybe you need to contact the manufacturer or report a zendesk? Make sure you have some recording for them to review… Judging from this video, there doesn’t seem to be anything wrong. But this is an older video, though.
My Bravo Throttle Quadrant arrived today and I’ve got the exact same problem here with the axis.
Alle axis work properly in the Windows controller settings or sensitivity settings, but when assigned to a control (like in the default profile), the bar doesn’t move.
The one I’m using (CH Products Flight Sim Yoke) doesn’t come with drivers, it works directly from USB without any need of drivers.
As mentioned before, the yoke controller axis work normally with any other app and recognized by both my system and the sensitivity tab of MSFS2020. I think there is a bug on mapping which I will be reporting to zendesk and the bugs section of this forum.
This is not the problem. I wasn’t able to include links to videos or add attachments when I first launched the thread but I think now that I have been a user for some time I can add links for videos on this behaviour (couldn’t add it as an attachment as the file was too large)
Can you check that you have no other controller mapped to these controls (i.e. to ailerons and elevator axis)? It might be that this is accidentally mapped to something else and this is overriding the input from the CH yoke. search for this in the top box under search on the left, one by one for each of your attached controllers
I did unmap all other primary flight controls with any other of my controllers including unplugged ones. I also tried unplugging every single controller device other than my yoke. The problem still persisted, unfortunately.
