Flock of the Seraphim Crash Fix

Launch week produced more crash threads than build threads. People stuck on the startup loading screen, people who crashed twice in twenty minutes on a high-end card, people whose achievements did not pop, people who said the save felt bricked. This page collects the public developer replies and the boring local checks. It is not a promise that every machine will run a Godot horde shooter.

If the game already runs and you only want to play, leave. Use Getting Started.

Try the DX12 boot option first

On a loading-screen review, GuuchanDev wrote that new boot options were coming and that the first one — play using DX12 — might help. When that launcher list appears, pick it before you reinstall for the fourth time. Several “I keep crashing when I load” posts are the same symptom with different titles.

If DX12 does nothing, the same reply says your specs may sit under the minimum. The store minimum is Windows 10 64-bit, a six-core Ryzen 5 class CPU, 6 GB RAM, a GTX 1060 class GPU, and 1 GB of disk. One public crash review was on an Iris Xe laptop. That is below the listed GPU line. The review repeats the table so you can refund with a straight face if you have to.

Video options that actually exist

The first big demo update added a max FPS cap and a preferred display picker. A later demo note said you can lower anti-aliasing to raise FPS. Use those three before you buy a new cooler.

• Cap FPS to your panel. Uncapped bullet soup is how late Endless clips stutter.
• Pick the correct monitor if you run a dock or a second screen. A tiny window thread already exists.
• Drop AA if the flock turns into a slideshow at minute twenty. The Endless guide assumes you already did this.

Sound is thinner. A review said there was no sound options page and that the first boot needed the Windows mixer. If the nun screams at 100, lower the executable volume there, then look again after a hotfix. Do not assume a missing slider is your headset.

Achievements that will not unlock

A launch review said in-game goals completed but Steam stayed dark, and the machine also crashed. The developer answered that an achievement hotfix was due within an hour and that boot options might help stability. If a master or Exorcist banner appeared in-run and Steam still shows a lock, wait for Launch Hotfixes, then reboot the client. Do not grind the same family for three hours on a known tracker bug.

The public achievement names worth checking are Exorcist, Pistol Master, Slayer, Kill Master, Kaboom, Roll Back To Hell, Shotgun Master, Bow Master, Rifle Master, and Resiliant (the store spelling). Tick them on the unlock checklist only after Steam agrees.

When a run crash looks like a weapon bug

On a “crashed twice in twenty minutes” review, GuuchanDev asked which weapons were in the flock. If you can reproduce a hard close, write the family names: dual swords, RPG, shotgun, and so on. That report is more useful than “game bad.” After you send it, try a flock without the last recruit and see if the client lives. The weapons page is the family vocabulary.

Force-closing during a result screen is how keeps vanish. If your flock looks empty after a crash, read How to Unlock Angels before you assume the account is bricked. Steam Cloud is listed; give it a minute, then relaunch.

Verify files, then stop looping

Steam’s verify integrity pass is the next boring step. Reinstalling five times without DX12 or a spec check is the loop already on the board. If verify fails, fix the disk. If verify succeeds and DX12 still dies on a 1060-or-better box, you have a real ticket for GuuchanDev@gmail.com, which is the support line on the store API.

This page will go stale when the boot menu changes. Check the hotfix log before you quote it in a month. Until then, the order is: DX12, spec line, FPS cap, AA, verify, then a short weapon note. Everything else is a play problem, not a boot problem.