Match the symptom before changing settings
| What happens | What to do next |
|---|---|
| Performance gets worse after hours of play | Rest in bed to save. Preserve the log if reporting, then close and relaunch. Compare the same area immediately after restarting. |
| A severe FPS drop happens specifically while saving | Steam 1.007 (September 28) announces a fix for saving-related drops. Check your installed update first; this does not establish that long-session slowdown is fixed. |
| Crashes on an ultrawide or unusual resolution | Steam 1.006 (September 25) announces a fix for intermittent crashes at those resolutions. If it persists after updating, record resolution, build and log. |
| Endless loading or a crash while opening a save | Steam 1.008 addresses a conveyor-related endless load; 1.009 addresses another load-time crash. Preserve the save and log, check the update, and report whether loading hangs or the game closes. Do not overwrite a save to test a theory. |
| Going to bed crashes or throws the character outside the scene | Steam 1.008 names this bed-specific fault. Check that patch before repeating the action; this differs from an ordinary FPS drop during saving. |
| A widescreen scene appears cut off | Steam 1.009 expands scenes to address cropping. Cropping, resolution-related crashing and low FPS are separate symptoms. |
| NPCs freeze and time stops on PS5 or Xbox | The publisher marks this exception as fixed and asks you to update. Its current page still describes a PS4 patch as in progress. Record your installed version if the freeze remains. |
| Frame drops from the start on PC | Use the PC checks below, changing one setting at a time. |
| Tearing on console | The publisher lists this as a current issue. No confirmed console-specific fix is listed. |
| Switch slows near the base with piles of logs or sticks | An older Demo report connected this to repeated drops from a glowing tree or bush. The current official list does not establish whether that issue remains in the released build; record the scene and build before assuming the cause. |
The official Steam patch notes support the update checks above. They do not confirm equivalent fixes in every console build. The comparison separates session slowdown, saving and display-related crashes; it is not an FPS benchmark.
Current issues that are not performance problems
The support page now groups stuck stations, iron deliveries, out-of-bounds points, missing soldier rewards and partial-stack chest loss as fixed by 1.007 on most platforms, with Switch 1 and 2 still awaiting that patch. Graphics changes will not address those symptoms. Use the known-issues symptom index to distinguish official temporary steps from problems with no published workaround; for a stopped worker, use the zombie worker checks. Older Demo reports about workbench overconsumption or zombie unspent skills are not on the current list; their release status is unknown.
Issue list and Steam patches checked September 29, 2026. Match platform and version: neither a stale listing nor its removal proves the outcome in your save.
Items disappeared while filling a chest?
The official known-issues page places partial-stack chest loss in its 1.007 fix group for most platforms, still pending on Switch 1 and 2. In the affected builds, a transfer into a nearly full chest can lose the portion that does not fit. This is a storage-transfer bug, not a graphics or framerate problem.
Before moving a valuable stack, leave enough storage space for all of it; avoid deliberately testing a partial-fit transfer. This is a precaution, not a verified fix or a way to recover items already lost. If it happens, keep the save and record the item, stack size, free storage space, platform and build for the support report below.
Warning checked September 29, 2026. Do not assume a fix without a current patch note or a check in your build.
PC checks, in order
- Check the publisher’s minimum requirements before trying graphics changes.
- Lower resolution or graphics quality. Revisit the same scene and note whether the symptom changes.
- Temporarily disable overlays, such as Discord or Nvidia App. Test again.
- Update GPU drivers and Windows, then verify game-file integrity in Steam.
If a change does not help, record that result. Avoid changing every setting at once: you will not know which change mattered.
Console-specific checks
- PlayStation: use the publisher’s linked cache guidance or internal storage where applicable. Restore licenses only for authorization problems, not as a general FPS fix.
- Xbox: after saving, restart the console; tinyBuild links the procedure for holding the console’s Xbox button for at least 10 seconds. Use internal storage where applicable.
- Switch: try system storage if installed on SD, restart, and check for corrupt data or software updates. Cache reset removes saved website IDs, passwords, cookies and history; it is not the first step for every slowdown.
The general troubleshooting source below links the platform-specific procedures. Do not choose a factory reset or erase save data.
Save useful evidence before relaunching
Steam PC 1.006 adds an in-game bug-report option. If your build lacks it, use the official support route below; no console menu path is implied.
On PC, copy Player.log before launching the game again. The publisher says it resets on launch. Requested save files are .dat and .info, in:
%USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2
Send files only through official support, not public comments or this fan site. Include platform/build, the affected scene, the steps that reproduce it, and whether a fresh launch helps. Screenshots or video are useful on consoles.
Verification notes
- tinyBuild general troubleshooting — platform steps and PC save/log location.
- tinyBuild extended-session performance guidance — save and relaunch after several hours when memory accumulation causes temporary drops.