[FIXED B507] Lock up w/ larger scenarios (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

ryszardsh -> [FIXED B507] Lock up w/ larger scenarios (3/29/2014 4:19:21 PM)

I seem to have a fairly consistent lock up/no response issue. Running 1.03, build 504. Attached is a dxdiag file, will upload autosave to next message. Lock up does not seem to be tied to any specific issue such as setting an emitter to on or off. Does seem somewhat tied to having many missiles in flight - or at least is more common then. Does seem to happen only with larger scenarios. I have sound turned off. System is a Haswell NUC unit with 8GB of ram running W8.1. Lock up does not appear permanently fatal - if I go back and load last autosave scenario will usually run through the previous lock up point - but will lock up again. ideas?

RAS



mikmykWS -> RE: Lock up w/ larger scenarios (3/29/2014 4:22:46 PM)

Thanks for the great report. Logged and we'll take a look.

If you can grab and post the autosave file after it happens next time that would great!

Mike



ryszardsh -> RE: Lock up w/ larger scenarios (3/29/2014 4:24:14 PM)

and autosave...had to change the extension to get it to up load so change back to .scen and all should be good..

Thanx

RAS



Rodwen67 -> RE: Lock up w/ larger scenarios (3/29/2014 6:22:17 PM)

I have the same problem with a Intel I5 chip and 8 gb ram.



caiman_ -> RE: Lock up w/ larger scenarios (3/29/2014 7:44:57 PM)

Hi

I was about to start a thread about this very exact issue. The more a scenario contains objects the more i'm experimenting freezing ( almost always random as stated before, with autosave i can continue the scenario ).
I managed to get a savegame where it crashes everytime within a few minutes.

My configuration is : Dell laptop E6540 Haswell I7 & 8go ram . Patch 1.03





vrnichol -> RE: Lock up w/ larger scenarios (3/29/2014 10:55:52 PM)

Having the same problem. Running AMD 8 and AMD 7970



steelp -> RE: Lock up w/ larger scenarios (3/30/2014 2:37:02 AM)

I have the same issue. I have tried changing timing of events, aircraft in air, types of missiles in air, reducing radar systems, reducing AU count, pulse mode vs no pulse, no sound etc. Here is one of many files. Only one in 10 plays in editor would run more than 30 minutes simulation time. Would like to know if there is a bug or some limit has been met as I would like to continue working this scenario. I did read about cruise missile issues and a fix on build 506 ( I believe) but I do not have access to try. This is built on 1.03 B504.



AndrewJ -> RE: Lock up w/ larger scenarios (3/30/2014 3:40:14 AM)

Similar problems for me too. Running Yokes' big 'Closing the Kurile Gap' scenario I can usually expect two or three crashes an hour, sometimes more. While it can happen with large missile and aircraft counts, I've also had it happen when nothing unusually large is happening. (Well, not large for that monster scenario.) Sometimes there'll be an error message box, more often just a freeze and eventual greying out of the screen. Autosaves play through normally, so it's not as if one specific action is causing the problem at one specific time, so I've not sent in any saves. It just seems to be a matter of waiting for the next random crash, and then reloading again.



steelp -> RE: Lock up w/ larger scenarios (3/30/2014 3:40:33 AM)

Newer version of previous submit. Runs longer but still locks up. I have delayed all ASM's from firing as far as I can tell at point of lock up. SSM's were on screen at various points up to lock up.



Dannyp19 -> RE: Lock up w/ larger scenarios (3/30/2014 5:34:28 AM)


quote:

ORIGINAL: AndrewJ

Similar problems for me too. Running Yokes' big 'Closing the Kurile Gap' scenario I can usually expect two or three crashes an hour, sometimes more. While it can happen with large missile and aircraft counts, I've also had it happen when nothing unusually large is happening. (Well, not large for that monster scenario.) Sometimes there'll be an error message box, more often just a freeze and eventual greying out of the screen. Autosaves play through normally, so it's not as if one specific action is causing the problem at one specific time, so I've not sent in any saves. It just seems to be a matter of waiting for the next random crash, and then reloading again.




Same here with the same scen.

It is a monster scen.



kaburke61 -> RE: Lock up w/ larger scenarios (3/30/2014 10:50:10 PM)

Just another data point. I had the "not responding" lockup problem with playing: "FOST: Advanced ASW Exercise",
which I have played many times with no problem before. I didn't attach a file due to the fact that restarting from
the autosave worked fine.



ryszardsh -> RE: Lock up w/ larger scenarios (3/31/2014 3:08:05 AM)

And another data point:
attached is an autosave from a smaller scenario, an adaptation of community scenario smooth trail, as before change the extension back to "scen". Lock ups occur w/ some regularity, this save was just before a lockup when a harpoon was impacting the amphibs in the rear row of the Russian formation. I have noted that sometimes - not every time -I am left with Command running as a process after closing the program - not sure why that is but the orphan process eats cpu cycles like crazy. Seems to be orphaned only when program locks up as in attached autosave but not every time.

RAS



AndrewJ -> RE: Lock up w/ larger scenarios (3/31/2014 10:19:30 PM)

Here's another one that may be related.

Playing 'Closing the Kurile Gap', B504, with nothing exceptional happening the pulse time ramps up to about 8000 and the game suddenly vanishes. There is no freeze or any other warning, just the sudden and complete vanishing of the main window and message log. Looking at the task manager shows four (!) copies of Command running. These persist in running until I manually close them out.

[img]http://i1355.photobucket.com/albums/q716/AndrewJsPhotos/Multi-functionsrunning_zps16669565.jpg[/img]

Reload the scenario, and it runs fine (for now...). I've attached a copy in case its of any use.



Dimitris -> RE: Lock up w/ larger scenarios (4/1/2014 6:39:56 PM)

quote:

ORIGINAL: ryszardsh

and autosave...had to change the extension to get it to up load so change back to .scen and all should be good..

Thanx

RAS


Thank you. Reproduced and fixed in Build 507.



Dimitris -> RE: Lock up w/ larger scenarios (4/1/2014 6:42:18 PM)

quote:

ORIGINAL: caiman_

Hi

I was about to start a thread about this very exact issue. The more a scenario contains objects the more i'm experimenting freezing ( almost always random as stated before, with autosave i can continue the scenario ).
I managed to get a savegame where it crashes everytime within a few minutes.

My configuration is : Dell laptop E6540 Haswell I7 & 8go ram . Patch 1.03



Unable to reproduce this in Build 507; it is possible that it has been covered by previous fixes. Please check again with B507!



Dimitris -> RE: Lock up w/ larger scenarios (4/1/2014 6:46:48 PM)

quote:

ORIGINAL: steelp

I have the same issue. I have tried changing timing of events, aircraft in air, types of missiles in air, reducing radar systems, reducing AU count, pulse mode vs no pulse, no sound etc. Here is one of many files. Only one in 10 plays in editor would run more than 30 minutes simulation time. Would like to know if there is a bug or some limit has been met as I would like to continue working this scenario. I did read about cruise missile issues and a fix on build 506 ( I believe) but I do not have access to try. This is built on 1.03 B504.


Unable to reproduce this in Build 507; it is possible that it has been covered by previous fixes. Please check again with B507!



Dimitris -> RE: Lock up w/ larger scenarios (4/1/2014 7:16:29 PM)


quote:

ORIGINAL: ryszardsh

And another data point:
attached is an autosave from a smaller scenario, an adaptation of community scenario smooth trail, as before change the extension back to "scen". Lock ups occur w/ some regularity, this save was just before a lockup when a harpoon was impacting the amphibs in the rear row of the Russian formation. I have noted that sometimes - not every time -I am left with Command running as a process after closing the program - not sure why that is but the orphan process eats cpu cycles like crazy. Seems to be orphaned only when program locks up as in attached autosave but not every time.

RAS


Thanks! The problem was reproduced and fixed in Build 507.



ryszardsh -> RE: Lock up w/ larger scenarios (4/2/2014 12:15:55 AM)

stupid ?

where is 507?

;)

