correct-as-is I think this could be a bug Datalink Contacts supplied via datalink visible on the HSD Page aswell are not visible on the FCR Pages aswell as any tracks. They can still be bugged but are invisible

[Mareno]

I cannot provide a tacview as I have only seen it happen on public servers so far (so tacviews are longer than 5minutes)
 No mods or anything. I had this happen now 4 times since release of the latest OB patch and friends of mine complained about the same.

With tracks I mean buggabble contacts in rws mode

[BIGNEWY]

Hi, 

if possible please include a track replay example that we can check. 

thank you

[Mareno]

The trackfile is 15 minutes long do you want it anyway?

Edited October 31, 2022 by Mareno

[BIGNEWY]

sure, but it maybe to big to attach here, try using drop box, or goggle drive and link it if possible

[Lord Vader]

Hello @Mareno

Can you please return to the same condition and cycle between your datalink filters? (By observing above OSB15, pressing HOTAS Comm switch aft with FCR as SOI)

It looks like you're filtering your FCR tracks to TGTS (targets) only. 
Also, you should wait a few seconds for Link 16 to populate information after you switch filters.

Please let us know if that's the case.

[Mareno]

Hello @Lord Vader
Are you sure you mean OSB 15?
To my knowledge thats the switch to "SWAP" the page on the left MFD with the page on the right MFD.

Edited October 31, 2022 by Mareno
To tag the dev so he sees the response

[Lord Vader]

You are correct, my phrase was truncated. 
It should be: By observing the text above OSB15 and pressing HOTAS Comm switch aft with the FCR as SOI.
Thanks for your note. Edited my reply.

[Mareno]

Am 31.10.2022 um 14:33 schrieb Lord Vader:

You are correct, my phrase was truncated. 
It should be: By observing the text above OSB15 and pressing HOTAS Comm switch aft with the FCR as SOI.
Thanks for your note.

I checked it was indeed not a bug but a mishap by me. Just as a headsuo though: The Switch is called IIF IN and IIF AFT in DCS Controls was quite confused while searching for a comms switch

 

[John Galt]

If you don't mind me asking, I have my IFF in programed for Link 16 transmit, what do you have IFF out programed to that deals with Link 16?

[Lord Vader]

22 hours ago, Mareno said:

I checked it was indeed not a bug but a mishap by me. Just as a headsuo though: The Switch is called IIF IN and IIF AFT in DCS Controls was quite confused while searching for a comms switch

 

It is called the Comms Switch on the HOTAS. The functions you described are just the written labels on the switch, it operates various functions. It depends if you short press or long press and what system is SOI (see below).

[Lord Vader]

18 hours ago, John Galt said:

If you don't mind me asking, I have my IFF in programed for Link 16 transmit, what do you have IFF out programed to that deals with Link 16?

Comm Switch Forward - Data links AG FCR cursor position (FCR as SOI) or Datalinks selected groundpoint (HSD as SOI)
Comm Switch Aft - Data links AA (holding for more than 1/2 seconds) or cycles filters for data link symbology (pressing for less than 1/2 seconds).

[John Galt]

Thanks LV for that but where in the controls menu is "data link aa" or data link ag" so I can assign my switch. Thanks again for your help.

[_SteelFalcon_]

12 minutes ago, John Galt said:

Thanks LV for that but where in the controls menu is "data link aa" or data link ag" so I can assign my switch. Thanks again for your help.

It is called comm switch IFF IN and Comm Switch IFF Out as far as i remember. Just type „iff“ in the search bar and they should pop up

[Fortinero]

Anyways, the comm switch cycles through the D/L filters for the FCR, why in TGTS or NONE you can't get any radar return and see the bricks? But able to TMS UP and bug a target in the FCR page as SOI looking at the D/L HSD contacts, it makes no sense.

Edited November 3, 2022 by Fortinero

[_SteelFalcon_]

2 hours ago, Fortinero said:

Anyways, the comm switch cycles through the D/L filters for the FCR, why in TGTS or NONE you can't get any radar return and see the bricks? But able to TMS UP and bug a target in the FCR page as SOI looking at the D/L HSD contacts, it makes no sense.

 

So you‘re saying that when filter is set to NONE or TGTS and i use the HSD symbology that shows my rdr cursor as a guide and move the cursor over a bandit (while FCR SOI) and TMS up, i can basically bug a target on a blank FCR page? That sounds funny

Edited November 3, 2022 by _SteelFalcon_

[_SteelFalcon_]

