Virpil CM2 throttle get Z axis (radar antenna elevation in F-18) change to 0%, 50% and then 100% values only after use with latest Openbeta.

[Bear21]

My CM2 Z axis (front zoom/radar antenna elevation) behaves strange after use with DCS (Software 2021.01.02, DCS latest Openbeta) , it suddenly has a Windows output 0% or 50% or 100% in steps rather than an axis behavior. The axis is perfectly normal in VPC configurator with a smooth progressions of raw and calibrated values with 20210102 software but VPC tester and Windows Game controller utility shows the three value behavior as well. I have set no axis to button or other settings to explain this behaviour, all axis are per default, only calibrated. I have done a detailed check in the details window of this axis against the TDC axis (they all three use the same type of sensor) and the settings of all three are identical, left per default in the 20210102 firmware.

If I reload the firmware and load the profile for the CM2 it retakes a normal axis behavior in both testers. Then I activate it with DCS and in e.g. F-18 axis it retakes this stepwise output. A recheck with VPCtester and Win game controller confirms the changed output, now in has changed to three steps. It has the values 0%, then 50% and finally 100% as you move the axis over the range.

I check my newly arrived CM3 (not used until now) loaded with the same firmware and profile (I added calibration of course), it behaves correctly in VPC tester, Windows game controller setup and DCS, also after flying sorties with the F-18. Then I check the CM2 and CM3 throttles on my work computer where I've loaded 20210102 and there both have the correct analog 0% to 100% axis on VPC tester and Win game controller. As I tested on this computer before I reloaded the CM2 with the 20210102 firmware/profile the stepwise CM2 behavior was on this non gaming computer as well, so it tells you it is indeed a change in the throttle output via Windows.

It's seems it's something with my DCS rig that changes this output on the Windows level but I can't figure out what. I have no known software between the VPC throttles and Windows or DCS. I'm an experienced Win user and keep my PCs minimally loaded with software to keep control. I did add Steam VR recently but find it hard to think it would be involved. I do not use Joystick Gremlin or any other joystick output modifier software.

That this shows up in VPCtester is strange, you would think it reads the CM2 output directly, but how can then the output change like this between computers with the same version of VPCtester. Anyone experienced this before?

I have now changed to use the CM3 with DCS (pray it doesn't degrade as well) but would like to understand what is happening with the CM2 throttle with the same firmware, profile and calibration attached to the same cable and rig as the CM3.

[Bear21]

This was solved by Steve K.  at the Virpil forum, here his post:

 

Almost sounds like maybe DCS is trying to using windows to calibrate the axis and not seeing the range and messing things up.

Try going to Windows game controllers properties for the throttle and do a 'Reset to default' from the Settings Tab and see if that brings back the range in VPC tester without having to reflash.

 

I reset to default in the Game controller ulity and now I had my alanog axis back. Strange case of Windows/DCS trying to be smart. Thanks Steve K.