umkhunto Posted February 4, 2020 Posted February 4, 2020 (edited) I think I've encountered a bug in the Tomcat, where the MiG-31 doesn't give a launch warning for the R-33, which it is supposed to. I tested it with several playable modules, where it worked as it should. Included is a link to a video showing the behavior and attached is the mission file. 31test.miz Edited February 6, 2020 by umkhunto
IronMike Posted February 7, 2020 Posted February 7, 2020 Thank you! I will take a look. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
umkhunto Posted March 31, 2020 Author Posted March 31, 2020 Hi, Just wanted to touch base and find out if there's been any progress with this issue.
umkhunto Posted April 13, 2020 Author Posted April 13, 2020 Hey IronMike, were you able to confirm this issue? I would just like to know if it is getting looked at.
Jonne Posted April 14, 2020 Posted April 14, 2020 The R-33 is not a simple standard SARH missile, so I would just throw in, that maybe the F-14 is correct and the other two are wrong? [sIGPIC][/sIGPIC]
Golo Posted April 14, 2020 Posted April 14, 2020 True, R-33 is Russian equivalent of AIM-54, depending on the launch profile it can be FOX1 (SARH), or FOX 3 (datalinked with active terminal radar homing).
sLYFa Posted April 14, 2020 Posted April 14, 2020 Do you have a source for that? Because all information I found(both in english and in russian) state that the R-33 is INS+SARH. ARH was considered during development but was dropped in favor of a cheaper SARH system. The RWR behaviour is indeed stange. Sometimes you get a launch warning and sometimes only a lock warning despite a missle inflight towards you. Sometimes I only got 31 ticks on the RWR, despite the missile still tracking me. i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD
AG-51_Sabot Posted April 14, 2020 Posted April 14, 2020 Hey IronMike, were you able to confirm this issue? I would just like to know if it is getting looked at. I think Mike is "out of pocket" for Family "There is an art … to flying. The knack lies in learning how to throw yourself at the ground and miss." Douglas Adams, The Hitchhikers Guide to the Galaxy https://www.cag-51.org/contact
mattag08 Posted April 20, 2020 Posted April 20, 2020 FYI, this is appears to be an issue with all semi-actives. R-27s have been doing this for 2 patches now. 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
nukemgood Posted June 12, 2020 Posted June 12, 2020 This issue occurred again today and doesn't appear to be fixed. Just got shot down without any RWR warning. The whole time I was only spiked by the Mig-31. Curiously enough, the radar did show something incoming...perhaps TWS actually picked up the missile, but I died shortly thereafter.
Noctrach Posted June 12, 2020 Posted June 12, 2020 This is not an F-14 specific issue. II've had this with a lot of other modules (F-15, F-5, F-16, Su-27, Su-33...) for more than 2 years now, even filed bug reports about it in the past but no dice. I think it has something to do with the fact that that the R-33 is supposedly SARH with ARH terminal homing, but supported by a PESA radar on the MiG-31. PESA should have reduced emissions compared to mechanical radars, but still generate all of the familiar warnings. There's some major jankiness in how this is simulated somewhere, resulting in missing RWR warnings.
Bruce_D Posted June 14, 2020 Posted June 14, 2020 Are you guys with your ECM on during the encounter?
Recommended Posts