tiny dagger
Right now, an EF24 using SAS will only update the existing enemy track ID rather than creating a new trackfile, even when contact is broken and reappears elsewhere as a different plane.
As noise is much less effective against 5th gen with their multiple data sources, SAS could be a neat way to confuse the TSD.
Would also be good if the TSD didn't rely on magic as much to determine between new/existing targets.
flint yoke
Yesss
snow shale
I assume this would also break datalinked 120D's when creating false TSD tracks
if so
I'm 1500% into this idea
tiny dagger
If the 45 fired on a 24, then the 24 swapped to SAS, the 120D would follow the dead 24 track until the 24 stopped using SAS or is otherwise identified
tiny dagger
I'm not sure how it would handle conflicting data. Right now the game sort of strobes the target ID but won't create new tracks if two radars report conflicting data
desert quiver
gimme a [delete track] button for the TSD then
tiny dagger
Yeah. 120Ds might need a way to retask too
Alternatively, track ID does update if SAS is turned on without breaking lock. If the 24 breaks track then reappears as a new target, new track
snow shale
I think if we want SAS to create new trackfiles, and then have AIM120D's not follow that new trackfile, that would probably require adding in code that could hypothetically allow AIM120D's to be retasked mid flight if baha wanted to add that too
somber valve
Right now, an EF24 using SAS will only update the existing enemy track ID rather...
Would also be good if the TSD didn't rely on magic as much to determine between new/existing targets.
Imo this is the biggest/most important one, DRFM is trivially defeated by just selecting the real contact initially, or because the real contact behaves differently. Making the TSD have ambiguity with nearby tracks/messy stuff would add a lot of realism/depth and aid with jamming being more fun an effective
somber valve
I suggested awhile ago that it inherrit the radar crown status but alas
