Has anyone else seen map "flickering" when zooming in and out?

[Easy301]

Hi team,

I have not played since the 64bit update, came back today and see that the map now has a "flicker" effect to it when zooming in and out. It's only the map, and it's only the background layer that flickers for a second, not the place-name text, but for example the satellite images or other layer.

This almost seems to be a problem with how the map tiles are drawn? Did something change in this respect? This was never an issue prior to the 64bit update. I've done extensive testing to isolate the problem away from my end, I don't think it's a system configuration issue or software conflict.

Again, this does not happen to the whole screen or the text, just the map textures. It makes zooming in and out quickly just look and feel really jarring. Has anyone else experienced this?

Thank you.

----------------------------Edit and Update---------------------------------------------------------------
8/16/2024- Issue is still present in the newly released Open Beta

8/17/2024 -Added DXDIAG and ExceptionLog to this post. I'll also include the video and things I've tried here so anyone checking this does not have to read pages upon pages. Hoping to get some dev eyes on this in hopes there's some other things I can try, or at least get this logged to be looked at seriously.

-Video of issue: https://imgur.com/a/fsexRQO

-Things I'm nearly certain of at the moment:

1. It's limited to only the 64bit client, 32bit works fine.

2. It's not a software interaction/overlay issue.

3. It's not an issue with any running services, both official and Microsoft.

4. It's not related to Steam software of a background Steam Process.

5. It does not appear to be a GPU driver issue.

What I've done to try and fix this:

Rolling drivers back intermittently up to a year. Using DDU the entire way to make sure the driver installs were clean.

-Disabled all start-up software with Windows Task Manager and then tried running the game.

-Used "Selective Startup" via the MSCONFIG tool to load only the bare necessary services (both Microsoft AND third-party) alongside disabling all start-up programs.

-Manually terminated all non-essential processes via task manager in hopes of finding a culprit

-Verified it was not a scaling issue.

-Tried various refresh rates, tried both monitors on a two monitor set-up.

-Tried running the program as admin, as well as various compatibility modes

-Reset all NVCP settings, and even tried some manually such as forcing Vsync, etc.

-Rolled back the last few Windows Updates

-Tried alternative peripherals and removed peripheral software (For example, I tried another mouse, and disconnected my Logitech one and removed the associated Logitech software.)

-Used a Steam emulation platform to try and isolate the issue further and see if it was possibly an issue with Steam. This allowed me to launch the game without Steam running while using my Steam Install and retaining all DRM protections. This sadly did not work either, meaning the issue is not related to Steam software interfering or a Steam background process causing this issue.

-Switched Drives to rule out any drive issues.

-Tried alternate internet connections, including alternate Wifi and wired connections incase the issue had to with my internet connection and the way tiles are fetched.

-Tried disabling and enabling Windows 11 "Windowed Optimizations" under Windows 11 graphics settings.

-Turned on and off GPU Scheduling.

-Removed any OC's of both my CPU and GPU

-Attempted Various power profiles, and made sure Command was set via Windows to use my Dedicated Graphics Card.

-Removed NVIDA drivers, and tried with generic Windows display drivers to test and see if it was a GPU incompatibility

[Nikel]

Is this problem?

https://www.matrixgames.com/forums/view ... 4#p5117544

[Easy301]

Is this problem?

https://www.matrixgames.com/forums/view ... 4#p5117544

So, that's what the flashing looks like, although it only happens when zooming, and stops immediately when you let go of the scroll wheel, it also only happens if you scroll semi-quickly. It's not as intrusive as that video, it happens consistently at split second intervals when zooming out quickly with the mouse-wheel.

Rolling back to the 32bit legacy does NOT have this problem. This occurs even with every background program closed aside from Command.

This is on an 8700k, 32gigs of ram and a 2080.

Unfortunately, something happened during the switch to 64bit that's causing things to flicker when zooming in and out.

Driver rollback, closing all background programs, turning off Steam overlay, etc does not resolve it.

[Nikel]

If the cause is some software running, post the exception log after selecting the box "Log debug information to file" in the General tab of the options.

[Easy301]

If the cause is some software running, post the exception log after selecting the box "Log debug information to file" in the General tab of the options.

