Woodstock Posted March 2, 2006 Posted March 2, 2006 Hi @ll! I´m shure this was brought up before, it´s just that my poor forum search skills didn´t find any old threads concerning this: The F-15C in LockOn has a buggy TrueAirSpeed indicator in the radar display. Bottom left corner of the radar shows a digital GroundSpeed readout which is working correctly. Bottom right corner readout is supposed to display TAS but in fact is showing Indicated (or Calibrated) AirSpeed. I did the following test: F-15C flying at sea level (Altitute 80 ft) with ten knots headwind at constant 400 KIAS. External F2-view bottom info-line shows 402 kts TAS, radar display shows 400 kts TAS (which is wrong, should read 402) and 392 kts GroundSpeed (GS). Climbing altitude 20.000 ft while maintaining 400 KIAS, the TAS should be rising over the IAS at about 2% per 1000 ft above MSL. It does so quite nicely in the external view, but not in the radar display where it stays at 400 kts. Having levelled off at 20.000ft MSL, we have the following situation: IAS still 400 kts, TAS (ext. view) 550 kts, GS (radar display) 540 kts, which is all about correct. But: The TAS displayed in the radar display still shows 400 kts, which is wrong, it should read 550 kts. This must have been noticed before. I imagine this to be a quite simple error that could easily be fixed. Since LOMAC is actually calculating and exporting the values to the graphic engine for IAS (HUD & Airspeed Indicators), TAS (external views and mission editor) and Ground Speed (F-15 radar display and A-10 TOT HUD readouts), I think this could be fixed by correcting the code that incorrectly exports IAS to the radar display TAS readout whereas it should export the TAS value. Estimated workload for ED: maybe 15 minutes work for a single programmer and maybe one man-hour for testing. Am I wrong somewhere? Didn´t anyone notice before? Is it only me having this? Is it not so easy to fix? I expect this to be corrected in 1.2. "For aviators like us, the sky is not the limit - it's our home!"
Brit_Radar_Dude Posted March 2, 2006 Posted March 2, 2006 Estimated workload for ED: maybe 15 minutes work for a single programmer and maybe one man-hour for testing. Nice one Woody old mate ! Gave me a good laugh. Whenever I was asked for an software estimate for a bug fix, I never gave an answer less than 1 man-month.... [sIGPIC][/sIGPIC] Sorry Death, you lose! It was Professor Plum....
Woodstock Posted March 3, 2006 Author Posted March 3, 2006 Yeah, you´re most welcome, ol´ chap!;) It´s so funny to be in the same business like you without having any mutual understanding for your work... I beg your compassion for my impatience, me being just an end-user, playing the "safety-against-all-odds" game day in, day out without pause button. To be honest, it´s just jealousy making me rant here, not having the time to pick the nose or scratch the crack now and then...;) Cheers! @ all: Anyone else here not willing to fly with a TAS display that shows IAS? "For aviators like us, the sky is not the limit - it's our home!"
S77th-GOYA Posted March 4, 2006 Posted March 4, 2006 http://forum.lockon.ru/showthread.php?t=6735&highlight=true First reported a year ago. It broke with 1.1 and it's been broken ever since.
Woodstock Posted March 4, 2006 Author Posted March 4, 2006 Thanks for the hint, Goya! S! Now, that´s really a shame! Something (supposedly) that easy to fix being ignored for so long...:mad: You know, ED, I´m trying to teach basics like Heading/Bearing/Track and IAS/TAS/GS to newbies for the benefit of the whole community. You could help me here by correcting this! "For aviators like us, the sky is not the limit - it's our home!"
Recommended Posts