Inverted throttle + idle detent not working
-
@Tumbler31 if it helps debug … I’m using a VKB not a Virpil, but symptoms are the same. I think the axes are all 16-bit [0-65535] range. (thinking, possible arithmetic-overflow if doing any math with int16 shorts)
actual realistic resolution is more like 11 or 12 bit, but iirc the HID layer reports [0,65535] or [-32768,+32767] logical range for all axes
I have some test code handy to output the HID report, if you need me to doublecheck that.
-
@airtex2019 thanks for checking all this, all have a look. I also have a VKB and I thought it worked ok when I created this.
-
@Tumbler31 just to try to eliminate VKB/Virpil as a cause… I plugged in a Xbox controller, and mapped the Z-axis (the triggers) to throttle. everything I described above still repros.
but surprisingly, Joy.cpl shows the range of values is [0-65535] … and VKB joytester shows range as [-32768,+32767] (it was surprising to me, I assumed it would be an 8-bit range)
(in HID terms I think “physical range” is the unsigned int16 and “logical range” is the signed int16 … but I forget which of those you get from DirectInput API)
-
@airtex2019 issue found, should be fixed in a next release.
dinput reads the values as long, and I think most devices will send 16bit. To prevent issues with some devices sending 0/+max and others -max/+max, bms forces the behaviour depending on the axis
-
@Tumbler31 Just tested this out on U3. Still broken, but better!
I used the Alternative Launcher to set myA/B and idle thresholds correctly, like so:
But then launching into BMS, the axis thresholds are reversed (red on top, green on bottom):
You can fix this by setting the thresholds in BMS itself, but of course, that fix is overwritten next time you launch using the AL.
-
@RISCfuture thanks, will look into a fix for this
-
I made a guide addressing this very issue. You can find it here - https://forum.falcon-bms.com/topic/25900/solution-t50cm3-setting-up-physical-idle-detents-fixing-throttle-range-issues-in-bms-good-for-bms-dcs-and-other-flight-sims
-
@MandolinHarm I followed your guide and it doesn’t really address the reversed/broken throttle axis issue. You still have to manually set the detents in the settings page every time you launch the game for the axis to work properly.
-
@joshr03 yeah the second have of my post which addresses the broken inverted issue is really just a temporary workaround for a new issue present on U3. The core of the post is meant to help users get proper idle detents setup.
-
-
I have the Virpil CM3 Throttle and I have been battling the issue described here. I cannot fly BMS 4.37 U3 for the time being. Engine management is just uncontrollable. My aircraft will just run away from the taxi position.
I will wait for a fix for this bug.
Thanks to the BMS guys for your work. It is sad I cannot enjoy the new features in BMS 4.47 U3. -
@Ernestwinslow said in Inverted throttle + idle detent not working:
I have the Virpil CM3 Throttle and I have been battling the issue described here. I cannot fly BMS 4.37 U3 for the time being. Engine management is just uncontrollable. My aircraft will just run away from the taxi position.
I will wait for a fix for this bug.
Thanks to the BMS guys for your work. It is sad I cannot enjoy the new features in BMS 4.47 U3.Check this Post
-
@Ernestwinslow - I had the same problem. Go into your Virpil software and select “inversion” for each throttle. Let me know if it works for you.
-
@VIPER-0 Copy that. Thanks.
-
@Ernestwinslow fix in progress but will be a few days. I will post a beta build soon, for any Virpil owners who want to help test.
What I would try, in meantime…
-
Do all of your axis and button setup in Alt Launcher.
-
Once in BMS, re-configure your throttle axis/axes and detents. Click ‘save’ or ‘apply’
-
Alt+Tab out to Windows, and make a backup copy of your axismapping.dat and joystick.cal files
-
Until we get AL fixed… launch BMS directly via the exe. (from the /bin/x64 subfolder) Make yourself a desktop shortcut, with the cmd line params you like … eg
"Falcon BMS.exe" -window -nomovie -vr
Before each BMS session… or at least, anytime after using AL… replace the axismapping.dat and joystick.cal files with the versions you saved away in step 3.
-
-
@airtex2019 Thank you chief for helping out. All information is well noted.
-
I have prepared a daily build of AL with about 12 bugfixes post U3… including now, better support for single- and dual-throttle devices with reverse-direction axes.
Invite open to everyone, but especially Virpil throttle users – please send me a DM if interested in helping alpha-test it!
-
This post is deleted! -
Same problem here with a VKB STECS
Ooops sorry double post
Marc… -
Tested the latest off GitHub and it works for me now!
-
is the new build this one?
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases
or should we look elsewhere?