Jump to content

Wrong IAS reported in scripts for non FC3 aircrafts


Recommended Posts

I have noticed that with non FC3 aircrafts, DCS World reports "wrong" IAS while reading values from LUA export script environment.


My code is baed on values found in scripts like


AirspeedNeedle			= CreateGauge()
AirspeedNeedle.arg_number	= 11
AirspeedNeedle.input		= {0,   50,   100,  150,  200, 250,  300, 350,  400, 450,  500, 550,  600, 650,  700}
AirspeedNeedle.output		= {0.0, 0.05, 0.10, 0.15, 0.2, 0.25, 0.3, 0.35, 0.4, 0.45, 0.5, 0.55, 0.6, 0.65, 0.7}
AirspeedNeedle.controller	= controllers.AirspeedNeedle


Here is some pseudo code:



For instance, while doing the test with the TP-51D, the value reported is something like about 200 times bigger than expected. I have noticed the same issue with other non FC3 aircrafts like the A-10C.


IAS is reported as expected by DCS World


Is this a bug or a new intended behavior?

Link to comment
Share on other sites

  • 2 weeks later...

Confirmed, for DCS 1.5.1 beta viewed in Tacview 1.4


Older PFM/EFM aircraft like the Ka-50, A-10C, P-52D and UH-1H have bugged IAS



FC3 aircraft like the Su-25, Su-25T, F-15C are ok



as is the 'Standard Flight Model' Hawk.



Surprisingly the L-39C is also ok






Edited by Ramsay

i9 9900K @4.7GHz, 64GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, Winwing Orion 2 Throttle + F-16EX Stick, TIR5, Win 10 Pro x64, 1920X1080

Link to comment
Share on other sites

  • 3 months later...

I have finally found the problem guys!


After a long debugging session, I came to the conclusion that the IAS now exported by DCS World 1.5+ in m/s instead of a “hand position” like in DCS World 1.2.


Sorry I didn’t understand this change earlier… This will be fixed in Tacview 1.4.3.

Link to comment
Share on other sites


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...