track added. Is that really "correct as is"? note how despite the FCR not showing anything depending on the filter that i deliberately chose, i am still able to lock targets by using the FCR cursor symbology on the HSD as aguide to slew the FCR cursor over the targets (while FCR SOI).

does the filter really only affect displayed symbology? why would one use a filter to "filter out" unwanted stuff, but knowing that if one is not precise enough with the cursor, it might still lock some hidden thing nearby?

how do those filters work (besides the obvious change in displayed symbology)? Do they affect trackfiles at all?

FCR Filter Target locking.trk

Edited November 4, 2022 by _SteelFalcon_

[BIGNEWY]

Hi, yes the team have checked it is correct as is

thanks

[Fortinero]

16 hours ago, _SteelFalcon_ said:

So you‘re saying that when filter is set to NONE or TGTS and i use the HSD symbology that shows my rdr cursor as a guide and move the cursor over a bandit (while FCR SOI) and TMS up, i can basically bug a target on a blank FCR page? That sounds funny

 

Yeah, once at home I will record a track file.

[Fortinero]

1 hour ago, BIGNEWY said:

Hi, yes the team have checked it is correct as is

thanks

"Positioning the switch outboard short (less than .5 sec) selects NONE and removes all datalink tracks. Selecting outboard short again returns to the previously selected filter option."

That's the description of the filter NONE, what we get in game now is that not only the datalink tracks are removed but also the radar returns, so, what's the use, or the partical functionallity of this filters? Common sense says that in the FCR page I can remove the symbols that the D/L provides, that also are shown in the HSD page, but why I would want remove also the little radar contact bricks returns?

[_SteelFalcon_]

@NineLine can this be checked again? The early access manual states on page 162/163:

„Positioning the switch inboard short (less than .5 sec) rotates between three filter options:

• ALL. All symbols are displayed

• FTR+. Surveillance tracks are removed

• TGTS. Surveillance and PPLI tracks are removed

Positioning the switch outboard short (less than .5 sec) selects NONE and removes all datalink tracks.

Selecting outboard short again returns to the previously selected filter option.“

nowhere does it say that raw radar hits/bricks are removed. Only that datalink info is being removed depending on the selected filter.

currently (at least on OB) it doesnt even display the raw radar bricks. But it somehow detects them anyway since you can lock non-displayed contacts on the fcr as demonstrated in my previous track with a little help using the HSD.

i believe the bug currently is, that raw radar hits are not being displayed correctly when certain filters are active.

[Fortinero]

On 11/6/2022 at 9:11 AM, _SteelFalcon_ said:

@NineLine can this be checked again? The early access manual states on page 162/163:

„Positioning the switch inboard short (less than .5 sec) rotates between three filter options:

• ALL. All symbols are displayed

• FTR+. Surveillance tracks are removed

• TGTS. Surveillance and PPLI tracks are removed

Positioning the switch outboard short (less than .5 sec) selects NONE and removes all datalink tracks.

Selecting outboard short again returns to the previously selected filter option.“

nowhere does it say that raw radar hits/bricks are removed. Only that datalink info is being removed depending on the selected filter.

currently (at least on OB) it doesnt even display the raw radar bricks. But it somehow detects them anyway since you can lock non-displayed contacts on the fcr as demonstrated in my previous track with a little help using the HSD.

i believe the bug currently is, that raw radar hits are not being displayed correctly when certain filters are active.

Mate, it seems we're not going to have any answer even as logical it sounds from our point of view, at least, we could get an explanation of what's the functionality of this, cuz I can't find it, "correct as is" is a nonsense feature of the jet.

[_SteelFalcon_]

5 minutes ago, Fortinero said:

Mate, it seems we're not going to have any answer even as logical it sounds from our point of view, at least, we could get an explanation of what's the functionality of this, cuz I can't find it, "correct as is" is a nonsense feature of the jet.

Nah dont worry, i figured it wont be seen in a post with that tag already.

The function of the mids filters can be found in some of the frequently mentioned documents about the viper and none of the descriptions there say that raw radar data should be removed. They only affect DL information

i got u

 

Edited November 11, 2022 by _SteelFalcon_

[Comrade Doge]

Still present in the latest openbeta, the radar bricks are removed, but they still can be locked even though invisible, if you guesstimate where they should be. Attached trackfile.

F16Filter.trk

[Frederf]

FCR-LINK 16 CORRELATED TRACKS are displayed with DISPLAY LEVEL:

• ALL
• FTR+
• TGTS
• NONE

The correlated tracks should be displayed with the NONE display option selected.