reported earlier Radar locking own fox 1

[Guericke]

The hornet radar is locking it's own missile when jumping from TWS or RWS to STT using trigger to fire Aim-7. No track needed, it's a easily reproduced issue. This cause you having to go STT before launching, not being able to let the plane go STT itself when firing the Aim-7.

[MARLAN_]

I think the issue lies with RAID 1LOOK is broken. I haven't got around to reporting it yet.

[BIGNEWY]

This has already been reported earlier. 

 

There should be some possibility to lock missiles, but it does need some tweaking. 

 

thanks

[Harker]

Regarding this thread:

I would like to point out that the radar should not be jumping between contacts uncommanded, since it should employ target range, Doppler, heading etc filters, in order to maintain the intended contact.

 

A switch like that should only be possible to occur (if it occurs at all) if both are in the same resolution cell (not modeled in DCS, AFAIK) and have extremely common characteristics when the switch occurs. The radar could be confused, merge them into one contact and then pick the wrong target when they break apart (i.e. being far away, smaller RCS targets flying in very close formation, initially being picked up as a single contact, with larger RCS). As such, an outgoing missile would never be confused with a fighter, for example and even if it entered the STT beam, it would be rejected immediately by the radar.

Apologies for referencing another bug post, but it was locked before I could comment. I'm just putting this out there so that, when devs go to fix this issue, they are aware of the intended final behavior, so they wouldn't need to possibly revisit this in the future. @BIGNEWY, feel free to merge the two threads. This isn't new information BTW, @GGTharos has already spoken about this in several threads, in good detail. I just wanted to put it out there.

Thanks.

[Ahmed]

Range/Doppler gates should prevent locking own missile indeed. Resolution cell modeling would also benefit other stuff such as RAID modeling.

[MARLAN_]

RAID 1LOOK seems to trigger this issue consistently as well, with RAID 1LOOK enabled you will often find yourself STT'ing your own missile, or bandits missile.

 

I would guess any time it attempts to do a RAID look during STT, it's causing you to temporarily lose lock for about half a second, but the radar memory is unable to lock the original target and just picks something at random.

Edited August 30, 2021 by MARLAN_

[Harker]

13 minutes ago, MARLAN_ said:

... but the radar memory is unable to lock the original target and just picks something at random.

 

It seems this is what is happening. The radar does not retain memory of the STT target, but of course it should.

Although this is not directly related, another thing currently compounding this behavior in DCS is the fact that STT causes MSI processing to stop in DCS, whereas it shouldn't (it should only stop in ACM and when in A/G mode). So, while the radar shouldn't need MSI, since it should employ gates, retaining the correct target becomes even easier, since all the radar has to do is focus on a particular MSI trackfile. This should become better once MSI is sorted out and we get actual MSI trackfiles, correct MSI sensor contribution logic and we can differentiate between radar and non-radar MSI trackfiles.

Edited August 30, 2021 by Harker

[Jak525]

Please listen to Harker, everything he is saying is entirely correct and important.

 

In other words: regardless of any debate over whether the radar can see missiles or dust particles or raining cats, it is not going to accidentally acquire ANYTHING that is not similar or identical to the commanded target of acquisition, with respect to range, bearing, direction, and closure rate.