ras



thewood1 -> RE: Lock up w/ larger scenarios (4/2/2014 12:19:22 AM)

Posted an hour before you message...

http://www.matrixgames.com/forums/tm.asp?m=3583708



steelp -> RE: Lock up w/ larger scenarios (4/2/2014 1:36:06 PM)

Installed B507. Sim ran flawless with large scenario(same as tested previous) for hours then had error message. Attached file - screenshot and auto save. Looking very good with new build. Not sure what this error is.



mikmykWS -> RE: Lock up w/ larger scenarios (4/2/2014 9:18:01 PM)

Thanks for the report. Logged for the next round.

Mike



caiman_ -> RE: Lock up w/ larger scenarios (4/3/2014 10:12:38 AM)

Hi

Just wanted to confirm that most of this issue seems to be solved for me too. From a 20 crash/hour before B507 i'm now experiencing let's say 1 crash each hour. Which make the game now playable. However i'm unable to find a way to reproduce the crash i'm still experiencing i will start a thread if i manage to find a common factor.

Anyway thanks for the fix



thewood1 -> RE: Lock up w/ larger scenarios (4/3/2014 10:51:28 AM)

One thing I have noticed is that in large scenarios with lots (in the hundreds) of missles firing at once, my CPU's four cores are all above 80% usage. I have an AMD laptop and the temperature control is always on. My CPU is throttled back most of the time because of it. I am wondering if some of these issues in large scenarios is heat related.



