![]() 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.Basically anything that needs proportional input will use the “Axis” version of the command. This includes control surfaces, engine controls (throttle, etc), brakes, etc. That is the issue you are having with your control inputs. All “linear” controls need to use the “AXIS” commands, not the basic commands.Click “Validate” to complete the binding. The space should fill in with the input number. Now physically activate the input on your controller. Click on the space that says “Search By Input” and it will light up. When you click on a command, it will bring up the “binding window”. MSFS can recognize the input just by activating it during binding. To bind an input (button, switch, slider, axis) you don’t need to know the actual input number for your controller.Helpful Name searches are “Axis” (see below) and the various views “Cockpit”, “Instrument”, “Drone”, “External”. The “Search By Name” will let you narrow down the (very long!) list of commands. To see a recommended set of starting commands select “Essentials”. If the controller doesn’t have default bindings, you won’t see anything! To see all the commands, change the filter to “All”. The Control Filter at the bottom of the left part of the screen defaults to “Assigned” which only shows the commands that are currently bound to the selected controller. ![]() I know the Control setup interface seems intimidating, but it actually works well once you understand the process and is really powerful in helping you set up your controls exactly the way you want! In addition here are some general hints and tips.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |