Error 321: two more causes fixed
1.2.11 and 1.2.12 fixed error 321 with AMD FSR and NVIDIA DLSS. This release goes after the two remaining causes seen in the reports.
1. The graphics card getting stuck (#154, #65)
A crash dump showed the card stuck inside one shader until Windows reset it. The renderer let two consecutive compute tasks run unordered ("dispatch overlap"). That's safe on the PS5's graphics chip, which always starts the first task before the second, but not on a PC card, where the second task can wait on the first while taking the whole card, so neither finishes.
- Fix: dispatch overlap is now off.
- Measured in Sky Garden (2 rounds each): the same average FPS (31.7 / 31.6 vs 32.5 / 30.4), and the occasional 300 ms freezes disappeared (worst frame 55-59 ms instead of 307-318 ms).
2. Running out of video memory (#155, #170)
At 4K on 8 GB cards, a large buffer (about 300 MB) sometimes fit neither in video memory nor in system memory, mostly on PCs with 16 GB of RAM.
- Fix: when that happens, the renderer now frees textures that haven't been used for a couple of frames, then tries video memory again, before falling back to system memory.
- Tested with simulated "memory full" failures during play: textures were freed on the spot and the game kept running. The real case could not be reproduced on the test PC (32 GB of RAM), so please report whether it helps.
- 1440p is still the recommended resolution for 8 GB cards.
How to get it
- 1.2.1 to 1.2.12: press Update in the launcher.
- New install: extract the zip into a new, empty folder and run
AstroHybrid.exe.
If you still get error 321
Please open an issue with Logs\hybrid-run.out.log and hybrid-run.err.log from right after it. The log now tells the causes apart.
SHA256 (AstroBotPC-AstroHybrid-1.2.13.zip): 2D3A96980C77E2107E4B48E448A7959A583FC6C7BABD65FD0283CD0C9169BAAE