Dannyp19 -> RE: Lock up w/ larger scenarios (4/3/2014 1:43:35 PM)

I was able to play last night for 2 hours and only one crash. That was when I had a lot of missiles about to hit (or get destroyed). Thank you auto save! I'm not able to reproduce any crashes or I would have sent them. I don't think it's heat related, my system has a water cooler and it stays a comfy temp. at all times. I do notice the pulse count getting up in the 1500-1800 is when things start to slow down quite a bit and a crash happens.



thewood1 -> RE: Lock up w/ larger scenarios (4/3/2014 4:22:46 PM)

I have found pulse counts nearing 1000 is a sign from god that bad things are happening.



caiman_ -> RE: Lock up w/ larger scenarios (4/3/2014 4:26:53 PM)

Now that you speak about the missiles.
For me too the crash occured just before massive missiles hits & anti missile trying to shoot them. But not always the same. Salvos of ARM , Harpoon or Mica EM did the same.
Not related to heat for me either.



thewood1 -> RE: Lock up w/ larger scenarios (4/3/2014 6:26:29 PM)

I think heat is a side effect, but it is a sign that a lot is going on behind the scenes in large missile engagements. I think that why some people have different crash points. I am sure it all depends on CPU load, CPU speed, memory load, software stack, etc. It might be that certain PCs have a limit on the size of the scenario.



caiman_ -> RE: Lock up w/ larger scenarios (4/3/2014 7:21:43 PM)

Mhm i highly doubt it's related to the hardware. I can play to very recent & demanding games without any troubles and B507 managed to remove most of the crashes.



thewood1 -> RE: Lock up w/ larger scenarios (4/3/2014 7:27:47 PM)

That just might be optimizations. I also suspect other games don't tax the CPU like Command. Take a look at CPU loading during a large scenario. I have never had a game bring a quad core CPU to it knees like this game can.

You can see this by switching to and from hi fi while watching CPU load.



caiman_ -> RE: Lock up w/ larger scenarios (4/3/2014 7:49:16 PM)

i just tested a scen with ~80 missiles in the air + lots of other unit.

Cpu performance set to maximize battery autonomy ( cpu underclock )
No pulse mode - time compression x1800
i get ~45% - 50% cpu load and pulse time never peaks at more than 150 -200 ms during the worst moment
A 1080p video is also running to put the cpu to his knees
I get no crash

That's why i'm not sure about an hardware issue.



Page: [1] 2   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.6582031