Matrix Games Forums

Hello!

So I have been playing Command for a few years now. I started with CMNO and moved towards CMO when that came out. The new update just dropped which made it 64bit compatible & wrapped in DX11(alongside other features obviously) so I decided to give it a reinstall. I never had any technical issues with the game. However, in the current version of the game it would appear that the map is entirely frozen for me. I can't pan the camera using the mouse or the arrow keys.

First, the obvious thing to check is if it's a input issue. But all the menu's work, and for further demonstration of the issue, changing the map mode does not update the map displayed (the starting globe orientation). Or, loading a scenario with units does not display the units even though with the globe orientation it should have. The map is just stuck.

I do use my PC in 125% DPI so I did lower it to 100% since programs not designed with DPI in mind tend to have larger text with native UI size so text gets cut off - which obviously isn't ideal.
Another thing I did, was disable Steam Overlay and Nvidia Overlay. My drivers are also updated. I tried disallowing fullscreen optimization and running it as admin but nothing is working. Any ideas? Verifying on steam failed to validate one file but it's reinstalled now.

Logged 0015229

Hi thryckz, thanks for the report, it is being investigated. In the meantime you can continue to use the 32 bit version, by accessing the "beta" and selecting 32 bit legacy

Here it's a guide to setup the 32 bit legacy

thryckz wrote: Wed Aug 09, 2023 10:38 am However, in the current version of the game it would appear that the map is entirely frozen for me.

thryckz, thank you for reporting this. Is there anyway you attach a screenshot to this thread, preferable with the View menu selected and open? Also, an exception log and dxdiag would be useful.

A way to get a screenshot that includes any open menus is to use Windows Key + PrintScreen Key and crop as necessary.

