Getting The Lost Bus to Actually Run
I spent about three weeks chasing down why my install kept failing. Not because the game was bad, but because the documentation for it is written in a way that assumes you already know the ecosystem around it. If you're just looking to play, you can grab it from GOG or the Steam store page, but the clean install on Windows 11 is trickier than it should be. The basic steps are simple enough: download, run the installer, and let it place everything in your Program Files folder. The problem is that the game's middleware uses an older DirectX runtime that doesn't ship with modern Windows by default. So you'll need the DirectX End-User Runtime from Microsoft's website before you even attempt the installation. Without it, you'll get an opaque error code and no clear indication of what went wrong.
The Lost Bus and Save File Quirks
Once it's running, the save system does something most people find annoying. It writes your progress to AppData\Local\LostBus\Saves rather than in the game directory where you'd expect it. If you've ever tried cloud syncing through Steam, you'll notice the sync works fine but the backup shows a one-minute delay. The developer confirmed this is intentional; the game waits after a checkpoint to batch-write multiple save slots at once, which avoids corruption but means you lose progress if the game crashes within that window. I hit this exact issue during a boss fight on a Steam Deck. The game stutters on that hardware when you push the render scale above 100%, and on my run, it crashed about thirty seconds before a checkpoint. Everything since the last batch write was gone. I worked around it by using a save editor script to extract the existing slot and manually restoring it. There's no official save-editor support, so that path only works if you're comfortable manipulating JSON files. Otherwise, the real fix is just playing conservatively on Deck and keeping render scale at or below 100%. Performance-wise, the game runs fine on anything with a GTX 1660 or better at medium settings and 1080p. I tested on a Ryzen 5 5600X with 16GB RAM and saw a solid 55 to 60 FPS average, dipping to about 42 during heavy particle sequences. Those drops aren't a profiling issue; the developer has been mostly responsive about patches. The main ongoing complaints from the community are around the audio stutters that happen when switching between dialogue-heavy scenes and combat, which usually means the background music stream isn't preloading fast enough on slower NVMe drives. I haven't found a fix for that one beyond closing background apps and using a dedicated SSD for the game install.
If you're considering installing it alongside another Unity-based title, watch out for DLL conflicts in the Redist folder. I ran into that on a second machine and the game would launch but freeze at the title screen until I renamed the conflicting assembly in one of the other games' installations. It's a minor thing, but it can waste an afternoon if you're not expecting it.
Get the Full Details
