Cannot bind throttle to actual throttle axis

[nchwomp]

I have a VKB Space STECs that I wanted to use for my throttle, but the game won't let me bind the throttle axis to throttle control. I can bind the throttle axis to any other axis-controlled system in the menu, and I can even bind the throttle control to any other axis on the STECs. Has anyone else had this problem?

[Vice]

What happens when you attempt to bind the throttle? And what method are you using to do so? If you post some screenshots of the 'Axis Configuration' menu as you attempt to bind throttle to the axis you want, I may be able to determine more about what could be happening. You can send the screenshots to me directly via e-mail if you like ( starwraith.com > contact ).

In the 'Axis Configuration' menu, does the axis indicator for the throttle axis you want to use move when the device is selected at the top of the menu and you move it? Here are text instructions on the procedure for reference:

https://www.starwraith.com/evochronlega ... me.htm#400 (axis controls)

Here is an older tutorial video showing how to map axis inputs (one note of change, the 'all' axis option has since been removed in favor of simply binding controls to individual axis channels):

[nchwomp]

Apologies. I just fixed this, I believe. My Space STECs came with an attached small console of extra buttons and switches. One in particular was a three-way switch that was in a down position that constantly registered as a button press. When I put the particular switch in its neutral position, I could register the throttle correctly.

To answer your question, the axis would move the slider, but the 'not-bindable' noise would play when I tried to bind it.

[Vice]

Active button presses shouldn't create a conflict in the Axis Configuration menu and will be ignored in the Key/Button Controls menu when mapping, so perhaps something is skipping or bypassing the input somewhere along the line (like the three-way input acting as a mode switch or something). If a buzz sound occurs in the Axis Configuration menu, that usually indicates a conflict with something that has already been mapped for the same control (since axis inputs are mapped to controls in that menu as opposed to controls mapped to inputs in the key/button menu). Peculiar behavior regardless, but stranger things have happened

Glad you got it to work.