Ramsay Posted August 20, 2016 Posted August 20, 2016 (edited) Description: DCS crash when Mistral is armed and player dies DCS Version: 1.5.4.55952 Steam: yes Map: Caucasus SP/MP: SP Airframe: SA-342 Mistral Reproducible: yes Step to Reproduce: Create a mission with a Gazelle Mistral (parking hot) Loaded with 4x Mistrals Arm the weapons system with the sight lowered and seeker beep. Arms - on Weapon Panel - on, 2x2 Mistrals loaded/displayed Left and Right Hard Points - Safety covers up and armed Pilot sight - down Mistral seeker tone - beeping Take off and deliberately crash killing pilot and co-pilot. DCS will crash with the windows messageDCS has stopped working A problem caused the program to stop working correctly. Please close the program. ->Close the program Screenshot: N/A Track Available: N/A Controllers: X52 Pro (Throttle), MS Sidewinder FFB2 (cyclic), TrackIR OS: Win 10 Pro RAM: 12GB GPU: GTX 670 2Gb Mods: JSGME all disabled Additional Info: Loading the 4x Mistrals is not enough, the weapons system must on and active. When testing, restart DCS between missions as the damage state can persist i.e. a hot parking Gazelle Mistral spawned with a broken tail and running engine. Repeating the test with a SA-342L does not crash DCS. Turning off the Armament system after activating it doesn't stop the CTD when the player dies Edited August 20, 2016 by Ramsay Tried to find a work around but turning off the armament system when you think you might die doesn't stop the CTD. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Marky3254 Posted August 20, 2016 Posted August 20, 2016 Yes I've been having the same issues as you with the SA-342 Mistral. Also with the weapons system not active, crashes, even relatively minor ones, almost always end in an explosion.
Mt5_Roie Posted August 20, 2016 Posted August 20, 2016 I've noticed it as well that going from the mistral version to another version sometimes causes a crash. So we can collect data, can you guys send us you DCS log along with the crash log so we can look at the info. Thanks. Coder - Oculus Rift Guy - Court Jester
Ramsay Posted August 20, 2016 Author Posted August 20, 2016 (edited) So we can collect data, can you guys send us you DCS log along with the crash log so we can look at the info. I assume you want dcs.log and the matching crash .dmp file. Here's one from just now. A single SA342 Mistral, 2x2 Mistral, 66% Fuel, hot parking @ Batumi, Armament system on, Seeker tone beeping. Take-off, assend to ~20m, roll inverted, crash killing pilot and co-pilot The 3rd person (F2) view of the burning Gazelle doesn't appear, instead a windows error message appears as described in my 1st post Edited August 20, 2016 by Ramsay Add .miz to .zip i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Ramsay Posted August 20, 2016 Author Posted August 20, 2016 After trying various loadouts and switch positions, the common indicator that the CTD will occur is if the missile seeker tone has played sometime prior to the pilot and co-pilot dying. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Mt5_Roie Posted August 20, 2016 Posted August 20, 2016 Seems correct...only once missile system is active does it occur. Testing different situtaions and hopefully will find work around until we can resolve issue. Coder - Oculus Rift Guy - Court Jester
Recommended Posts