To find exception logs, look in the Logs subdirectory in the Command installation (if you installed with Steam, this should be the "steamapps\common\Command - Modern Operations\Logs" directory inside the Steam installation directory, which is usually "C:\Program Files (x86)\Steam".

To get a dxdiag report, select the Start menu in Windows, type dxdiag, run it, then select Save All Information.

oran42 wrote: Wed Aug 09, 2023 2:34 pm

thryckz wrote: Wed Aug 09, 2023 10:38 am However, in the current version of the game it would appear that the map is entirely frozen for me.

thryckz, thank you for reporting this. Is there anyway you attach a screenshot to this thread, preferable with the View menu selected and open? Also, an exception log and dxdiag would be useful.

A way to get a screenshot that includes any open menus is to use Windows Key + PrintScreen Key and crop as necessary.

To find exception logs, look in the Logs subdirectory in the Command installation (if you installed with Steam, this should be the "steamapps\common\Command - Modern Operations\Logs" directory inside the Steam installation directory, which is usually "C:\Program Files (x86)\Steam".

To get a dxdiag report, select the Start menu in Windows, type dxdiag, run it, then select Save All Information.

Sure thing! I've attached all the stuff you asked for and annotated everything just to clarify the issue that's being shown in the photo. Thank you two for the help so far!

thryckz wrote: Thu Aug 10, 2023 11:30 am Sure thing! I've attached all the stuff you asked for and annotated everything just to clarify the issue that's being shown in the photo.

Thank you for following up. Do you have multiple GPUs (the dxdiag has four entries for NVIDIA GeForce GTX 1080)?

Also, do you get the frozen map if you disable all layers in the View menu except Base Earth and restart?

oran42 wrote: Thu Aug 10, 2023 1:29 pm

thryckz wrote: Thu Aug 10, 2023 11:30 am Sure thing! I've attached all the stuff you asked for and annotated everything just to clarify the issue that's being shown in the photo.

Thank you for following up. Do you have multiple GPUs (the dxdiag has four entries for NVIDIA GeForce GTX 1080)?

Also, do you get the frozen map if you disable all layers in the View menu except Base Earth and restart?

I am afraid the issue persists after disabling all of the map layers '

As for the multiple GPU question. I only have one GPU but I have four monitors which would be why there's four entries. I can't imagine having enough room or the money for four 1080's haha.

thryckz wrote: Fri Aug 11, 2023 11:48 am I am afraid the issue persists after disabling all of the map layers '

As for the multiple GPU question. I only have one GPU but I have four monitors which would be why there's four entries. I can't imagine having enough room or the money for four 1080's haha.

Thank you for the additional information. I hate to inconvenience you in this way, but do you have an easy way of disconnecting all but one of the monitors and seeing if the issue persists? I'd like to rule the multiple 1080 entries out and it sounds like disconnecting all but one monitor might at least rule it out. An updated dxdiag with only one monitor connected could also be helpful. If that is too much of an inconvenience for you to do, no problem, I will continue to see if I can replicate.

oran42 wrote: Fri Aug 11, 2023 5:28 pm

thryckz wrote: Fri Aug 11, 2023 11:48 am I am afraid the issue persists after disabling all of the map layers '

As for the multiple GPU question. I only have one GPU but I have four monitors which would be why there's four entries. I can't imagine having enough room or the money for four 1080's haha.

Thank you for the additional information. I hate to inconvenience you in this way, but do you have an easy way of disconnecting all but one of the monitors and seeing if the issue persists? I'd like to rule the multiple 1080 entries out and it sounds like disconnecting all but one monitor might at least rule it out. An updated dxdiag with only one monitor connected could also be helpful. If that is too much of an inconvenience for you to do, no problem, I will continue to see if I can replicate.

Sure thing! I restarted Command with all but one monitor and the issue persists. I also want to note as I glossed over mentioning it before, that the legacy version does work for me as intended. So, I obviously don't know what's changed underneath the hood to transition to 64bit but could things like virtualization or TPM play a factor? I know that directly it won't impact Command but within context of the actual Windows API would it be possible that stuff like that could play a role in this not working? TPM is required for Windows 11 so if that was an issue I'm sure you guys would have heard of that by now but there's a lot of CPU parameters in BIOS nowadays. At least, that's all I can think of. Anyway, thanks for the help so far and hopefully you can find a fix for me!

thryckz wrote: Sun Aug 13, 2023 11:21 am Sure thing! I restarted Command with all but one monitor and the issue persists. I also want to note as I glossed over mentioning it before, that the legacy version does work for me as intended. So, I obviously don't know what's changed underneath the hood to transition to 64bit but could things like virtualization or TPM play a factor? I know that directly it won't impact Command but within context of the actual Windows API would it be possible that stuff like that could play a role in this not working? TPM is required for Windows 11 so if that was an issue I'm sure you guys would have heard of that by now but there's a lot of CPU parameters in BIOS nowadays. At least, that's all I can think of. Anyway, thanks for the help so far and hopefully you can find a fix for me!

thryckz, thank you for testing with one monitor and the updated dxdiag. I have not forgotten about this and am making some tweaks and running some tests that may either fix the issue for you on next release or enable you to gather some more information that to find out why the map is frozen on your machine. I do not think that virtualization is the issue unless you are running inside a virtualized container like a virtual machine or sandbox. I do not think that TPM is an issue.

Hey! I am having the same issue on Steam version, both in main branch and beta. I am on a laptop with a dedicated and integrated gpus. I also have a second monitor. I tried the "unplug other monitors" fix and it did work. Just wanted to let you guys know. It then froze again as soon as I plugged the monitor back in.

frozander wrote: Fri Aug 18, 2023 8:29 pm Hey! I am having the same issue on Steam version, both in main branch and beta. I am on a laptop with a dedicated and integrated gpus. I also have a second monitor. I tried the "unplug other monitors" fix and it did work. Just wanted to let you guys know. It then froze again as soon as I plugged the monitor back in.

frozander, thank you for the additional report. Is there any way you could upload an exception log and dxdiag when this
occurs with multiple monitors attached?

To find exception logs, look in the Logs subdirectory in the Command installation (if you installed with Steam, this should be the "steamapps\common\Command - Modern Operations\Logs" directory inside the Steam installation directory, which is usually "C:\Program Files (x86)\Steam".

To get a dxdiag report, select the Start menu in Windows, type dxdiag, run it, then select Save All Information.

thryckz wrote: Fri Aug 11, 2023 11:48 am

frozander wrote: Fri Aug 18, 2023 8:29 pm

thryckz and frozander, can you please upgrade to the new update on Steam (1328.9) and let me know if you still have this issue or if it resolves with the update?

oran42 wrote: Wed Aug 30, 2023 2:11 pm

thryckz wrote: Fri Aug 11, 2023 11:48 am

frozander wrote: Fri Aug 18, 2023 8:29 pm

thryckz and frozander, can you please upgrade to the new update on Steam (1328.9) and let me know if you still have this issue or if it resolves with the update?

I know this is late and you probably already got enough feedback but the update fixed my issue. Thanks

frozander wrote: Wed Sep 20, 2023 8:32 pm I know this is late and you probably already got enough feedback but the update fixed my issue. Thanks

frozander, thank you for your follow up. It was helpful to get confirmation that the fix worked for you.

If anyone else has this issue despite the fixes that have gone into recent updates, please let us know.

I am having this issue with version 1328.10.1. Unable to pan at all.

fp2024 wrote: Sat Oct 28, 2023 8:30 pm I am having this issue with version 1328.10.1. Unable to pan at all.

Please open a new thread and provide as much information as possible. This is not a helpful post.