[1.03-rc3] Milestone screen not respecting fps cap

[lavish cypress]

System: Intel i5-12400F, RTX 3060, 32 GB Ram, Windows 11.
Settings: FPS capped at 60.
Issue: When watching milestone screen one of my fans speed up a lot.
Cause: Probably the above. Currently I just try to check the milestone screen faster so it doesn't trigger as much.

[viral helm]

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 86 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 Log files help us investigate issues. You can find yours here:
• Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

💾 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:
• Windows: %USERPROFILE%/AppData/LocalLow/tobspr Games/shapez 2/

1. [SPZ2-5330] — 👀 72% similar

Unlocking a milestone the auto side scroll wobbles weirdly with the frame rate limiter is set to 30
To Do • Priority: High • Fix: 1.1 Release [1.1.0]

When unlocking a milestone, the auto-scroll animation on the Milestones Screen wobbles erratically when the FPS limiter is set to 30 in graphics settings. The issue is more pronounced for later milestones such as milestone 4 compared to milestone 1. It can be reproduced by limiting the frame rate to 30fps, starting a new Manufacture Mode save, and unlocking milestones. The expected behavior is that the auto-scroll animation should be smooth regardless of the frame rate setting. This issue has...

2. [SPZ2-3309] — 👀 55% similar

Knowledge Panel "Basic Controls" page is lowering performances
To Do • Priority: Low • Fix: None

Opening the Basic Controls page in the Codex causes significant performance drops across the entire game. When this specific page is selected, FPS drops from around 80 to 50, and the performance impact persists even outside the game window. Other Codex pages with similar or more content do not cause this issue. The problem is reproducible by launching an empty game with everything unlocked and navigating to the Basic Controls page in the Codex. This suggests a performance bug specific to that...

3. [SPZ2-3375] — 👀 40% similar

FPS unlocked at 60 but locked at 30
To Do • Priority: Low • Fix: None

The player reports that FPS (frames per second) behavior is inverted on Mac Mini M2 with 16GB RAM. When FPS are unlocked, the game runs at approximately 60 FPS, but when FPS are locked to 60, the actual framerate drops to around 30-35 FPS. Additionally, the player cannot achieve more than 60 FPS regardless of Graphics settings. The expected behavior is that locked FPS should maintain the target framerate, and unlocked FPS should allow higher framerates based on hardware capability.

4. [SPZ2-5627] — 👀 35% similar

FPS limit not applied in editor
To Do • Priority: Lowest • Fix: None

The FPS limit setting does not persist correctly when launching shapez 2 in editor mode. When the game is set to limit FPS to 30 and then restarted, the frame rate becomes unlimited again even though the setting still shows the correct value. This issue only occurs in editor mode and does not affect the main menu. The expected behavior is that the FPS limit should remain active after restarting the game when the setting is configured.

5. [SPZ2-6023] — 👀 30% similar

Vsync set to "on" has no effect when playing on a STEAM Beta 2 build.
Done • Priority: Critical • Fix: 1.0 Release [1.0.0] • Resolution: Not A Bug

When Vsync is set to "on" in the Steam Beta 2 build of shapez 2, it has no effect and the game pushes as high an FPS as possible instead of capping to the monitor's refresh rate. The "Half" and "Third" Vsync settings function correctly, limiting FPS to 120 and 80 respectively on a 240Hz monitor. The issue appears specific to Steam builds, as local builds work correctly. Expected behavior is that Vsync "on" caps FPS to the monitor's refresh rate. The issue was closed as not a bug after other u...

Found 5 similar reports • Searched 3,528 reports • Use /check-duplicates to recheck

[rain summit]

Thank you for your report @lavish cypress ! I don't seem to be able to reproduce this issue on my system. Would you be willing to record this issue occurring with the following debug enabled in Console?

Just press F1 and type 'debug.show-charts' and it should show you the FPS at every time

[lavish cypress]

I have now looked at it further - it is not a FPS issue. The FPS limit is respected on the milestone screen. I checked my CPU usage and for some odd reason something on the milestone screen is very CPU intensive. My CPU usage is 45% when looking at that screen and then down to normal when I close it.

[viral helm]

✅ Thank you for providing further information, our team will have a look again!

[lavish musk]

I think it's instead the videos that cause a lot of CPU usage

Can you try disabling them in the settings? "Animated Content" or so

[lavish cypress]

Turning 'hover-to-play-videos' on solved the issue.

[lavish musk]

@QA seems that's a good fix for lower-end setups / CPU bound systems