[ALREADY REPORTED]Wrong diamond location via HUD

[TAW_Impalor]

Instant action - Syria - Bekaa Valley Strike. Always see the diamond in the wrong place via HUD after finding a target with TPOD. So gun runs are problematic. In other missions too has noticed this problem, but I think only on Syria map. Not sure if it's a Syria map bug or a Hornet bug, so feel free to move into another forum. Track exceeds 5Mb, can't attach...

 

Update: cannot reproduce on PG and Caucasus, so it's definitely a SYRIA map bug!

[dorianR666]

Ensure the INS knob is in IFA position.

Ensure you have actually designated the target with the TGP (TDC depress). It doesnt appear the FLIR page displays the diamond, which it would if you designated (and HUD would display the diamond with dot).

[TAW_Impalor]

dorianR666 do you not reproduce this bug, or just assume it's not there? While true that F18 air starts unaligned (what?), this is not what is causing it. I attached more screenshots and encourage everyone to try for themselves!

[dorianR666]

While true that F18 air starts unaligned (what?)

it starts aligned, IFA position chosen from aligned NAV position does NOT mean in-flight alignment but GPS-aided function. if you had it in NAV, it would accumulate drift, which would result precisely at what you experience. which is why i mentioned it. there is someone reporting a bug while having disabled GPS almost every day.

 

found out that designation works correctly by checking with AG radar, its the diamond on HUD which is wrong. i also found out that the HUD diamond goes up and down as you change barometric altimeter's setting.

 

so yes, the bug is confirmed.

[hein22]

Is this really a Syria bug?? So if you change the altimeter in PG the hud diamond won't move?

[hein22]

Ok I tried and it doens't happen in PG. So I guess Syria doesn't have terrain elevation mapped into the hornet DTED, thus depending on altimeter or radalt.

[TAW_Impalor]

Also tested on PG, same observation. I don't know if wrong diamond location on HUD and vertical dependence on baro setting on Syria map are related. The baro setting 29.92 in that mission is correct to weather. Changing it do something else does not make sense, and does not correct the problem. I see diamond displaced horizontally as well as vertically. TPOD gives correct coordinates for GDAMs, for example, so the problem is only with HUD. No idea why.

[BIGNEWY]

Please include the shortest track replay possible to show this issue,

 

thank you

[TAW_Impalor]

Hello. I included a short track where I try to target some warehouses at the end of the pier. In 'cross-hairs' mode on FLIR the HUD diamond is showing above the target. After I do TDC depress the HUD diamond jumps below the target and starts crawling away. The diamond on FLIR is also crawling, so I must constantly correct it until it runs away completely. I did not touch the baro setting in this track, but it also moves the HUD diamond.

flir.trk

[TAW_Impalor]

Why does the title still read '[NEED TRACK REPLAY]'?

[BIGNEWY]

Why does the title still read '[NEED TRACK REPLAY]'?

 

Because I have not got to the report yet.

 

checking now.

 

thanks

 

 

[BIGNEWY]

Thanks for the track, I have already reported this issue and have added your data to the report.

 

thank you