Crossover M2 Macbook Pro.

I've been happily playing for ~180 hours.

Unfortunately, with the latest patch (v0.8.5) the game locks up/freezes my laptop completely. My computer heats up, then mac reboots. It's happened 3 times so far. The latest time it happened when altering a mine tower's area. During which the anchor points were behaving wonky. It seemed like it was too large of an area. Maybe that is a clue.

Also unfortunately, I will not be playing anymore unless this is fixed. I just lost an hours progress and do not enjoy my laptop overheating and rebooting. I'm fully aware it could be crossover, but it's been working for 180 hours with previous versions.

Also, also unfortunately, the game is amazing so I'm sad.

I'm not sure where they are on a Mac, but they'll probably need your logfiles to be able to do anything about that.

We'd need a little more to be able to investigate this issue. Mac is not officially supported and none of us have mac or crossover, so please give us as much info as you can.

With crossover, the location of the logs might be in the same spot as it replicates the filesystem of windows. Where are they normally on windows for a steam install?

Logs can be found at: %USERPROFILE%/AppData/Roaming/Captain of Industry/Logs. You can also include Unity logs from %USERPROFILE%/AppData/LocalLow/Mafi Games/Captain of Industry/ and %USERPROFILE%/AppData/Local/Temp.

Attached are the roaming and locallow log files. Prior to starting the game I deleted all of today's logs and so there wasn't a log file in temp. There was no crash log either.

I played for a few hours yesterday with no issues.

This morning it froze then crashed (i.e. restarts my laptop) and I figured out what causes it:

I am able to reliably get it to do it when panning (wasd) while zoomed all the way out with the layers showing (mineral layer, mining designations, mine tower areas etc.). No other interactions are needed. It might be the additional zoom range that the new patch added or something since it did not do this prior to the latest patch.

It does not lock up unless the layers are showing. Panning at max zoom level while they are not showing is fine.

Here is a phone recording of it freezing. I didn't wait for the laptop to crash and restart, as it takes ~30 seconds.

I load a save, open the mining designation tool (to get the layers to show), zoom all the way out, then pan with wasd. It locks up. I cut the audio off of the phone recording, but the music does keep playing until the laptop reboots. The laptop heats up, too. Maybe like a tight CPU loop or zoom level stressing out the video card or something.

https://imgur.com/a/h8GHsQZ

I'm not a CoI dev, but that behavior strikes me as a hardware- or driver-level crash. Given the zoomed-out, show-layers requirement, it suggests you're running out of memory, either system, video-dedicated, or both, and the system doesn't know how to handle that gracefully.

Looking at the log files, I see a couple of stack traces, but no actual exception identifiers, suggesting internal, recoverable "error" states not using Exceptions (both do have messages suggesting that). The second stack trace is the last thing in the file, though, and comes right after "loaded game", albeit with a seven-second timestamp gap... which supports a memory exhaustion theory. I've seen in my own experimentations that CoI will often have a final spike in memory consumption, before reaching a stable level, when first un-pausing the game after loading.

Is there a utility, like Windows' Task Manager, that'll let you view/display memory utilizations in real-time while performing the crash sequence?

Does the game work on Crossover for others? Anyone seeing similar issues?

Captain Marek wrote:

Does the game work on Crossover for others? Anyone seeing similar issues?

I've taken a break from gaming for a week, but before that I was able to play for hours using Crossover. I'm playing on a Mac Studio M4 Max with Crossover 26.1.0.

@charlesincharge Crossover version 26.2.0 was released a few days ago—have you tried it yet?
Have you checked how much free space is left on the internal SSD?