reported Marpoint problem using HAD & TGP

[Bricux]

Dear ED Crew,

There is a problem with how the creation of a new Markpoint works. When press ICP 7, MARK DED menu appears. Default sensor for MARK is HUD, while pressing ICP 7, even when you have another SOI, MARK causes to set HUD as your SOI. In my mind MARK shouldn't ever have HUD as default SOI because it making HUD as SOI.

Examples:

1. Plane in NAV mode. Left MFD AA RDR, Right MFD HSD. Left MFD (AA RDR) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK and RDR set in AGR mode, and HUD as SOI generally. It's bad. (Doesn't appear in Plane AA mode [MARK default setting is OFLY]).

2. Plane in AG mode. Left MFD AG RDR, Right MFD TGP. Left MFD (AG RDR no lock) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK and RDR set in AGR mode, and HUD as SOI generally. (Doesn't appear when You lock SPI in AG RDR). It's bad.

3. Plane in AG mode. Left MFD AG RDR, Right MFD TGP. Right MFD (TGP no lock) is SOI. Pressing ICP 7 MARK causing to set TGP as SOI for MARK. It's good!

4. Plane in AG mode. Left MFD HAD, Right MFD TGP. Left MFD (HAD) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK, and HUD as SOI generally. It's bad.

5. Plane in AG mode. Left MFD HAD, Right MFD TGP. Right MFD (TGP) is SOI. Pressing ICP 7 MARK causing to set TGP as SOI for MARK. It's good! 
BUT! You create new MARK, and You try to TMS DOWN to switch SOI (to unlock HAD, w/o closing DED MARK page) causing to set TGP as SOI for MARK, and HUD as SOI, causing TGP to crazy.

Generally You can' switch SOI from TGP to HAD with MARK DED page open.

MRK_HUD_BUG.trk

Post scriptum: when MARK set Your HUD as SOI every weapon switch to VIS mode. What it's generally good but not with this problem described above.

[Frederf]

There are some fundamental issues with current mark implementation:

• Mark mode overrides sensor selection control so in all mark modes SOI cannot be moved. Sensor is changed with DCS SEQ. In OFLY mode there is no SOI.
• HMCS mark is an extension of HUD mark mode by TMS long press.
• As the mark mode rotary is changed the SOI and sensors are reconfigured automatically. E.g. HUD mark temporarily overrides FCR to AGR only as long as mark mode is HUD submode. When mark mode is not HUD submode the temporary override ends.
• If sensor (all types but OFLY) mark is attempted in A-A modes (AA, MO, DGFT) then OFLY mark is the result. I.e. position recorded is according to the OFLY logic regardless of appearance. Sensor marks can be done in NAV and A-G modes.
• Sensor marks in A-G visual submodes (CCIP, DTOS, EO-VIS, EO-BORE, strafe) result in mark at current steerpoint (i.e. SPI location).
• When in any mark mode the "RDY" SMS indication must be suspended and weapons release is impossible (including cannon).
• When sensor is SOI and non-tracking TMS forward must not create a mark point. E.g. FCR first TMS causes track, second causes mark point record.
• For HUD marks in AG preplanned SPI is set using the HUD. Mark slews are erased and the SPI returns to the previous location when mark is exited. This applies to FCR GM marks as well, any slewing in mark mode is reverted to those that were in effect as when entering mark mode upon exit.

I also notice that TMS aft in non-HUD mark mode (and when HUD is not SOI) is doing odd things to the HUD. During HUD submode some TMS aft results in mark symbol changing into target designator square symbol instead of the mark circle.

[desertowl]

Following Frederf report, please find attached a track file showing erroneous markpoint DED behavior. 

1. Left MFD set as TGP, Right MFD as HAD

2. "Markpoint" screen selected

3. DMS pressed down, TGP is selected as SOI 

4. DMS pressed down again, HAD "blinks" as SOI momentarily and immediately deselected - cannot be SOI until exiting markpoint DED screen 

mark_HAD_bug.trk

[[ED]Ben]

19 hours ago, Bricux said:

In my mind MARK shouldn't ever have HUD as default SOI because it making HUD as SOI.

HUD is the default SOI if the TGP or FCR are not tracking.

HAD is not a valid source for mark mode, but you should be able to select as SOI - this is known issue. 

 

Thanks!

[Bricux]

But pressing MARK shouldn't cause changing SOI (even if that screen is not displayed e.g. AGR).

And problem is when You change SOI when MARK DED page is displayed, causing setting HUD as SOI even if TMS DOWN was used.

Edited November 22, 2021 by Bricux

[[ED]Ben]

Yes you are correct on the SOI - the auto SOI selection bug is reported, and we are working on it. 

Sorry i did not make that clear in my first reply.