Others can chime in, but I have never used CH Control Manager and don’t recommend it. For sure any control setup done in Control Manager will NOT carry over to MSFS! The sim recognizes the CH Yoke, but it is completely “blank” with no bindings. See my post further up the thread that discusses this and links to Squirrel’s YT setup video. Also note that you don’t need to know the input numbers on the Yoke - the binding process can recognize the input by activating it (see the tip on this below).
I know the Control setup interface can be intimidating, but it actually works well once you understand the process. I’ve had to completely rebuild my CH Yoke bindings a lot of times during the alpha/beta and it has always worked. The hardest part is finding the correct MSFS Commands that you want to bind! The screen shot examples above cover most of the important basics.
A few quick tips:
- The Filter defaults to “Assigned” which only shows the commands that are currently bound to the selected controller. If the controller doesn’t have default bindings, you won’t see anything! To see all the commands, change the filter to “All”. To see a recommended set of starting commands select “Essential”. The “Search By Name” will let you narrow down the (very long!) list of commands. Helpful Name searches are “Axis” (see below) and the various views “Cockpit”, “Instrument”, “Drone”, “External”.
- To bind an input (button, switch, slider, axis) you don’t need to know the actual input number for your controller. MSFS can recognize the input just by activating it during binding. When you click on a command, it will bring up the “binding window”. Click on the space that says “Search By Input” and it will light up. Now physically activate the input on your controller. The space should fill in with the input number. Click “Validate” to complete the binding.
- All “linear” controls need to use the “AXIS” commands, not the basic commands. That is the issue you are having with your control inputs. This includes control surfaces, engine controls (throttle, etc), brakes, etc. Basically anything that needs proportional input will use the “Axis” version of the command.
- Unless you have a complex throttle quadrant with multiple throttles, make sure you bind your Throttle to the “Throttle Axis” command and not any of the numbered Throttles. This will control all throttles on multi-engine aircraft simultaneously.
- My example has the “Hat” control bound to the “Quickview” camera controls. These are the ones that snap back to center. If you would rather have the Hat do smooth panning, use the “Cockpit Look” commands and not the Quickview ones.
- You can actually access and change Control bindings while inside the live sim (use Esc to get to the main menus). This is helpful if you are trying to fine tune or debug things.
- You can create multiple binding Profiles for each of your Controllers. This is helpful if you want to map your controls differently for different aircraft. It is also useful if you need to adjust the Sensitivity settings differently for different aircraft. Just make sure you select the correct Profile for each session.
- I have not used any external controller management or calibration applications or drivers. If you do, your mileage may vary! For sure any control input assignments you make outside MSFS will not carry through inside the sim. I have seen a lot of suggestions to use the Windows applet to calibrate your
- Adding an Xbox Game Controller (wired or wireless) makes controlling the Drone Cam and Slew really easy and intuitive! MSFS immediately recognizes it and sets up all the bindings by Default.
Please let me know how else I can try to help with this. Believe me that all of us that have been part of testing really want to see you up and flying! Rick