We are constantly working to make your experience with Viperpits.org the best it can be!!
missing or are needed and I will ask the Dev's to see if we can add them
Quotemissing or are needed and I will ask the Dev's to see if we can add themGreat idea.What's definitely missing in the SharedMem is the current HUD brightness level.We can fire keystrokes INC/DEC to change the brightness level but this is just fine for gamer's with keyboard.The simpitters with analog thumb wheels on the ICP need the current level in order to properly synchronize BMS with the pit.It would be great to have it in the form [0,1,2,3,4,5] where 0=OFF, 5=max brigthnessor float [0 ... 100%] if it makes them happier.More to come ...Klaus
In game time for the analogue clock (and for standalone clock for GCI/Awacs/ATC).And in viewpoint of ATC, wind (speed & direction) & QNH would be nice too
In game time for the analogue clock (and for standalone clock for GCI/Awacs/ATC).
When you wire a pot and declare it in the UI as HUD brightness, then when you enter 3D, the HUD brightness is defacto adjusted to the pot position, so no out of sync issues. It works just like a joystick, you don't have to centre your HOTAS before entering the pitSame for other analog controls.
I think it's indeed in Flight data 2AltCal reading (not per se QNH, but often is)&CurrentTimealthough it may need additional parameters (or conversion) to get exactly what you needGuys, there is an applet called BMSFlightData in your tools folder, there you can see it all
Agree 100% Olivier. Klaus, I dont understand how PHCC works that is different from any other system. Don't you also have analog pot inputs somewhere on a PHCC card?
JoyMapperDesktop application for remapping analog and digital inputs from DirectInput devices, BetaInnovations non-Joystick-class HID devices, and PHCC devices using PPJoy virtual joystick drivers.
I dont understand how PHCC works that is different from any other system
No problem with backwards compatibility. The developers have extended the shared mem so many times withadditional sections that is won't hurt at all. To me it would be the clean solution to have this extra info in there.
So keep the request coming, it's good to have these questions addressed anyway - but don't anyone be offended if the answer to your request is initially a pointer to where the feature already is implemented