Thanks for all the replies, I appreciate it. Command is really the only game I play, it's my all time favorite and I'm holding out hope this can be fixed.

I don't know if you read my reply but like I said, this is not software related. Closing down every single program and then running command does not fix the issue. The only way I've been able to resolve it so far is rolling back to legacy which imho is not a long-term viable fix.

[Nikel]

Yes, I read it

Software may be running in the background and we are not aware.

The event log may indicate it with the setting I wrote above, having seen it many times.

And if it is not what is happening, it is a good idea to exclude it completely. But it is up to you of course.

[Easy301]

Yes, I read it

Software may be running in the background and we are not aware.

The event log may indicate it with the setting I wrote above, having seen it many times.

And if it is not what is happening, it is a good idea to exclude it completely. But it is up to you of course.

This is what I could find after turning on that option, but it does not look too helpful. Is this what you needed?

[Nikel]

Yes that is.

And as you said there is not software interfering.

Well, a bug then I guess.

More info for the devs? Post your dxdiag file. And do you know how to record a video displaying your issue?

[Easy301]

Yes that is.

And as you said there is not software interfering.

Well, a bug then I guess.

More info for the devs? Post your dxdiag file. And do you know how to record a video displaying your issue?

Good idea.

Here's an example of what's going on: https://imgur.com/a/fsexRQO you'll notice in the quick video, it stops when I turn off a certain layer but then starts again when I turn on a different layer such as satellite.

Excuse the resolution, the host lowered the quality but it's more than adequate to see the issue and what's going on.

I've been really struggling for hours now trying to resolve this, I don't mind playing it as is, I just don't know if it's something I can fix or if it's something the team has to fix, that's kind of what I'm trying to get to the bottom of right now.

[Nikel]

Strange things happen in the Sahel

Just kidding, of course.

And the Dxdiag file?

[Nikel]

Wait, the event log is incomplete.

There should be more lines, I just post the first and the last of what is missing.

Successfully loaded Sim Configuration.
...

DXNTRACE-INIT: Initialized DX11 renderer.

Did you check the box, close the game and then restart?

[Easy301]

Wait, the event log is incomplete.

There should be more lines, I just post the first and the last of what is missing.

Successfully loaded Sim Configuration.
...

DXNTRACE-INIT: Initialized DX11 renderer.

Did you check the box, close the game and then restart?

I did check the box but did not restart the game. Here's a full log capture from the last session:

Code: Select all

--------------- Starting new GUI-client session - 8/15/2024 3:47:13 PM Build 1328.18 -----------------

User's machine 
Machine's name : DESKTOP-0KKR5NV
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732374.5Mo
Available RAM : 28120.9Mo
Total virtual memory : 140737488.2Mo
Total RAM : 34286.7Mo
OS name : Microsoft Windows 11 Home
OS platform : Win32NT
OS version : 6.2.9200.0
>>Not running as administrator ! <<

Successfully loaded Sim Configuration.
Discovering DPI
DPI_scale = 0
DPI registry setting, HKEY_CURRENT_USER\Control Panel\Desktop\LogPixels:96.
Showing splash screen.
Loading splash image
Splash image loaded
Client.Initalize
Initialization started.
Starting initializing Sim Core.
Successfully started database scan.
Loaded terrain grids (BGD).
Successfully created Sim World.
Done initializing Sim Core.
Successfully initialized Sim Core.
Successfully switched to High Performance power plan.
Successfully loaded Lua UI Handlers.
Successfully created new game.
Successfully set database hash value.
Successfully completed Set Current Scenario.
Successfully initialized Lua.
Successfully cached map symbols.
Successfully created new scenario.
Initialization completed.
Wait for terrain to load.
Terrain loaded.
Starting loading MainForm.
Configured MainForm working area
License: Command full version
Configured range ring colors
Loaded Reference Points Color, Plotted Course and Waypoint Color
Done loading MainForm.
Calling MainForm_Shown.
Populated CanalList.
Added World Window panel.
Built database list.
Preparing Wold Window.
Preparing Wold Window done.
Prepared Wold Window.
Calling MainForm_Shown: Show window.
Closed splash screen.
Showed Start Game window.
Finished MainForm_Shown.
DXNTRACE-INIT: Initializing DX11 renderer.
DXNTRACE-INIT: Initialized DX11 renderer.

