STPT page question
-
On DED STPT page,it will show LAT,LNG and ELVE for pre-plan. In 4.33,the ELEV is correct data(like 18000ft). In 4.34,the ELEV is not correct data(like 0ft, 30ft ).That is not for pre-plan.
-
The 4.34 situation is realistic. F-16s are programmed with ground surface elevations in the ELEV field and not flight plan altitudes.
-
You have it backwards, actually.
It used to be incorrect, and is now corrected. Steerpoints are points on the ground, not in the air, so the elevation should be the altitude of the terrain at the steerpoint coordinates. Which is what we have now.EDIT : A bit late, sorry.
-
Hi All,
OK. But how the pilot can know during the fly the planned elevation for that STP? Is there any point in which this information is accessible?
Thanks,
Gundam
-
Hi All,
OK. But how the pilot can know during the fly the planned elevation for that STP? Is there any point in which this information is accessible?
Thanks,
Gundam
Well … in the printed Mission Data Card!
Not sure why not in the programmed STP though. -
OK. But how the pilot can know during the fly the planned elevation for that STP? Is there any point in which this information is accessible?
Yes. In his data-card or ATO sheet, or worse case scenario … his memory.
-
Wasn’t there a kneeboard with a notepad on it at one stage that could be used for notes such as these?
-
Wasn’t there a kneeboard with a notepad on it at one stage that could be used for notes such as these?
WDP, print, pen/pencil, jot down notes
-
Correct.
WDP can even inject your mission data on in-game kneeboard.
-
Good!! Ok thanks.
-
Frederf, thx for explain. I’m still learning and still finding i missing some basics xD (RTFM xD). I was wondering if it is a bug or not. So yes, Data from briefing sheet are for flight plan altitudes and data in DED page 4 ELEV (callsign.ini and mission.ini) are true elevation data on the ground of that points. I was mixing these two things together. Now it has clear sense.