Opesher

Hey. I recall this happening to me and thanks to your thread I remembered it. This works if you have ever entered any A/G radar modes. So, when you switch main modes while your FCR is in AGR, it will remember the radar mode in prior to AGR and return to it when you switch weapon mode. But that breaks when you switch to another master mode because it replaces whatever radar settings you had before entering AGR (GMT -> RWS for example). It works with any weapon and even with HUD mark (as it forces FCR into AGR mode). F-16 GP bombs and aa radar modes.trk F-16 GBUs and aa radar modes.trk F-16 HARM and aa radar modes.trk

There's nothing unusual, think of your FCR and datalink as these are two separate entities. Onboard FCR still has to go through the whole process to generate it's own track data - detect (search target), sweep for a little and generate track data (track target), the only difference datalink provides is correlation between your detected contact and an already existing track data of that contact of a donor for situation awareness, not for a firing solution. That's when filtering comes in place, so you can see your own contact state behind shared data.

Hello. To put it into two cents and make response useful to other people who may read this, I will get into some context. As for "not functioning at all" and "cannot see which targets are buggable or not" is not true a bit in my case. I see a lot of people having troubles with understanding difference between your own onboard tracks and datalink tracks (not to blame), and that's probably the issue you and the person above are having. To not play the "guessing game", there is a datalink data filter for your FCR, and the current setting is displayed above OSB15. You can either cycle through the options with IFF IN or disable all datalink tracks with IFF OUT. - ALL: Show all datalink tracks. - FTR+: Filter out all surveliance datalink tracks. - TGTS: Filter out all surveliance and PPLI (donor) tracks. - NONE: Filter out all datalink tracks. That's a good practice to keep general situational awareness with FCR set to ALL and HSD, but switch filter to FTR+/NONE prior to engagement to actually know what your radar actually sees. It will be still correlated on HSD display, so just crosscheck it. Let's have an example: 1. AWACS detects a contact. 2. Determines either this contact is hostile, ambiguous or friendly. 3. Sends the data over datalink. 4. You receive that data (in this example, a hostile aircraft, indicated by a hollow red triangle on fcr and hsd pages). When you point your radar in the direction of the target, the red triangle changes to a yellow box, and that's where many people start having problems: -- Yellow: Means target is ambiguous. Although surveliance/donors have declared the contact hostile (red), it's still unknown (white) to your own FCR. -- Box: Indicates track data received from a datalink source. It's not your FCR track data! Even if it's correlated, it may still be a search target. This only means that whatever radar return you had at that position has been correlated to datalink track data. In this scenario, unless you apply a filter, you can't know the status of the contact - search target or track target.

This seems to be intentional. The change came with latest openbeta update. To avoid CAQ and BAM result in unfrozing, simply select FRZ before you enter PAN mode. Fixed: TSD FRZ should be disabled when CAQ or BAM are exited if FRZ was not selected prior.