I'll grab the DXDIAG in a bit but just for ease, here's my configuration:

Windows 11 Home
32 gigs of RAM
i7 8700k
Geforce RTX 2080 (Using newest game ready drivers)

[thewood1]

My guess is you have some kind of overlay running in the background. Thats what I have found causes flickering. Usually nVidia or Steam overlays, but some of the PC companies and GPU companies use overlays also.

[Easy301]

My guess is you have some kind of overlay running in the background. Thats what I have found causes flickering. Usually nVidia or Steam overlays, but some of the PC companies and GPU companies use overlays also.

Thanks for the suggestion, unfortunately making sure all overlays were turned off was the first thing I did, even some of the more "hidden" ones within Windows. Steam Overlay is off, all GPU overlays including things like Shadowplay, Geforce experience, Microsoft gamebar, etc are turned off.

I've tested with nearly no other software running aside from Command and Steam. As of now I can almost 100% rule out that it's an overlay causing the issue, there's just absolutely none running. Unfortunately, I'm almost as confident that it's not another piece of software that's interfering with Command due to the extensive testing I've done including running command in an environment where only the software needed to run windows and Command are running.

I say unfortunately because I don't know what else to try currently. I'm open to any suggestions and will try and provide info that anyone needs. It's so disappointing as I'm finally feeling better enough to play Command and I just can't solve this issue.

Edit: I also tried starting the computer in safe-mode and running Command that way just to double check it was not anywhere software interfering. As of now it seems to be something with Command. Does anyone have any ideas on things I may try?

[Nikel]

The eventlog is now complete and displays no error or interference.

I bet for a bug, indeed there are bugs in the 64-bits/DirectX 10 version that were not present before, like the losing of borders and coastlines.

Lets hope the new beta will fix them

[Easy301]

The eventlog is now complete and displays no error or interference.

I bet for a bug, indeed there are bugs in the 64-bits/DirectX 10 version that were not present before, like the losing of borders and coastlines.

Lets hope the new beta will fix them

I hope so, so far every where I've checked the problem has not been acknowledged by the devs at all. It's usually (rightfully so), chalked up to user error with something like an overlay, or software interaction.

That's not the case here though and I hope behind the scenes at least that they saw this thread and may take a look. If it's a problem that's only with certain hardware configurations it's possible they may never even have the same issue.

I just hope it's something that can at least be looked into, as of now I can't play my favorite game.

[Easy301]

The eventlog is now complete and displays no error or interference.

I bet for a bug, indeed there are bugs in the 64-bits/DirectX 10 version that were not present before, like the losing of borders and coastlines.

Lets hope the new beta will fix them

I'd stick to using the legacy 32bit client but the Community Scenario pack does not work with that version. The standard scenarios work but anything from the CSP just says "The scenario you selected uses a DB not in folder" or something such as that. I even tried moving the DB folder from the 64bit version over to the 32bit legacy and still no go.

If I could get the CSP working in the legacy version I'd be able to play at least.

[Nikel]

The devs use this method for protection, you cannot use new dbs with older versions of the exe.

The current CSP is v48.

I think you could use v47, but there is no link available.

The last version seems to be v46, try this one.

https://command.matrixgames.com/temp/Co ... ack046.zip



Anyway the new beta release should be around the corner

[Easy301]

The devs use this method for protection, you cannot use new dbs with older versions of the exe.

The current CSP is v48.

I think you could use v47, but there is no link available.

The last version seems to be v46, try this one.

https://command.matrixgames.com/temp/Co ... ack046.zip



Anyway the new beta release should be around the corner

Thanks Nikel,

I guess I'll just hold my breath and wait for the beta, hopefully it's fixed then.

[thewood1]

I wouldn't hold my breath on the beta fixing it. The devs haven't even acknowledged it and the issues seems to be very isolated. I suspect the issue is something on your end because its just not showing up outside people who have overlays of some kind running. I would just wait until a dev can get the time to come in and take a look.