HSD and HUD showing target at different azimuth

[tekwoj]

Both HSD and HUD show my heading as 313, but HUD shows my target is right from me and HSD shows it to the left. Can't reproduce it at the moment here's a screenshot from when it happened flying multiplayer.

[BigBorner]

On 8/25/2025 at 1:25 PM, tekwoj said:

Both HSD and HUD show my heading as 313, but HUD shows my target is right from me and HSD shows it to the left. Can't reproduce it at the moment here's a screenshot from when it happened flying multiplayer.

I think the AG Radar is screwing with you

Make it SOI and press target unlock in case its acting up again. 

null

[tekwoj]

Target was waypoint, radar wasn't touched. I think it was the HSD that had everything wrong.

[Napillo]

Your AG radar was in snowplow, you should set it to SLV.

[tekwoj]

3 hours ago, Napillo said:

Your AG radar was in snowplow, you should set it to SLV.

The AG radar was untouched, target was either waypoint with tgp slaved or tgp selected. You can even see the waypoint circle in the correct position on the radar. HSD is the only one not in line with the TGP and HUD indicators.

[Napillo]

3 hours ago, tekwoj said:

The AG radar was untouched, target was either waypoint with tgp slaved

I know that, but there's this bug or quirk where the radar will have a target somehow and you have to select that screen and hit the unlock button (backspace).

[tekwoj]

17 hours ago, Napillo said:

I know that, but there's this bug or quirk where the radar will have a target somehow and you have to select that screen and hit the unlock button (backspace).

There's a lot of bugs with radar, but what does it have to do with HSD data being rotated around 20 degrees?

[uboats]

@JG54_NF2

 

any trk to share or video recorded?

Edited August 30 by uboats

[JG54_NF2]

2025/8/25 PM7点25分，tekwoj说：

Both HSD and HUD show my heading as 313, but HUD shows my target is right from me and HSD shows it to the left. Can't reproduce it at the moment here's a screenshot from when it happened flying multiplayer.

Did you do anything before this problem occurred?

[tekwoj]

46 minutes ago, uboats said:

@JG54_NF2

 

any trk to share or video recorded?

No, sorry, it happened in a multiplayer session about an hour or 2 into it. I tried reproducing it but no luck so far.

 

43 minutes ago, JG54_NF2 said:

Did you do anything before this problem occurred?

I don't think so, I'll try to verify, but I think the only thing I did different than usual is during the INS alignment I didn't input heading because it was 000 anyway.

[uboats]

22 minutes ago, tekwoj said:

No, sorry, it happened in a multiplayer session about an hour or 2 into it. I tried reproducing it but no luck so far.

 

I don't think so, I'll try to verify, but I think the only thing I did different than usual is during the INS alignment I didn't input heading because it was 000 anyway.

did you actively set the SPI by either HUD or radar or other sensor or it's just from selecting WPT (i.e. 5 from your screenshot)?

Edited August 30 by uboats

[tekwoj]

22 minutes ago, uboats said:

did you actively set the SPI by either HUD or radar or other sensor or it's just from selecting WPT (i.e. 5 from your screenshot)?

SPI was from a waypoint, then pod slaved to it. 

Here's a screenshot from a bit later when I used WMD pod to set target. HSD situation is still rotated, but less than in the first screenshot.

 

[uboats]

i'm working on it. should be an issue.

[uboats]

@tekwoj please try again in latest update. My operation sequence: manually entered wpt00 coord and then started fast align, once done, loaded DTC.

[tekwoj]

Seems good, I've flown quite a bit lately and didn't see the issue repeat.

[tekwoj]

@uboats

Bad news and good news. Bad news is that the bug? is still there. Good news is I reproduced it and have a track and mission file.

It happens when the plane is cold started with heading 000, but the pilot is too lazy to enter 000 during nav align because the heading field is already set to 000.

The mission file already has the 2 waypoints added so they don't have to be input by hand like I do in the tracks.

The jf-17-000-heading-ok.trk shows that behavior is ok if I input the 000 heading during nav align.

17-nav-test2.mizjf-17-000-heading.trkjf-17-000-heading-ok.trk

Edited October 7 by tekwoj

[uboats]

On 10/8/2025 at 5:26 AM, tekwoj said:

@uboats

Bad news and good news. Bad news is that the bug? is still there. Good news is I reproduced it and have a track and mission file.

It happens when the plane is cold started with heading 000, but the pilot is too lazy to enter 000 during nav align because the heading field is already set to 000.

The mission file already has the 2 waypoints added so they don't have to be input by hand like I do in the tracks.

The jf-17-000-heading-ok.trk shows that behavior is ok if I input the 000 heading during nav align.

17-nav-test2.miz 8.8 kB · 1 download jf-17-000-heading.trk 4.85 MB · 1 download jf-17-000-heading-ok.trk 2.5 MB · 1 download

thanks for your time and patience. i will check it.

just returned from a long trip for friend's wedding. recovering.