Consecutive M-points cause second M-point to copy coordinates from first M-point when overflying first M-point (and using TRIGGER UNSAFE)

[TOViper]

OB 2.7.10.19402
SP, mission editor

Using two consecutive M-points (target points) when overflying the first M-point causes the second M-point to have same coordinates as first M-point.
In this example, I overfly M1 by attacking a fuel tank on top of the mountain (not replayed correctly on my machine, it was offset), and then M2 has the same coordinates as M1, despite they were differently before taking off. When overflying, M1 should switch to M2 (not B3), because I am not in NAV mode (not in ANF where automatic switching would be inhibited).
 

If you are not able to replay the TRK, just load the MIZ and fly along the waypoints.
 

AJS-37_Viggen_M-points_mixup.trk AJS-37_Training_Nevada_Rb75+AKAN.miz

Edited February 7, 2022 by TOViper

[QuiGon]

I've done both, watching your trackfile as well as playing the mission by myself and in both cases I could not observe what you described.
Instead I saw the waypoint switching from M1 to M2 automatically upon reaching M1 and waypoint M2 was still located in a different place than M1 afterwards (different commanded heading on the course ring and different distance on the waypoint distance indicator was shown for M1 and M2).

See my attached track file of my own attempt:
AJS-37_Viggen_M-points_mixup QuiGon.trk

10 hours ago, TOViper said:

(not replayed correctly on my machine, it was offset)

When recording trackfiles, please make sure to not use fast forwarding, as the use of fast forwarding makes it much more likely that user imputs will be logged imprecisely.

Edited February 7, 2022 by QuiGon

[TOViper]

Replay:

Video:

Edit: It seems the TRIGGER UNSAFE is causing this problem.

Edited February 7, 2022 by TOViper
add info

[QuiGon]

1 hour ago, TOViper said:

Replay:

Video:

Edit: It seems the TRIGGER UNSAFE is causing this problem.

 

Alright, I do indeed see the described behaviour in the video now!

Edit: I flew your mission again and this time I actioned TRIGGER UNSAFE on M1 and the NAV system acted really strange. It looked like it placed M2 on my aircraft position, so whenever I selected M2 it immediately jumped to B3.

Edit2: Short track file of the issue:
AJS-37_Viggen_M-points_mixup QuiGon New.trk

Edited February 7, 2022 by QuiGon

[Machalot]

I was just browsing the manual and found this paragraph on p. 162. Could this explain what you're seeing?

Edited January 19, 2023 by Machalot

[TOViper]

When firing pods in NAV, a target fix for the M-point should be made (this is before overflying the waypoint). After overflying it, the system should switch to the next B-point.
When firing pods in ANF, a target fix for the M-point should be made (this is before overflying the waypoint). After overflying it, the system should stay at that M-point.

What should be checked with the current OB right now is the following:
When NAV is selected and the exact moment has come for the navigation system to switch to the next waypoint, trigger SAFE should be already selected by the pilot.
This should in no case change the coordinates of the next M-point. If it changes, there is something wrong.

 

Edited January 19, 2023 by TOViper

[TOViper]

Mode NAV

It seams only happening when really firing a weapon; I used trigger unsafe without firing the gunpod, and no fix is beeing made (according to manual).
If I really fire the gun, then a fix is made and the waypoint M2 is then at the location of M1. I trigged UNSAFE far before overflying the waypoint.
See TRK.

It seems that the fix is - in fact internally - done after the switch to the next M-point is initiated by the CK.

 

AJS-37_Training_Nevada_Rb75+AKAN_target_fix_problem.trk

Edited January 19, 2023 by TOViper