Throttle range issue with Virpil CM2
Just about managed to get my axis bindings sorted using a combo of the alt launcher and in-game setup: with one exception.
My throttle is correctly registered and inverted (in game throttle -> virpil throttle left), but it only seems to register the last 50% of the travel, so my throttle is stuck between 50-100%. It doesn’t show this when checking the axis guage in the bindings, and it looks fine in both the virpil config tool and DCS. The CM2 doesn’t have detents so they have been left as default (right at top and bottom).
What am I doing wrong?
Hi, I’m not sure exactly what the problem is, but if you are using Alternate Launcher, don’t go back to the in game menus and make changes to HOTAS there. Do it all in AL if you can. That could be your problem.
@Caster someone else was having similar sounding problem, with Virpil CM3 throttle
the “reverse” axis checkbox is new for 4.36 … it’s possible there’s a bug or quirk with Virpil throttles
Late reply but turns out the issue was a case of user misuse (isn’t it always )
Long story short, the Alt Launcher UI doesn’t reflect the inversion of the throttle properly when the axis is inverted. So setting the AB detent at 80% showed it was in idle cutoff (or something like that, showing the wrong detents in UI even if they were set properly. Naturally I was trying to ‘reverse’ the detents to get the UI looking right, which set my detents up backwards and caused this weird issue
Looking in game you can check the real detent settings, although they should be set in the alt launcher and not the game since the change will not persist otherwise
@Caster what version of AL?
I’m not sure if even the latest supports the throttle-axis-reverse setting of 4.36.
@Caster bug/quirk and workaround explained here: