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

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

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

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [FIXED B629] 1.06...same crash as before -- Question?

Page: [1]

Message

<< Older Topic Newer Topic >>

[FIXED B629] 1.06...same crash as before -- Question? - 12/18/2014 2:24:05 PM

batek688

Posts: 92
Joined: 10/16/2014
Status: offline

I've posted numerous crash-dumps in the past from the beta build so I decided to "recreate" under the new 1.06. One example, in The Big Stick I open up with the SSGN launching 154 Tomahawks as a giant SEAD first strike on the Syrian coastline while my patrol and support boxes are being populated. Just as in the beta version (573 iirc), in the middle of the tomahawk strike I get the out of memory exception thrown. (Middle = the strikes on the southern coast have gone in and the middle/northern coast are beginning to detect and be engaged by Syrian SAMs. The patrol/support mission includes ELINT/Surv aircraft which are detecting all sorts of stuff as well.)

Now, my question (and the reason I didn't post it yet): Do I need to go and perform a database update for all scenarios first? I assume yes, but didn't know if part of the installation process included scenario upgrades to the new DB -- and if not, perhaps this is something to put into the "hey, for 1.07/2.0's installer...".

Thanks!

Bill

< Message edited by Sunburn -- 12/21/2014 9:15:07 AM >

Post #: 1

RE: 1.06...same crash as before -- Question? - 12/18/2014 4:38:52 PM

JPFisher55

Posts: 589
Joined: 11/22/2014
Status: offline

When I play Command, I first set my computer performance to best program performance rather than windows choices. This is done under advanced system settings for the properties for the whole computer in windows explorer.

I have not had one crash since I started doing this step.

(in reply to batek688)

Post #: 2

RE: 1.06...same crash as before -- Question? - 12/18/2014 4:58:35 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

I just ran it under version 403 DB, which I had as the original release on that scenario and under DB 420, the current release DB version in 1.06. Played to conclusion on both under acceleration of 1:15. No crashes. I launched all 154 missiles at once and played until the were all off the board. The game slowed a little when the missles were all in the air and went to pulses of about 150ms to 300ms for few minutes.

Note that this scenario has almost 1100 active units and then you throw 150 missiles plus a few dozen SAMs into it. That sized scenario is typical of what can cause Command to crash on some PCs. Not only that, I suspect you have not rebuilt the scenario under a current DB. That is the responsibility of the player or scenario author on community scenarios.

I think you have something going on on your PC that makes so it can't handle a scenario this large...drivers, other programs, etc.

I am running a midrange laptop with AMD A10 at 2.7Mhz, 8Mb RAM, and windows 8.1.

(in reply to JPFisher55)

Post #: 3

RE: 1.06...same crash as before -- Question? - 12/18/2014 5:23:02 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

I just ran it again and launched all Tomahawks...almost 400. There were a ton on SAMs launch at them and active units went up to almost 1500. Scans slowed down to almost 4000 - 6000ms. Once the missiles were done, it went back to 50ms scans.

(in reply to thewood1)

Post #: 4

RE: 1.06...same crash as before -- Question? - 12/18/2014 8:28:45 PM

batek688

Posts: 92
Joined: 10/16/2014
Status: offline

Well, I went from "mostly solid/rare crashes" to crashes all the time back when I put build 573 on. The crashes are almost always "out of memory." My rig is an FX-8 series CPU w/ 16GB on an SSD -- hardly short of memory, but not relevant since this is an x86 prog. Win7, 64 bit. I'll try the performance settings suggested by JPFisher55 and let you know.

Thanks for the suggestions.

(in reply to thewood1)

Post #: 5

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:41:07 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

Do you get those crashes in smaller scenarios. Do the scans start to spike with a lot of missiles in the air?

(in reply to batek688)

Post #: 6

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:45:18 PM

NakedWeasel

Posts: 500
Joined: 1/14/2014
Status: offline

I have to concur, I'm afraid. I am experiencing frequent out of memory crashes to desktop. Of course these are very large, and combat intensive scenarios with hundreds of airborne missiles and OECM blaring... but my 1.50 build plays them with hardly a hiccup. I am playing a large WW3 nuclear scenario right now with the new DB3000 and it's chugging right along. 1.60 is crashing somewhere between every 5 to 10 mins during the same battles. I'll patiently wait for a fix, don't worry.

_____________________________

Though surrounded by a great number of enemies
View them as a single foe
And so fight on!

(in reply to batek688)

Post #: 7

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:46:21 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

What is 1.5 and 1.6?

(in reply to NakedWeasel)

Post #: 8

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:51:33 PM

NakedWeasel

Posts: 500
Joined: 1/14/2014
Status: offline

Sorry. I'm playing Build 570, currently.

_____________________________

Though surrounded by a great number of enemies
View them as a single foe
And so fight on!

(in reply to thewood1)

Post #: 9

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:51:56 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

I am going to go back to my old tried and true...every system has a limited amount of resources. If you are consistently getting out of memory errors on large scenarios that other people can play, you are most likely at the intersection of your system configuration and the games upper footprint. If you can run smaller scenarios without crashes, then until the devs can continue optimizing, you will probably be stuck with scenarios of less 1000 AU and no huge nuclear exchanges.

I have found those boundaries on my system and steer clear of them.

People keep asking for stuff and the devs keep putting it in. In large scenarios, you might be right at the cusp of operability. Add a couple Lua scripts or the new algorithms for unit proficiency, and you might just tip over the top. There are no free lunches in memory management...just better error-trapping.

< Message edited by thewood1 -- 12/18/2014 10:53:46 PM >

(in reply to thewood1)

Post #: 10

RE: 1.06...same crash as before -- Question? - 12/18/2014 9:52:59 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

quote:

ORIGINAL: NakedWeasel

Sorry. I'm playing Build 570, currently.

so you mean 1.05.0 and 1.06.0?

Do you have the same issue in 1.05.02 (573)

(in reply to NakedWeasel)

Post #: 11

RE: 1.06...same crash as before -- Question? - 12/18/2014 10:00:21 PM

NakedWeasel

Posts: 500
Joined: 1/14/2014
Status: offline

I never downloaded 573, I don't think. Was that the Beta that was released several months ago? In any case, 570 is stable, and the newest release is simply not so much.

_____________________________

Though surrounded by a great number of enemies
View them as a single foe
And so fight on!

(in reply to thewood1)

Post #: 12

RE: 1.06...same crash as before -- Question? - 12/19/2014 12:11:47 AM

mikmykWS

Posts: 11524
Joined: 3/22/2005
Status: offline

Guys can you post your files and could you let us know your general computer stats? Wondering if there is a connection.

Thanks!

Mike

_____________________________

(in reply to NakedWeasel)

Post #: 13

RE: 1.06...same crash as before -- Question? - 12/19/2014 12:13:16 AM

mikmykWS

Posts: 11524
Joined: 3/22/2005
Status: offline

quote:

ORIGINAL: batek688

I've posted numerous crash-dumps in the past from the beta build so I decided to "recreate" under the new 1.06. One example, in The Big Stick I open up with the SSGN launching 154 Tomahawks as a giant SEAD first strike on the Syrian coastline while my patrol and support boxes are being populated. Just as in the beta version (573 iirc), in the middle of the tomahawk strike I get the out of memory exception thrown. (Middle = the strikes on the southern coast have gone in and the middle/northern coast are beginning to detect and be engaged by Syrian SAMs. The patrol/support mission includes ELINT/Surv aircraft which are detecting all sorts of stuff as well.)

Now, my question (and the reason I didn't post it yet): Do I need to go and perform a database update for all scenarios first? I assume yes, but didn't know if part of the installation process included scenario upgrades to the new DB -- and if not, perhaps this is something to put into the "hey, for 1.07/2.0's installer...".

Thanks!

Bill

quote:

e

Thanks for reporting and sorry we didn't get it.

Updating can only help as Command has changed significantly since that scenario was built.

Thanks!

Mike

_____________________________

(in reply to batek688)

Post #: 14

RE: 1.06...same crash as before -- Question? - 12/19/2014 12:28:28 PM

Dimitris

Posts: 13282
Joined: 7/31/2005
Status: offline

quote:

ORIGINAL: NakedWeasel
I have to concur, I'm afraid. I am experiencing frequent out of memory crashes to desktop. Of course these are very large, and combat intensive scenarios with hundreds of airborne missiles and OECM blaring... but my 1.50 build plays them with hardly a hiccup. I am playing a large WW3 nuclear scenario right now with the new DB3000 and it's chugging right along. 1.60 is crashing somewhere between every 5 to 10 mins during the same battles. I'll patiently wait for a fix, don't worry.

...and to diagnose/troubleshoot the reason for the slowdown in this specific scenario, we'll telepathically read it from your mind

Alternatively, you can upload it and let us have a look at it

_____________________________

Facebook
Twitter

(in reply to NakedWeasel)

Post #: 15

RE: 1.06...same crash as before -- Question? - 12/19/2014 4:16:49 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

Here's an example of the crashes I'm getting.

Happens regularly after a few minutes of play---- game runs fine then slows down and crashes. System specs or duel core 2.4, Windows 7 64 bit, ATI Radeon 5770, and 2 GB ram. Let me know if you need the autosave as well.

Attachment (1)

(in reply to Dimitris)

Post #: 16

RE: 1.06...same crash as before -- Question? - 12/19/2014 4:20:45 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

And well looks like the jpg I tried to upload is blank. Is there an e-mail address where I can just send the png file and autosave to? The forum requirements for zip and file type are a pain...

(in reply to marcpennington)

Post #: 17

RE: 1.06...same crash as before -- Question? - 12/19/2014 4:35:16 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

Here's one more try at uploading the error.

Attachment (1)

(in reply to marcpennington)

Post #: 18

RE: 1.06...same crash as before -- Question? - 12/19/2014 4:38:24 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

And the autosave.

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

Attachment (1)

(in reply to marcpennington)

Post #: 19

RE: 1.06...same crash as before -- Question? - 12/19/2014 5:53:29 PM

Tomcat84

Posts: 1952
Joined: 7/10/2013
Status: offline

I loaded your autosave and started running it in build 624 at 15 min speed in the background while I did other stuff and sure enough after like twenty minutes real life time it crashed on me:

Running at again now to see if it will crash again and if at exact same time or not.

_____________________________

My Scenarios and Tutorials for Command

(Scenarios focus on air-warfare :) )

(in reply to marcpennington)

Post #: 20

RE: 1.06...same crash as before -- Question? - 12/19/2014 6:01:37 PM

Tomcat84

Posts: 1952
Joined: 7/10/2013
Status: offline

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

_____________________________

My Scenarios and Tutorials for Command

(Scenarios focus on air-warfare :) )

(in reply to Tomcat84)

Post #: 21

RE: 1.06...same crash as before -- Question? - 12/19/2014 6:34:17 PM

mikmykWS

Posts: 11524
Joined: 3/22/2005
Status: offline

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

Mike

_____________________________

(in reply to Tomcat84)

Post #: 22

RE: 1.06...same crash as before -- Question? - 12/19/2014 7:16:01 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

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.

(in reply to mikmykWS)

Post #: 23

RE: 1.06...same crash as before -- Question? - 12/20/2014 6:18:28 PM

batek688

Posts: 92
Joined: 10/16/2014
Status: offline

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.

(in reply to marcpennington)

Post #: 24

RE: 1.06...same crash as before -- Question? - 12/21/2014 8:12:02 AM

Dimitris

Posts: 13282
Joined: 7/31/2005
Status: offline

quote:

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!

_____________________________

Facebook
Twitter

(in reply to batek688)

Post #: 25

RE: 1.06...same crash as before -- Question? - 12/21/2014 8:13:35 AM

Dimitris

Posts: 13282
Joined: 7/31/2005
Status: offline

quote:

ORIGINAL: map66

And the autosave.

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

Thanks! Fixed in Build 629.

_____________________________

Facebook
Twitter

(in reply to marcpennington)

Post #: 26

RE: 1.06...same crash as before -- Question? - 12/21/2014 3:39:08 PM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

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

(in reply to Dimitris)

Post #: 27

RE: 1.06...same crash as before -- Question? - 12/22/2014 3:17:22 AM

dnewell96

Posts: 14
Joined: 12/19/2014
Status: offline

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.

(in reply to marcpennington)

Post #: 28

RE: 1.06...same crash as before -- Question? - 12/30/2014 2:46:14 AM

marcpennington

Posts: 335
Joined: 1/31/2011
Status: offline

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... :;

(in reply to dnewell96)

Post #: 29

Page: [1]

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [FIXED B629] 1.06...same crash as before -- Question?

Page: [1]