Bombing solution seems to use Barometric Altitude only

[ldnz]

In opt mode, a2g, in a dive with a good steady solution bombs appear to always fall short. In active pause, the only thing that appears to affect the indicated slant range is the altimeter setting, laser makes no difference.

It appears that radar altimeter and laser aren't being used for slant range calculation, only baro alt.

Unsure, but in previous mission in mountainous terrain I found a2g cannon with laser (I think, but altimeter would have been no use) to be pinpoint accurate, so possibly just not right with bombs.  

LastMissionTrack.trk

[AeriaGloria]

I have a feeling this has to do with the target altitude in DTC. I couldn’t understand the way Wags explained it exactly what this was changing, and it seemed to be for every waypoint 

[NineLine]

It's quite simple. For accurate ground attack, it helps for the aircraft to know the exact target altitude. If there is a difference in elevation of the aircraft altimeter and the target elevation, that can throw off calculations. The Target Point DTC function simply sets this elevation, just as Wags explained.

[ldnz]

Thanks, but which part of the calculation? Just density? Right now it appears only barometric altitude is used in the slant range calculation, not laser

[Esac_mirmidon]

And we should set barometric altitude to QFE or QNH for the Mig-29 regarding ground attack?

[AvroLanc]

18 minutes ago, Esac_mirmidon said:

And we should set barometric altitude to QFE or QNH for the Mig-29 regarding ground attack?

Set QNH for ground atttck presumably, otherwise there would be no need for setting a target point elevation. This also assumes that, by design, you must ensure the target is co-located as closely as possible with your current Waypoint. 
 

[IvanK]

1 hour ago, NineLine said:

It's quite simple. For accurate ground attack, it helps for the aircraft to know the exact target altitude. If there is a difference in elevation of the aircraft altimeter and the target elevation, that can throw off calculations. The Target Point DTC function simply sets this elevation, just as Wags explained.

But ....based on the limited documentation out there I believe IRL you cannot actually set a target elevation preflight into the INS/WCS. Though the DTC allows it and the DTC capability is being used to neatly simulate data entry by the ground crew on the ground , IRL there just isn't provision for any altitude entry into the system. Happy to be corrected here.

I guess if there is documentation that shows that Baro ranging can be used then that would settle the issue ... just haven't seen that in the Docs I can source.

Though I guess changing the QNH to a dodgy value (aka target area QFE) might work ??

Edited 12 minutes ago by IvanK