Matrix Games Forums

...or my day with CMO new versions was ended because I don't want to update my Windows OS (Windows 10 1607) to any newer version. (some applications depends on it)

After downloading the new beta from steam (and installed Edge WebView2), I start CMO and didn't have a normal map render in the main window like the attached image. Other interface functions, including the DB viewer which should depends on the WebView2, works as far as I tested.

Can you at least say the OS? Is it Win7?

thewood1 wrote: Fri Aug 16, 2024 10:26 pm Can you at least say the OS? Is it Win7?

They did say (Win 10 ver 1607), which is about 8 years old.

I don't know, sounds like they could be out of luck with refusing to at least update to the latest version of Win 10

Sorry...missed it.

Actually...didn't miss it. He edited it.

I have a Windows Surface Book with an older version of Windows 10 and it works fine. I think its 1511. I still fire it up periodically. It has CMO 1328.12. Has an i7 and nVidia 965.

"Intel(R) UHD Graphics 620" from the dxdiag.

Thats your problem. Not the OS. It was announced quite a while ago the Intel's move to discontinue support for DX9 on Arc and Iris GPUs pushed the devs to DX11. I am pretty sure the HD 6XX series is the problem because it doesn't support DX11 natively. My guess only.

Did you try the 32-bit CMO 1307 version. Its been left up specifically for people struggling with the 64 bit version.

The same system runs 1328.9 and later in the 1328 branch (to the 18) good, maybe some update on map drawing procedures breaks it?

And sorry for not stating the Windows build in the original post, I though the dxdiag is enough.

In the game Options, General tab, tick the box:

"Log debug information to file (for debugging only)"

Restart the game, and upload the new exceptionlog created.

If there is no error displayed, I would search for updated drivers.

This is what I would do in your case

Damn, I just discovered that I didn't enable the error log in steam copy (I have a offline license and always play with it). Here's the most recent logs.

It seems I may really have some driver issue or something like that, but I really don't dare to do any major update to anything now.

Well, 1328.9 serves me well enough.

Let's go through the checklist, just in case:

* Is Command running as admin? (ie. prompting you "are you sure you want to run this program" when you launch it)
* (Steam only) Are Steam overlays disabled for Command?
* (Steam only) Is Direct-Write disabled on the Steam client?
* Are all other applications (and especially hardware-helper apps like RivaTuner, Nahimic, MSI Afterburner etc.) shut down?
* Can you try temporarily switching to 100% DPI (font sizes etc.) and see if that resolves it?

Checklist complete, all the mentioned settings are verified at the intended state.

And it is the same as before.

There are 2 errors in the exception log.

What do they mean?

It usually means the GPU can't launch or support DX11.