Ahmed Posted August 25, 2020 Posted August 25, 2020 Hi, I think I reported this long ago but it got marked as reported for a different reason, and not exactly this one. The RWR does not give 'spurious' launch warnings when the player is not the target, even if the player is flying fingertip with the target (that's not fingertip on the track I know). It does, however, give spurious lock warnings. The RWR seems ot be coded to magically know who the target is in case of a missile launch, even if the player would be within the resolution cell of the radar. This likely applies to other modules as well. Regards,rwr.trk
ED Team BIGNEWY Posted August 25, 2020 ED Team Posted August 25, 2020 Hi As far as I am aware this is not a bug, the beam should be very tight on the locked target. thank you 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
Ahmed Posted August 25, 2020 Author Posted August 25, 2020 (edited) Deleted Edited August 30, 2021 by Ahmed
GGTharos Posted August 25, 2020 Posted August 25, 2020 (edited) Hi As far as I am aware this is not a bug, the beam should be very tight on the locked target. thank you Hi BIGNEWY, While I realize that this may not actually be a bug (as in the software works as intended), the relevant information is as follows: 1) The beam is commonly defined as 1+ degrees depending on the radar, which covers about 17m/deg/km. At 50km distance it will have a diameter of about 850m with just a 1deg beam. A lot of older radars, especially certain SAMs, have beams as wide as 4-8 degrees. 2) The width of the beam a the mathematical definition based on RF density/power fall-off. You're still getting a lot of power outside of the mathematical definition of the beam, and the received power at the RWR would have to be calculated. Right now it's not calculated at all IMHO, it's basically 'I've locked onto object ID x, send him the you're locked and launched on flag' So the physical RF simulation is fairly lacking in this case. I still wouldn't call it a bug because the software works as intended, but it would be very nice to push up the level of emission simulation (not just RF). Edited August 25, 2020 by GGTharos [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
Ahmed Posted August 25, 2020 Author Posted August 25, 2020 Thanks GGTharos for the insight! Yes, my point precisely is that there is no way currently in DCS of flying into the beam and getting the spurious missile launch warning. The RWR seems to be hardcoded to just trigger the launch warning if the aircraft is the target, while in the past it seemed to be simulating and area around the beam and triggering the launch warning on other players flying into it.
ED Team BIGNEWY Posted August 25, 2020 ED Team Posted August 25, 2020 Thanks for the info, I will ask the team 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
Ahmed Posted October 31, 2020 Author Posted October 31, 2020 Hello Bignewy, Any news on this? After some further research, if the RWR in DCS discriminates between search and lock even if the player is not the target, it should certainly discriminate too between lock and launch even if not target. Currently the RWR while trigger a lock warning in a very wide sector (if not omnidirectionaly, didn't test enough), however it only triggers a launch warning if the player is the target. A lock and launch warning should be triggered if the player is close enough to the beam. While specifig guidance methods and specific systems will have different characteristics, the general explanation and rough numbers given by GGTharos agrees with all available public data on the simulated systems. Again, I report is a bug because in the past DCS worked this way and spurious launch tones were triggered (just maybe in a too wide area), while at some point it stopped doing it for the launch tones, so it may have been an overlook in some update.
Recommended Posts