reported SPI shifts when FCR GM-lock nearby SAMs emissions

[falconzx]

I had some trouble designating targets with FCR GM (nav master mode) nearby SAMs. Attempts to designate someting (to retreive coordinates for example or performing a nav fix or putting a markpoint), on the same bearing of the SAM station but at slightly different range result in a SPI shift on the exact position/range of the SAM (way more precise than a HTS PGM2 solution... that's the funny part :P)

This is pretty annoying when trying to use FCR to create a fast markpoint in order to POS HARM launch (closer than the target to enlarge the search area of the HARM over the target zone) because of this shift.

Here the track.

 

SPI_moves_FCR_close_sam_emission_FCRdesignation.trk

Edited January 28 by falconzx

[Lord Vader]

Hello @falconzxtruly a strange event.

Reported internally, thanks. 

[pchRage]

1. Setup A2G, GM, CCRP, TGP, CZ on STP that is in general location of AO.
2. Slew GM to near (BUT NOT ON) Target (SA-15 at Wujah in this example) by using HSD to eyeball the area as ref for GM Cursor indicator.
3. Note TGP is aligned to GM SOI and also shows location of GM cursor over "general terrain/water"
4. TMS UP on GM SOI to lock this position over "general terrain/water".
5. NOTE: GM shows proper location locked over "general terrain/water".
6. ERROR: HSD GM cursor indicator now has "JUMPED" over to the SA-15 instead of where the GM is actually locked!
7. ERROR: TGP shows the SA-15 centered in crosshairs (matching the HSD position) and NOT where the GM is actually locked!

Screenshots are Named for the Above Step they relate to (1.png, 2.png, etc)...

Screenshots, Track, and Miz Attached.

LastMissionTrack.trk Test_GM_TGP_Offset.miz

I dont know why it kept showing the LAST screenshot first.. so I removed from main post and have it here so they are in "order"....

Edited yesterday at 05:24 PM by pchRage

[BIGNEWY]

this has been reported

thank you