Guns of Eschaton Demo Crashing — Known Causes and Fixes

Crashes in the demo cluster into a small number of causes, and all of the ones the studio has acknowledged were fixed inside the first two weeks. If you are starting the demo now, you are running a build that has had five rounds of repairs.

The documented causes

Broken graphics auto-detection. The demo shipped with auto-detect assigning the Epic preset to machines that could not run it. That produced low frame rates, stutter and, on marginal hardware, instability rather than a clean error message. The studio acknowledged it on 6 October and shipped a fix on 7 October that makes detection pick the right preset.

If you have not patched, patch. If you have patched and still stutter, go to graphics settings and pick a preset by hand instead of trusting auto-detect.

Faulty items in the menus. A hotfix on 13 October removed a bug where incorrect, hidden or locked items appeared in the Abilities, Weapon Upgrade and Equipment menus. In some cases, the studio stated, selecting one of those items could cause a crash. If your game dies when you open a specific menu, this was the reason.

An aggro bug near a campfire. Resetting the world at the Muttering Path campfire and then shooting a ricochet object on the cliff could pull the Wraith into the tutorial area. That is not a crash on its own, but it is the kind of state corruption that makes the next encounter behave strangely. Fixed in the same patch.

The order to check things in

1. Update the demo. Five hotfixes have landed since 5 October. A build from launch week still contains every bug on this list.
2. Set graphics manually. Go to settings, pick a preset below what auto-detect chose, then raise it one step at a time. The 7 October fix makes auto-detect trustworthy, but a manual baseline removes it from the equation.
3. Leave the field of view at 75 while you test. The FOV slider is explicitly experimental, runs 75 to 90, and the studio has said the levels and encounters are balanced around the default. Changing it while diagnosing a crash adds a variable.
4. Try the lower-weapon option. Added in October along with a toggle-or-hold aim setting, it removes one rendering path from the first-person view. It is not a crash fix, but it is the cheapest variable to eliminate.
5. Check the storage type. The full game's requirements list an SSD as required, 45 GB. Running the demo from a mechanical drive is the most common cause of stutter that looks like a crash.

If the menu itself is the problem

One specific pattern was reported around the demo's menu system: unresponsive UI navigation and, on some gamepad models, a single directional press moving the selection two positions. The double-step was fixed in the 10 October hotfix. A "slippery" directional movement on certain pads was acknowledged in the same patch and remained under investigation at the time.

If your gamepad drifts in menus, that is a known track rather than your hardware failing. A keyboard works as a workaround for the menu-only case.

What to send the developers

The studio has asked for reports repeatedly and reads them — the fix list above exists because of that loop. If you still crash on the current build, the useful report includes the graphics preset you were on, the menu you were in when it happened, and whether the crash followed a campfire reset. Those three details map directly onto the bugs already fixed.

What "crashing" usually means in this build

Crash reports for the demo fall into three distinct categories, and they need different responses.

A hard crash to desktop. The documented cause is the menu bug where invalid items appeared in equipment and ability screens. If your game dies specifically when you open a menu, that is the tracked issue and it was patched in October.

A freeze or long hitch. Almost always assets streaming from slow storage, or a preset the machine cannot sustain. The SSD requirement exists for this reason, and the graphics auto-detect bug made it much worse in the first week.

A failure to launch at all. Different problem entirely, and usually a driver or DirectX 12 issue rather than the game. Verify the demo's files, confirm your GPU supports DX12, and check that the launcher is not being blocked by security software.

Sorting your symptom into one of those three categories is faster than working through a generic checklist.

When to stop troubleshooting and report it

If you are on the current build, the preset is manual, the game is on an SSD and it still crashes in the same place every time, that is a report rather than a settings problem.

The studio reads them, and the fix list above exists because players sent them. A useful report names the preset, the menu or location, and whether a campfire reset preceded the crash — those three details map onto the bugs the team has already fixed, which is how they found them.

The settings that matter more than the ones people tweak

Most troubleshooting advice for a shooter concentrates on the wrong dials. In this build, four settings do almost all of the work.

Preset. The single largest variable, and the one the launch bug corrupted. Set it manually.

Resolution scale or upscaling. On a card near the minimum, dropping the internal resolution is worth more than every other setting combined. The game already supports the standard upscalers, and a lower internal resolution at native output looks better in motion than it sounds.

Shadows and volumetric lighting. The two heaviest effects in an Unreal Engine 5 title. Lowering both is the usual first move on a GTX 1070.

Texture pool. On a 16 GB machine, this interacts with the SSD streaming budget. Raising it past what the drive can feed produces hitching that reads as a crash.

Set the preset first, then move one dial at a time. Changing four settings between tests tells you nothing about which one helped.