[0.1.1] Game flickers and locks up at low framerates

[subtle nest]

I'm running on an older Mac Mini (purchased 2020). When the game lags a little, it sometimes loses its mind and will flicker back and forth between two different video frames. I can't reliably trigger it, but it is rare at the beginning of a game and becomes more likely as the map gets bigger. Some intermittent triggers are

• Zooming way out. There's a little lag as the display switches to a less detailed representation, and if it glitches that's when the glitch starts.
• Switching between Tiny Building Mode and Space Block Mode (whatever they're called; the spacebar does it). The glitch is more likely if the changes are rapid.
• Copying or pasting, especially big structures.
• I've noticed a couple of times when some other process on the computer wakes up briefly, and that little lag triggers the glitch.

One mode this gets into (which I wasn't able to video-capture) is that selecting some an object for placement triggers the glitch, but the game is fine while the selection is cleared. It's usual that Tiny Building Mode is more sensitive than Space Mode. So for instance I can shift-5 and place some Space Platforms and Space Roads and hit space to zoom into a platform without problems. Then maybe pressing 1 to lay some Tiny Roads glitches, and the glitch continues until I clear the selection with Escape, and I can intermittently get the glitch to come and go.

[chilly notch]

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages — we're also scanning for duplicate reports automatically now.
📨 There are currently 25 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

💾 Savegame files (.spz2) are very helpful if relevant to the issue!
Export via Main Menu → Play → click the download icon on the relevant savegame.
You can also find them here:
• macOS: ~/Library/Application Support/tobspr Games/shapez 2/

[chilly notch]

📋 Log File Analysis

Log Analysis (Player.log):

1. InvalidOperationException: The UnityWebRequest system is not yet available or has already been shut down, occurring at UnityWebRequest.Create() via AnalyticsWebRequest..ctor and WebRequestHelper.CreateWebRequest.

[subtle nest]

Here are a couple of other Player.log files which have stuff about "Failed Allocations" at the end.

[chilly notch]

📋 Log File Analysis

Log Analysis (Player-prev.log):

1. InvalidOperationException: The UnityWebRequest system is not yet available or has already been shut down, occurring during UnityWebRequest.Create() via AnalyticsWebRequest..ctor and WebRequestHelper.CreateWebRequest.

[chilly notch]

📋 Log File Analysis

Log Analysis (Player.log):

1. InvalidOperationException: The UnityWebRequest system is not yet available or has already been shut down, occurring during UnityWebRequest.Create() via AnalyticsWebRequest..ctor in the Unity Analytics service.

1. [SPZ2-2836] — ✨ 82% similar

Game flickers after a few minutes of running. Getting errors
Done • Priority: Medium • Fix: 4 - Early Access • Game: 0.0.0-alpha22.3 • Resolution: Duplicate

The game flickers after a few minutes of running and produces errors. The issue appears to be triggered during normal gameplay, with the player receiving errors logged in player.log. The flickering may be related to a Train Launcher connected to The Vortex, as removing it seemed to stop the problem. The player was using F9 for speed modifications and had to revert to a previous save state. This significantly disrupts gameplay by causing visual flickering and forcing the player to reload earli...

2. [SPZ2-2724] — 👀 68% similar

Game rendering breaks down. "Mesh ID Exceeded range" error spammed in console
Done • Priority: Medium • Fix: 4 - Early Access • Resolution: Done

Game rendering breaks down after 1.5-2 hours of gameplay, with "Mesh ID Exceeded range" error spammed in console. Issue possibly related to having many Wires on screen while working on a Make Anything Machine. The error indicates the game exceeded its internal mesh ID limit during rendering. Game becomes unplayable and requires full restart. Not reliably reproducible but has occurred twice under similar conditions.

3. [SPZ2-2815] — 👀 65% similar

Game rendering breaks down again, "Material ID exceeded range" spammed in console
Done • Priority: High • Fix: 4 - Early Access • Resolution: Done

Game rendering breaks down with "Material ID exceeded range" error spammed in console. This occurs when loading a savegame, possibly triggered after creating multiple large savegame backups while trying to revert to a previous save state. The error spam begins at line 6656 in the player.log file and continues until the end. The issue causes graphics to break down completely. Similar to a previous rendering bug but with a different error message.

4. [SPZ2-4429] — 👀 62% similar

FPS drop when switching between micro and macro
Done • Priority: Medium • Fix: None • Game: 0.0.9-rc7 • Resolution: Won't Fix

User reported experiencing FPS drops and lagging when switching between Machine View and Space View. The issue occurs during camera transitions between the zoomed-in building mode and the zoomed-out platform overview. The attached logs showed only DNS resolution errors for Unity services but no relevant performance data. Without the savegame file and PC specifications, the development team could not investigate further. The report was closed as won't fix after the user did not respond to foll...
💬 Threads: FPS drop

5. [SPZ2-2995] — 👀 60% similar

Game lags when zooming out or in (transition between viewmodes)
Done • Priority: High • Fix: 4 - Early Access • Game: 0.0.0-alpha23 • Resolution: Done

The game experiences lag and freezing when transitioning between view modes (Machine View, Space Platform, and Space View) in nightly builds. The lag can extend beyond one second, during which the game appears frozen but continues processing in the background, causing the camera to jump position after the freeze ends. The issue is more pronounced when scrolling with WASD during zoom transitions. Loading savegames sometimes causes the game window to crash temporarily before recovering. Autosav...

6. [SPZ2-1156] — 👀 58% similar

Shader settings to High/Extreme will cause severe glitch
Done • Priority: Medium • Fix: OLD Early Access • Resolution: Done

Setting Graphics / Shader quality to High or Extreme causes severe visual glitches on Mac mini M2 after alpha 7. The issue occurs when changing the shader settings in the game options menu. This results in consistent graphic rendering problems that affect game visuals. The bug is reproducible every time the Graphics settings are adjusted to High or Extreme quality levels on this hardware configuration.

Found 6 similar reports • Searched 3,128 reports • Use /check-duplicates to recheck

[balmy yoke]

Thank you for your report. We have seen the ticket and will take some more time to investigate.