Terrible Lizards crashing

Choose the symptom closest to what you actually see. A process that closes with Fatal Error, a level that fails to appear, a character unable to sprint and a scene that remains playable at low frame rate should not be treated as the same problem. Note the last checkpoint and whether the failure repeats after the same action.

Record Steam, PC Game Pass, PlayStation 5 or Xbox Series separately, together with the game version and date. A report about one storefront does not establish the condition of another build. Also distinguish the released game from the earlier demo before applying advice from an old discussion.

The developer’s October 30 changelog names several specific fixes. It does not say that every crash, streaming issue or hardware combination is now resolved. Confirm that your installed build includes the update, then check the original problem again before trying another change. Console update timing is not established by the PC announcement.

Useful matches include a title screen remaining over gameplay, Stella calls locking buttons, immediate slide deaths, controller sprint lockouts and levels failing to load or unload. The second Bronto hunt’s invisible collider and the second Allo hunt’s four-fuse issue also appear in the official list. Those are developer statements, not fixes we reproduced in the game.

First write down the exact error and whether the game reaches its title screen. Finish pending game/client updates and use the appropriate storefront’s built-in file verification or repair controls. Restart and test the same point once. This is a conservative troubleshooting sequence, not proof that damaged files caused your failure.

Do not delete save folders, replace random DLLs or install an unofficial “crash fix” to follow this guide. Preserve your existing game data. Website JSON backups contain only manual checklist records and cannot restore a damaged game save. For repeated failures, keep a short record of what changed and send it through the developer’s official reporting channels.

Compare your hardware with the separately listed PC requirements, but do not turn a matching GPU name into a promised frame rate. The store gives minimum and recommended components without a published target resolution or FPS. A performance complaint does not by itself prove a memory leak or a particular driver fault.

Players have reported different results even with similar RTX 3070 systems. One Game Pass player said a different graphics preset and upscaler got past a failing point; that is one reported workaround, not a verified general fix. If you test graphics options, note the originals, change one option at a time and restore it if the result is worse. Avoid BIOS or registry changes based on forum guesses.

Check the official patch matches before rebuilding your control setup. Controller sprint lockout and several loading/unloading problems are explicitly named in 1.0.9. An unresponsive button after a Stella call may also be a progression issue rather than a broken controller. Record when it began and which platform/build you used.

If the game remains responsive but you cannot find the next action, use the chapter walkthrough instead. Its prerequisite/action/result checks address route confusion, not software crashes. Similarly, the four-plush tracker records your own challenge progress; it does not repair checkpoints or unlock a blocked event in the game.

Include the platform and storefront, version, CPU/GPU/RAM when relevant, the exact message, chapter and landmark, last successful action and whether the same failure happens again. State which reversible changes you tried and what happened. An error screenshot can help, but remove account details and unrelated personal information before posting publicly.

Use the developer’s linked Steam discussion or official support community, and read its pinned instructions first. This website does not collect crash dumps, account passwords, reward codes or save files. We organize official notes and attributed player observations; we have not benchmarked the game or confirmed the reported workarounds.