DUSTY Posted April 12, 2019 Posted April 12, 2019 (edited) So in the change log: New: Added radar beam structure emulation to the RWR. Since this update I've done most of my flying in the Buddyspike Blue Flag PG server and I've noticed being spiked by hostile HAWK SAMs but when they launch there is no launch indication from the RWR like there used to be. Is this to be expected or has the RWR been 'nerfed' a little too much? Cheers! Edited April 14, 2019 by IronMike F-15E | AH-64 | F/A-18C | F-14B | A-10C | UH-1H | Mi-8MTV2 | Ka-50 | SA342 | Super Carrier | Nevada | Persian Gulf | Syria | Intel Core i7 11700K - 32GB 3200MHz CL16 DDR4 - MSI GeForce RTX 3060 Gaming X 12GB - Samsung 970 EVO Plus NVMe SSD 1TB
mattag08 Posted April 12, 2019 Posted April 12, 2019 Also, are all aircraft now supposed to show a "U" indication if they are enemy? Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights! I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII
Super Grover Posted April 12, 2019 Posted April 12, 2019 (edited) Hey! Thanks for reporting your observations. @|DUSTY| I've checked HAWK online, and indeed sometimes it gives no launch indication. I investigated it further, and it looks that sometimes in multiplayer you can be tracked by multiple subsystems of one SAM system. In such a situation, the first strongest locking subsystem may be not the subsystem engaging you with a missile, and we are checking for the missiles guided from the strongest lobe. I've corrected this by checking all subsystems and not only the strongest one. Should be available in the next update. Side note: "sometimes" in my case was 10-20%. For 80-90% it gave correct indications. @mattag08 Now, "U" should appear only for some unknown types, not in the database. I checked it online and offline today, using the latest open beta, and it worked correctly. However, I found that the HAWK CWAR radar wasn't in the database, so I added it. I think that multiple "U" you got was because of the mission (maybe spammed with CWARs ?) and not the RWR. Edited April 12, 2019 by Super Grover Krzysztof Sobczak Heatblur Simulations https://www.facebook.com/heatblur/
DUSTY Posted April 13, 2019 Author Posted April 13, 2019 Thanks Super Grover, you're a champ! F-15E | AH-64 | F/A-18C | F-14B | A-10C | UH-1H | Mi-8MTV2 | Ka-50 | SA342 | Super Carrier | Nevada | Persian Gulf | Syria | Intel Core i7 11700K - 32GB 3200MHz CL16 DDR4 - MSI GeForce RTX 3060 Gaming X 12GB - Samsung 970 EVO Plus NVMe SSD 1TB
SpicyMiG Posted April 20, 2019 Posted April 20, 2019 Hey Grover, we just experienced an issue and wanted to let you know of a different situation in which this can happen, since it hasn't been mentioned already. First, we had a two-flight of Tomcats engaging two MiG-31s. We had a lock tone, but neither of us ever got a launch tone from the two R-33s that were fired at us. Later, we had a Tomcat shot down by a 9M33 Osa (SA-8 Gecko) which never received lock or missile lock warnings from the RWR. They were just cruising above the AO lasing targets and exploded. Will attach Tacview when the mission is finished.
Recommended Posts