Hotfix v.1.5.102

DriveWave · published

Hey everyone,This time a pure hotfix. A few of you posted on the forums this week about the game launching, showing up in the taskbar, and then... not actually being there on the desktop. A couple of others noticed FPS dropping since the last patch. Both should be fixed, both in this build.🖥 The window comes back

  • If your monitor was shorter than the window the game was trying to draw (most 1080p setups once you scaled the window up), it was getting centered partially above your screen — title bar in negative territory, the rest clipped by the top edge. Steam showed it running, the taskbar showed the icon, there was just nothing to click on.

  • The window now clamps to your actual monitor before it picks a position.

  • If your saved scale is too big for the current monitor, the game steps down to the largest scale that actually fits — for this session only. Plug back into your bigger display and your preferred scale comes back.

  • Players from a couple of patches ago: your saved window position is preserved. I renamed the keys that stored it and forgot to migrate the old ones (whoops). That happens quietly on first launch now, which means the game no longer falls back to a default position that doesn't fit.

  • Ctrl+R still resets the window to the center if you've been fighting it.

💾 Save system stops punching the frameFixed the FPS drop a few of you reported since v1.5.100. Short version: there were around twenty places in the code that wrote to disk synchronously on the main thread during gameplay. Every biome switch, every volume slider move, every environment level-up would stop rendering for a few milliseconds while the full save state hit the disk. On a small save with a fast SSD you wouldn't notice. With a fuller save and a slower drive some of you were eating 5-50ms hits multiple times a minute.

  • All of those writes now go through the background save thread the game already had running.

  • Same data safety — the cache is updated instantly, the disk write just doesn't block your frame anymore.

  • Quit and app-close paths still write synchronously so nothing gets lost when you close the game.

Expected result: smoother gameplay, most visibly when the environment switches and when you're dragging volume sliders.🧪 One quiet thing

  • The first-time-drag tutorial was writing directly to disk instead of going through the save wrapper. Rare corruption risk if the timing lined up badly — no reports of it happening, but it's cleaner now.


As always: if something feels off, Discord is the fastest way to reach me. Forums work too, I just see Discord first.Thanks to everyone who posted about the game not showing up — that thread is exactly how I saw it.See you on the road.
– Tolga 🏁

Hotfix v.1.5.102 · DriveWave patch notes · SteamPeaks