Crazy high CPU use sitting in main menu (on TR2990WX)

[Lifeless]

Anyone else noticed this? Its running 32 hardware threads at 100% (out of a possible 64 on the machine...)

[75Karsten]

CW3 is single-threaded. So no, I doubt it. What we do know is that there is a long-standing Unity bug to do with losing frame lock if the game is left open a long time/computer goes to sleep, etc. and that drives the FPS on the main menu to insane levels.

Shutting the game down resolves that.

[Lifeless]

So, this imgur[imgur.com] I've uploaded shows:
CPU utilisation in a level (not the load screen, per your description of that being a known bug). The dark blue rectangles are 100% or nearly-100% utilised cores.

The process monitor trace shows the threads being created and sitting around until the game was exited a couple minutes later. Definitely multi-threading, even if the core logic is written single-thread.

[The_Mell]

But which processes use those cores?
Is it really CW3? Or maybe something else going bogus?

Had some terrible CPU usage with a buggy GPU driver once for example.

[Lifeless]

Its cw3.exe as already stated. Have added a screen shot of task manager showing 49% cw3.exe, 48% idle, and then other processes down at 01%. (100% would mean 64 threads running concurrently, one per logical CPU)

[75Karsten]

I will alert the dev, but this is not a known problem, And it's unlikely that there will be a fix forthcoming in the game. It could be a unity bug and just today I've also read of Windows dispatch issues on THreadripper processors. Not that I think that specific issue is in play here, just suggesting it might be a Windows or Unity problem As I said, the game itself doesn't multitask, so there's no inherent way it'll spawn that many processes or run on that many htreads.

Here's the Windows issue I'm talking about: https://youtu.be/M2LOMTpCtLA

[Lifeless]

Thank you. I am aware of the threadripper scheduling issue - I'm already using the workaround. In CW3's case though, the number of threads is such that cross-fabric memory access will be force (even though the total RAM used is tiny). This is because of the 64 cores, at most 16 have direct access to any part of RAM. (16 get one half, 16 get the other half, and the remaining 32 have no local RAM at all). This prevents the scheduler workaround from having any effect - what it does is tries to move all the threads for a game to one node, but 32 threads cannot fit in any one node.

As for being single threaded - as I said, large numbers of threads are a) being spawned and b) executing work, as shown by the data I've gathered. I don't know whats different about my config to trigger this behaviour, but its definitely happening :/

[Knuckle Cracker]

As an experiment give the "version 208" version of the game a try. Go to the betas tab for the game in steam (right click the game and select Properties in the steam client) and select version 208 from there. This is the same game, it is just built with an older version of Unity.

In CW3 I don't spawn any threads in the game code. But Unity itself does for sure. On my desktop it looks like a number are created related to my sound card and my amd GPU. In addition to those there's what looks like a thread pool. I don't have any direct control over the threads, other than unity version and possibly some command line options. So try the old version of unity in version 208. That may give us another data point.

Also, take a look at the log file for the game. Just to make sure there isn't something being logged there. Note that the log file gets created each time you launch the game (it gets overwritten on start). This post has info on where to find the log file: http://knucklecracker.com/forums/index.php?topic=16476.0

[Lifeless]

Did a super quick test with 208 which is much better behaved! taskmgr[imgur.com] - feels a lot better to play too. Will grab logs later from both versions for you.

[Oooch]

Fascinating! I've been playing this and noticing it uses 100% of my 13900K, using 100% of all cores, but version 208 handles fullscreen differently and makes the mouse cursor move at 30 fps so is just trading one problem for another

Fortunately even though its using 100% of all cores its not making the CPU shoot up to 100C and just hovering around 60C

[wyt_gogogog]

Having a similar problem. I'm on an intel 265k with nvidia 3080 and running in windowed mode. Had no problems on my previous puter, but on this one it starts ok, running on one core, but after a couple of minutes all 20 cores suddenly jump to 100% load. Stops when CW3 is closed. Really strange.

[75Karsten]

Are you reporting an issue then the game is on the main menu, or when you are playing a map?

[Mika]

Yesterday I saw this and I wanted to look at the CPU usage (5 ~ 8%, very low) and I found a small bug, nothing important.

I play in windowed mode, if I switch to full screen mode, then go back to windowed mode and now press "maximize window", the game starts to rapidly and continuously change the resolution between 1080P and 1050P (because of the taskbar) causing high CPU usage (up to 24 ~ 28% in the main menu and up to 40 ~ 50% in a map, screenshot 1).

Only happens the first time, the second time, when maximizing the window stays at 1050P but scaled to 1080P, resulting in the HUD/UI looking a little deformed (screenshot 2, the texts: CN2, Energy number, pause text and mission time), in addition to being behind the taskbar and causing the position of the buttons to be displaced, for example, if I want to unpause from the button I have to press the sound button and the sound on the number zero. This applies to all buttons.

As I say, it's nothing important because it's something that only happens in that situation, maximizing the window without switching to full screen doesn't happen.

1. https://steamcommunity.com/sharedfiles/filedetails/?id=3422100110
2. https://steamcommunity.com/sharedfiles/filedetails/?id=3422112404