HUD brightness axis

[unknown]

I use one of my axis on my Virpil Mongoost-50V2 throttle for the HUD brightness axis binding for many modules in DCS.

With the Mirage-2000C there is a little problem. It looks like the Mirage Module is the only one that uses values from 0 -100 to interprete the axis instead of -100 -> 0 -> +100 like all the other modules. This means that the first 50% of my physical axis movement is ignored by the module and onyl the last 50% to 100% are used to regulate the in game HUD brightness.

null

 

[Kercheiz]

Ok, I fix this for consistency with other modules. Aux gunsight deflection has the same issue and is fixed too.

Too late for january update though, it will come in february.

Edited January 20, 2023 by Kercheiz

[unknown]

15 hours ago, Kercheiz said:

Ok, I fix this for consistency with other modules. Aux gunsight deflection has the same issue and is fixed too.

Too late for january update though, it will come in february.

 

Thank you very much!