Matrix Games Forums

I made it a few minutes into Smart Bracelet (2014) before this happened. The BMNG layer was off, relief layer was on, and the lat/long grid was on. I'm running Win7 x64 with 20GB RAM, an i5 2500k on a stable overclock, and an HD 6870. Command is installed on an SSD. I've attached dxdiag.txt to this post (I... think?).

I haven't seen this issue with other scenarios yet; I'll see if I can reproduce it on this PC/a different one. The UI quickly became unresponsive while I was playing the scenario, but the game itself didn't lock up until the unhandled exception. Time mode was set to no-pulse.

Here's a link to the autosave and here's one to the 100 second autosave

Be very careful overclocking with large scenarios. Command is incredibly CPU-intensive and I have brought a couple mid-level CPUs to their knees with multi-thousand unit scenarios. I have seen significant thermal spikes with hi-fi on, and real-time pulsing. This is especially true with a lot of ECM and missile engagements.

Stable overclocks don't create probs wood. Been Running large scenarios for some time now and the main prob is that after a while it runs out of memory on large scenarios. Best solution is to save every 10 mins and restart. Last update (536) they even solved the jamming issue so that is out now

Btw did you do a deep rebuild of the scenario ?

Stable and overclock are oxymoronic... Doesn't mean you can't do it. It is matter of how much risk you are willing to accept and how much airflow you can generate. I used to QA for a large chip manufacturer...its all in risk and percentages.

Wood i run stable overclocks on all my K chips at work and it makes a diff esp on Desktops. Never had any probs as i test them throughly. Now i am waiting for the new haswell-E for CMANO and i will see how it performs on such a monster. On Xeons it runs smoothly that's for sure

No prob, but in my SW company as soon as someone tells us they are overclocking when they have an issue, we won't talk to them until the take it down a notch. That is experience over a significant sample size.

Issue logged. We'll take a look.

Thanks for the effort with the files and explanation!

Mike

Unable to reproduce in Build 540.