TGT Steerpoints taken from dtc missing elevation
-
Flying tonight noticed that the tgt steerpoints I had saved on my datacard in 2d had no elevation data in the jet on the DED… fortunately I had each tgt steerpoints GPS data written down and also the elevation so I just punched it in manually. Wondering if this is a bug?
All the gps points were correct in the ded… just no elevation data (-0ft) to be clear.
I made my wingman check his stpt data too and his was the same… -
Flying tonight noticed that the tgt steerpoints I had saved on my datacard in 2d had no elevation data in the jet on the DED… fortunately I had each tgt steerpoints GPS data written down and also the elevation so I just punched it in manually. Wondering if this is a bug?
All the gps points were correct in the ded… just no elevation data (-0ft) to be clear.
I made my wingman check his stpt data too and his was the same…’
If you’re using GPS, what’s all this hoopla regarding target elevation? (BMS)
-
It’s true. BMS currently does not source any steerpoint elevations from the data cartridge. It doesn’t matter what you write in the callsign.ini, elevations for steerpoints won’t follow.
I think it’s related to recent change to not have flight plan altitude (21,000’ etc.) but instead ground elevation as the flight plan steerpoint elevations which is operationally realistic. Probably there was no easy way to get Falcon to read elevations for an arbitrary point in 2D interface to save to DTC. As such flight plan altitudes are still saved to DTC but 3D world ignores these values and substitutes ground elevations.
The downside is that no DTC editing of elevations propagates into the airplane which includes steerpoints outside of the normal flight plan.
-
’
If you’re using GPS, what’s all this hoopla regarding target elevation? (BMS)
because of this:
Target coordinates can not be accurate for a falling bomb unless you have accurate target elevationsteerpoint elevation have been changed in 4.34, but the change is not complete and we will have to consider a Work in progress
Hopefuly, targetting at some point will need the Z value for accurate placement of targetting point
I guess it’s a check in 3-4 weeks… -
@Red:
because of this:
Target coordinates can not be accurate for a falling bomb unless you have accurate target elevation……. and an accurate aircraft altitude and/or height position. Either provided by radar updates, baro (ACAL) or various radar or laser telemetries.
GPS won’t provide a very accurate vertical position because of the approximations (among other) from its digital earth model. -
Fortunately we don’t have WGS84 or MSL subtleties to worry about in the jet
Just to be clear, does the DTC file itself save elevation ? AKA : in callsign.ini, do you have elevation = 0 ?
If yes the fix might be more troublesome -
l3crusader, custom waypoint elevations are saved in callsign.ini but airplane doesn’t load them. If you look at flight plan saved in DTC you will see flight plan altitudes (e.g. 22,000’) but when loaded into the jet it turns into surface elevations instead. For non-flight plan waypoints like precision it saves the ground elevation but it’s not loaded (-0 feet).
-
As partial solution, TGP seems to know the exact elevation of every point it is looking at. So i select my target steerpoint, cursor zero and replace the 0 in the elevation line with what I read on TGP display.
-