Matrix Games Forums

Hey, I'm creating a new thread for what probably is the same issue as reported in the thread "GUI freezes".

I'm on Windows 10 64-bit (Home) with a 4770K and a 770.
I've had this problem since I started playing on Black Friday. It happens randomly every few hours or so, I guess. I haven't really counted how often it happens.

Every now and then, Command becomes unresponsive, almost as if it was running at 5 FPS. My Windows mouse cursor moves normally and everything except for the Command GUI is fully responsive, but the Command window gets really slow. If I press "Missions" for example, it takes a full second for the drop-down menu to appear, instead of almost instantaneously.

When the game is "unresponsive", mouse clicks are often dropped, but not always, if this is any clue to the problem.

Also, sometimes, the GUI 100% stops. When that happens, I have never button mashed, but if I did, I think Windows would say the process is unresponsive and ask me to close it, like it usually does with frozen processes.

Just now, I started Command a while ago and then started writing a little bit on the forum and when I went back to the Command window, it was in the unreponsive state. I checked CPU usage (1%), memory use (3GB, which of 500MB was Command, out of 16GB), disk use (0%) and internet use (0%).
I clicked Options and it took several seconds for the window to render properly. I'm attaching a screenshot of this.
Also note that the game is paused and was paused for the entire duration of this "episode", so it can't have been a taxing situation or scenario. It's just the start of Mark's second tutorial.
After about 10 minutes, as I was writing this, the GUI snapped back into responsiveness. Not related to anything I did, most likely.
I don't run a lot of background software, only MSI Afterburner (I tried turning this off: no change), Steelseries Engine and OneDrive.

Also: when it has happened before, I have solved it by minimizing the Command window using the taskbar or the bottom-right desktop shortcut on the taskbar. When I open the window again, the GUI is as snappy and responsive as ever again.

And to re-iterate, this has happened many times, in many scenarios, both while running (to my recollection) and while paused and sometimes with dialogs open and sometimes with no dialogs open. It seems to simply happen randomly as a function of time.

Thanks added to the list of things the guys should look at.

What version of the game are you running (sorry didn't see in the screenshot). If it isn't 972.12 grab that here: tm.asp?m=4386511

If you could the next time it happens at least let us know what scenario it is. Just helps get to a solution quicker.

Thanks!

Mike

ORIGINAL: mikmykWS

Thanks added to the list of things the guys should look at.

What version of the game are you running (sorry didn't see in the screenshot). If it isn't 972.12 grab that here: tm.asp?m=4386511

If you could the next time it happens at least let us know what scenario it is. Just helps get to a solution quicker.

Thanks!

Mike

It's 972.11. I'm going to try updating and report back it the issue persists.

Also, I can post my DxDiag if it helps, but I don't know if I have to capture it as the glitch is on-going?
I captured shortly after and this stuck out in it. No idea if this means anything to you:

+++ WER1 +++:
Fault bucket 129406014646, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem signature:
P1: Command.exe
P2: 1.0.0.0
P3: 10.0.15063.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

ORIGINAL: mikmykWS

Thanks added to the list of things the guys should look at.

What version of the game are you running (sorry didn't see in the screenshot). If it isn't 972.12 grab that here: tm.asp?m=4386511

If you could the next time it happens at least let us know what scenario it is. Just helps get to a solution quicker.

Thanks!

Mike

Unfortunately, it didn't work. Still a problem, but I am able to reproduce it: I simply start CMANO, load the only save I had available, start Photoshop, wait like 15 minutes and when I open CMANO again, it's unresponsive.
I'm attaching the save, though I doubt it has anything to do with the scenario. Photoshop probably also has nothing to do with it. My guess is simply leaving CMANO open in the background for a while triggers the problem.

Thank you! Added to the notes on the issue. A dev will get to it when they can.

Mike

This problem may caused by corrupted system files or not properly installed drivers. Check the system with running "sfc /scannow" in elevated cmd.com and check devices in Device Manager.

ORIGINAL: Filitch

This problem may caused by corrupted system files or not properly installed drivers. Check the system with running "sfc /scannow" in elevated cmd.com and check devices in Device Manager.

Didn't fix it. I also updated my graphics card drivers, for what it's worth and restarted several times of course.

My problem as I described it above is 100% reproducible on my system: I just have to leave CMANO minimized (or possibly in the background, but the issue doesn't seem to occur if CMANO is the "active window") for 20 minutes (10 minutes doesn't seem to be enough) and when I come back and bring CMANO into full-screen, it's in the unresponsive state. As always, minimizing the widow and bringing it back up again fixes the unresponsiveness.
I've tested this lightly a few hours today while doing chores, coming back to the computer every now and then. It feels like CMANO is down-prioritised as a background process or something like it. Someone suggested search indexing might be the problem and I do have that activated, but there's zero disk activity, which I think there would be if the SSD was indexing. Also, everything except for CMANO remains responsive.

This may or may not be related to when the game freezes entirely, as was reported in the other thread (which I've also experienced). Also, I've had the problem(s) while playing normally and not only while leaving the game for a little while.

It might take me a few days to play CMANO enough to see if I get a complete freeze again. For now, I only get unresponsiveness.

It could be some random small issue that only affects me and that other guy. I can't think of any way to diagnose it, so it might be hard bug to squish.

Can someone try leaving CMANO minimized for 20 minutes, then bring it back up and see if you have the same issue? I could try re-installing it and see if that does anything.

I've been having this problem as well for the past few months. I tried Process Lasso per suggestion in another thread but it didn't help at all. Minimizing and restoring Command seems to help, but not always.

Thanks guys! Devs have the files etc. and hopefully will be able to help. Workaround for now is to not turn autosave off so your progress isn't lost.

Mike

Just curious, have you tried this:
tm.asp?m=4190908

"Radar" sounds like one of those MSI/Nvidia/AMD "helper" apps...... running anything like this?

bump

ORIGINAL: emsoy

Just curious, have you tried this:
tm.asp?m=4190908

I did try that, to no effect. Currently, I'm in my "study" phase and not playing Command. I'll probably get back to it in January, but if there are no other active reports of this issue, then it probably only affects a small part of the userbase.
I'm running the following background software: Afterburner, Onedrive, and SteelSeries Engine. I think I've tried killing Afterburner before and it didn't change anything. I have a very clean computer that I re-install every couple of years and keep a minimum of stuff on, so background processes probably isn't the problem.
Also, as far as I'm concerned, this was two issues: the almost 100% reproducible "unresponsiveness" that happened sometimes at random and always or almost always if I left the app minimized for a while AND the "total freezes" I experienced every now and then.
The "total freeze" is something I never managed to reproduce, it just happened a few times during normal gameplay.

In a while, when I start playing intensely again I might be able to give a good report on whether the problems persist.

I've updated to the latest version (released on 12/12, IIRC) and after testing once, I couldn't reproduce the unresponsiveness. So it may have worked itself out.