RPY Variable Posted August 30, 2022 Posted August 30, 2022 (edited) FCR does not display datalink aircraft, it also doesn't display search targets (white dots). But if you press TMS UP (aiming the cursor via de FCR cursor mirror on HMS over a datalink target) and lock a target, it will bug a target and then show the appropriate symbiology and it will also STT. But if you are not lock at something, the radar just wont show anything. Edit: the datalink must have been the IFF OUT button. But wouldn't explain the missing white dots. Edited August 30, 2022 by RPY Variable Interl i7 6700k - 32Gb RAM DDR4 - RX 590 8GB - Sentey 32"2560x1440 - Saitek X-55 - TrackIr 3
Tholozor Posted August 30, 2022 Posted August 30, 2022 (edited) You have the FCR filter set to FTR+, change it to ALL. Edited August 30, 2022 by Tholozor 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
RPY Variable Posted August 30, 2022 Author Posted August 30, 2022 That seems to be the datalink targets missing. My fault. But still... it was not showing the search targets as well. I shot down two bandits by blind TMS up on a known location. Targets like 15 nm away. Even the AWACS was invisible to the FSR. And it was on a look-up attitude at 15 miles. Only visible by bugging him via TMS up on known location via HSD FSR cursor mirror. Interl i7 6700k - 32Gb RAM DDR4 - RX 590 8GB - Sentey 32"2560x1440 - Saitek X-55 - TrackIr 3
Fortinero Posted September 6, 2022 Posted September 6, 2022 (edited) I can replicate this behavior using any FCR filter instead "ALL", so you will be unable to see any radar contact (white bricks) when FTR+, TGTS, or NONE is selected. Edited September 6, 2022 by Fortinero
AvroLanc Posted September 16, 2022 Posted September 16, 2022 On 9/6/2022 at 3:23 PM, Fortinero said: I can replicate this behavior using any FCR filter instead "ALL", so you will be unable to see any radar contact (white bricks) when FTR+, TGTS, or NONE is selected. Yeah this is clearly not how the real thing should work. THe FTR+, TGTS and NONE filters should be filters for the datalink portion of the track only. The raw ownship radar contacts should be present ALL of the time. In no way should those filters actually filter out the radar returns. 1
ED Team BIGNEWY Posted September 16, 2022 ED Team Posted September 16, 2022 15 minutes ago, AvroLanc said: Yeah this is clearly not how the real thing should work. you have public evidence of this? Please PM me Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
AvroLanc Posted September 16, 2022 Posted September 16, 2022 3 hours ago, BIGNEWY said: you have public evidence of this? Please PM me Ok, so I’ve been through my reference ( prob same one as you guys are using), and can’t specifically find a sentence that says ‘raw FCR targets are displayed whatever the declutter level’. I think that is just presumed, since it is just common sense. The ALL, FTR+, TGTS, NONE options are datalink display options…i.e datalink…. They should not remove ownship radar contacts…even if that track is correlated with a datalink track. The NONE option should just remove the datalink colour overlay for that track, leaving behind the raw search/system track. Currently a correlated search target will disappear completely with the wrong declutter which is…dangerous. It wouldn’t be designed this way. There is actually a diagram that illustrates this, but admittedly doesn’t explicitly describe the behaviour. This is one of those examples where ED’s 20+ years of experience simulating this stuff should aid in interpreting the correct function. 1
Recommended Posts