[FIXED B629] 1.06...same crash as before -- Question?

[Tomcat84]

Same exact error happened again. This time earlier at 6:16:36 zulu. Before that already see pulse times steadily going way up.

[mikmykWS]

Sorry this wasn't fixed but we'll take a look. Thanks for taking the time to explain and post things that help!

Mike

[marcpennington]

No problem. One other thing to add is that the crashes behave slightly differently when high fidelity mode is on and running at 1 second. Then the crash report appears with a big blank map X on the screen. Otherwise the crashes generally occur at about the same point in the scenario. They also appear to occur at roughly the same amount of (real) time into the scenario regardless of the scenario's size or complexity.

[batek688]

I'll occasionally get that big blank X crash as well, and the "onTimer" stack that was posted above. I will recreate a few and generate separate threads so that you can debug.

A couple of notes: What I would call "moderate" scenarios like Operation Brass Drum will crash/not crash depending upon what i'm doing. For example, if I start the game with massive Tomahawk strikes to knock down all runway access points, with follow-up Tomahawk strikes for SEAD (versus all at once), I can then play the scenario up through when I get into the straits of hormuz. If I don't "cheat" that way but instead take a rolling approach from east to west it crashes. This leads me to believe it has to do with the number of platforms "in play."

All of the large scenarios -- forget it. I even tried The Big Stick differently, going 6+ hours and allowing ELINT/JSTARS to detect everything in Syria. THEN I launched my strikes piecemeal. Instead of one massive launch on all coastal AD I split up into zones hitting south, central, then northern AD sites. At this point, the scenario went "white with red X" like map66 describes. FYI -- if you "cancel" the close command dialog, the scenario still runs, you just have no access to a map (my inbound strikes still do their thing).

Anywho, now that the initial reports out of 1.06 (LUA install) have subsided, i'll start a couple of new threads this coming week with the crash details so you can take a look. I'll attach dxdiag and msdiag info as well so you have full system specs and the like. I'll also try running the scenarios and a couple alternative rigs I have to see if I can help narrow things down for you in the event it is hardware/driver related which DX isn't abstracting correctly.

[Dimitris]

ORIGINAL: batek688

I'll occasionally get that big blank X crash as well, and the "onTimer" stack that was posted above. I will recreate a few and generate separate threads so that you can debug.

A couple of notes: What I would call "moderate" scenarios like Operation Brass Drum will crash/not crash depending upon what i'm doing. For example, if I start the game with massive Tomahawk strikes to knock down all runway access points, with follow-up Tomahawk strikes for SEAD (versus all at once), I can then play the scenario up through when I get into the straits of hormuz. If I don't "cheat" that way but instead take a rolling approach from east to west it crashes. This leads me to believe it has to do with the number of platforms "in play."

All of the large scenarios -- forget it. I even tried The Big Stick differently, going 6+ hours and allowing ELINT/JSTARS to detect everything in Syria. THEN I launched my strikes piecemeal. Instead of one massive launch on all coastal AD I split up into zones hitting south, central, then northern AD sites. At this point, the scenario went "white with red X" like map66 describes. FYI -- if you "cancel" the close command dialog, the scenario still runs, you just have no access to a map (my inbound strikes still do their thing).

Anywho, now that the initial reports out of 1.06 (LUA install) have subsided, i'll start a couple of new threads this coming week with the crash details so you can take a look. I'll attach dxdiag and msdiag info as well so you have full system specs and the like. I'll also try running the scenarios and a couple alternative rigs I have to see if I can help narrow things down for you in the event it is hardware/driver related which DX isn't abstracting correctly.

Can you please submit this on a separate thread so that we can track and (if possible) resolve it separately. Lumping multiple reports on a single thread makes it much harder for us to keep track of what's fixed and what is still pending. Thank you!

[Dimitris]

ORIGINAL: map66

And the autosave.

Sorry for that taking multiple posts. Let me know if you need more info.

Thanks! Fixed in Build 629.

[marcpennington]

Thanks for so quickly looking into the problem, and fixing it! Looking forward to the next beta.

[dnewell96]

From the "for what it's worth" file. I have issues with out of memory crashes for a while. It's frustrating but I see as a cost of doing business. The devs do such great job with the game, it is so complicated and intense, I can deal with it. I have noticed some self inflicted things I do that lead to more frequent memory issues. The big one is running Google Chrome at the same time as Command. Seems like a no brainer but sometimes my adult onset ADD kicks in and I multitask while my troops are getting ready for battle. [:-] A fresh reboot and curbing my ADD produces a much better experience.

My machine is running Windows 8.1 with an i7 processor and 8GB of RAM.

[marcpennington]

Just out of curiousity, is there any ETA on a public release of the beta that has this crash fix? I think I might be seeing at least a couple slightly different crashes, but don't want to waste your time in bug reports when the underlying thing might have already been fixed.... And, well that said, eager to get deeper into the game then playing a few minutes, saving, reloading, repeat... :;