Needle type VVI gauge incorrect when exceeding 3 to 4k ft/min
Focaldesign last edited by
Tested vanilla KTO & Balkans 3.5 with modified Janhas acdata.
In both I tested blck52 & any country MLU. Verified with shared memory (as read by Yame; Yame tested with tape VVI gauge, needle VVI gauge & CP60 data gauge to eliminate texture issue on YAMEs side).
Baseline: in both theaters, I first try the block52 with tape VVI gauge and compare the value in 3D in BMS to shared memory and extracted gauges. They correspond ok. That should make me believe the shared memory and original BMS 3D VVI textures are ok, and YAME is reading it out and visualizing it correctly too.
Comparison: When I switch to an F-16 with needle VVI (e.g. BAF MLU) the shared memory and the extracted gauges still are in sync. However in BMS 3D, once moving above 3 to 4k ft/min (or below -3/-4), the needle shows a too high (low) value (e.g. +4k ft/min in memory shows needle at +5k).
You can also tell by when moving to the max the gauge can offset (+/-6), the needle is past the 6 marker in 3D. The needle is actually correct (6 is 90°), but the texture shows the 6 a bit shallower then full 90°.
I believe the used VVI gauge texture is a bit wrong as it comes to the indicated white markings.
I have cut out the texture from the dds, and placed a picture of a real one I took above it with the same 0 point and matching the up/down labels on the top/bottom left. You see the further you go up or down the scale, the more the real start to diverge from the BMS version. I think the used picture was slightly badly squeezed/transformed during implementation.
Not a biggy, but I thought I’d let you know.