itye1970 Posted February 5, 2016 Posted February 5, 2016 Module DCS: Flaming Cliffs 3 Game version DCS World 1.5.x Message When creating a fast mission for m2000 is crashes to windows with DCS has stopped working...only happens on this option with this plane
ED Team BIGNEWY Posted February 5, 2016 ED Team Posted February 5, 2016 Please provide your logs folder zipped after the crash. A guide to reporting can be found in my signature. 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
sumguy Posted February 16, 2016 Posted February 16, 2016 (edited) Hello. I figured I'd chime in because I'm having this same problem. Game crash with the M-2000 in a fast-mission. I also tried loading a mission from the editor after changing a player aircraft to the M-2000 and it crashed the same. I looked around a little for a solution but didn't see anything. I appreciate any insight into this. Hopefully it's not my computer, but, it wouldn't shock me.. Though, otherwise, so far I've been shocked at how well my compie is handling the amazing planes! Edited February 20, 2016 by sumguy (attachments removed)
Zeus67 Posted February 17, 2016 Posted February 17, 2016 Unfortunately we must wait for the 1.5.3 version. 1.5.2 is not being updated anymore due to the impending upgrade. We have been submitting 1.5.3 modifications for a week now and only 1.5.3 is being updated by ED at this time. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
sumguy Posted February 20, 2016 Posted February 20, 2016 Well, at least this update does appear to have 'resolved' this issue for me. ^^ Thanks everyone for the replies
Recommended Posts