Solved [BUG OR FEATURE] MARK Mastermode FCR
-
During some testing of the MARK Mastermode I found with the help of some fellow pilots, that the FCR in GM is not scanning while in MARK.
The antenna azimuth marker stops moving from left to right and freezes in the center, also the radar picture does not update while in MARK Mastermode.Is this a bug or a feature?
-
Seems odd. What sensor is selected for marking?
-
The FCR is SOI.
-
@Frederf
Here’s a screen recording of the feature/bug:
https://www.dropbox.com/s/mpi3d78ucmh4b2g/Video_2022-08-02_133916.mp4?dl=0Edit:
All done in NAV mode. I didn’t try in AG or AA mode. But I expect the same there.
This behavior was introduced with 4.36.0. -
From what I’ve read it should not be possible to SEQ the markpoint rotary to FCR until in a ground mapping mode. In your video you set GM before ICP Mark but the cursors are outside of the 60 degree PPI zone when FCR mark is sequenced to. This creates a bug where the FCR is beyond limits and then FCR mark is entered and it doesn’t know how to resume normal behavior. Simply changing MM and back doesn’t inhibit the radar this way. If you have the cursor in the PPI zone when selecting FCR mark you don’t get this. But there is buggy behavior while turning and occasionally providing cursor inputs in FCR mark mode. The cursors jump and jump more the more turning has been done since the last cursor input.
I just noticed this forum software does not allow underlined text… hilarious.
Anyway, if you put FCR GM, turn around so cursors are outside the PPI region, and then set MARK FCR mode you will get this behavior. A quick flip into MO/DGFT override and back will fix it. I think I’ve had this behavior in not mark mode too where GM FCR gets confused and stops updating.
Even when FCR GM is canning in FCR MARK you get these sizeable cursor jumps on minimum slew input after changing heading by a bit.
-
@Frederf
Sorry but there is no cursor jump. The screen record is at 20 fps. The cursor moves without any jumps.
The issue is that the GM radar doesn’t update after selecting the FCR Mark page.
The work around for this issue is to go to the FCR Mark page first and the select the GM mode. -
I did my own test and it does jump on my end. It was just another thing. I see what you’re talking about. Anyway, I only get the behavior from your video if I switch to mark while the cursors are off the map like that.
-
During my testing to confirm the behavior, I also got the issue with the cursor on the STPT straight ahead in front of the jet.
So I assume the PPI isn’t a factor. -
Was able to repro.
Culprit, is NAV mode.
If you change the AA FCR to GM while in NAV mode and select TGP or FCR mark, the AG FCR stops scanning in azimuth.Works fine in AG mode
-
I will make another little videoclip and as we identified this behavior as a bug, I also will file s complete bug report accordingly and link to it here.
-
-