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. -
@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?
-
@CloudWallace1981 that’s the one … v2.4.1.3 is the latest stable daily build
-
@airtex2019 many thanks, I’ll try this evening
I presume it is enough to overwrite the one inside the FalconBMS alternate launcher folder, right?
-
@CloudWallace1981
Quote from github: Instructions => unzip and run anywhere… AL will use the registry to lookup your BMS install location(s). -
My friend found a solution to the CM3 issues with the latest version of U3.
According to him, he got his throttle working by swapping place of the AB detent and the Idle detent in the Virpil software. For some reason, BMS reads these values differently in runtime even though all other tools like AL and ingame axis configuration indicates this correctly.
So swap them around, move the AB detent to the idle postion and vice versa.
-
@b0bl00i Virpil software has a concept of Idle- and AB-detent?
What does it do with those values? I’m a little confused by that. Maybe by swapping them, it has the mathematical effect of reversing the axis-direction? Neat trick, if that works.
-
@airtex2019 since I don’t have the cm3 myself I can’t check the software. According to him, in U2, default position is for ab detent and idle detent was correctly read.
In U3, bms this reads them in opposite way. From what I learned, swapping them and updating the firmware solves this.
-
@b0bl00i Worked for me, thanks a lot.