If the floor is missing after the Bronto chase rock gap and every respawn drops you into empty space, you may be encountering a reported level-loading failure rather than missing a jump. Steam full-game patch 1.0.9 addresses some level-loading problems, but recovery of an already affected save is not confirmed. There is no verified universal workaround for this exact fall loop.
This applies to the full game's cavern progression. The verified version baseline is Steam 1.0.9, dated October 30, 2026. It does not establish the version or fix status of the Xbox, PS5, or Epic build. Demo version 0.9.76 belongs to a separate application and cannot establish whether this full-game problem is fixed.
Identify the failure before repeating the chase
The reported problem occurs after a Bronto chase when you pass through a narrow rock gap. The critical symptom is absent ground on the other side. A failed parkour attempt can also end in a fall, so look at what the game presents when control returns: a visible landing surface that you miss is a different situation from an empty area where the next part of the level should exist.
If a respawn immediately puts you back into the same fall, repeated attempts may provide no new information. Note whether you regain control on solid ground, inside the gap, or already below the playable area. Those distinctions make a useful problem report and help establish whether you have a route to retry at all.
Use the creature and rocky ledges to distinguish the early cavern chase.
A separate report describes a similar repeated fall after entering water in the second level. Keep that trigger separate from the rock-gap transition. The symptoms overlap, but a shared symptom does not prove a shared cause or guarantee that one recovery method applies to both.
Check the build on the affected platform
On Steam, make sure the full game has received the available update before making another attempt. Patch 1.0.9 is the confirmed baseline for some level-loading corrections. The wording does not establish that every rock-gap fall is repaired, and it does not guarantee that an existing checkpoint will be rewritten into a safe position.
For a console or another PC store, check the update offered by that platform. Do not assume that an update with a different number is older or newer than Steam 1.0.9, or that the same changes arrived simultaneously. An update is worth applying; its presence alone is not proof that this specific save can continue.
The full game and demo have different Steam application identities: 2920220 is the full game and 5244130 is the demo. If you are comparing patch notes while troubleshooting, confirm you are reading about the installed application. A demo movement adjustment is not evidence of a full-game cavern fix.
The full-game patch number is separate from the Demo version; compare it with your installed build.
Try recovery without discarding progress first
Use the least disruptive available action first. If you can return to a menu, exit normally and reopen the game before assuming a new run is necessary. This is a general loading check, not a confirmed fix. Record the result: does the ground appear, does the same checkpoint repeat, or does the game load a different safe position?
If the game offers an existing checkpoint reload, distinguish it from restarting a chapter or beginning a new game. The supplied information does not verify an earlier-save selection feature, a rollback command, or a safe file-editing method. Do not delete your progress because an unverified suggestion promises that it will reset the missing terrain.
A sensible sequence is:
- Record the platform and installed full-game version.
- Capture the missing floor and the place where the respawn begins.
- Apply an available update through the platform you use.
- Reopen the game normally and check the same transition once.
- Stop repeating the loop if the state is unchanged and preserve the existing progress while seeking a platform-specific resolution.
This sequence cannot promise recovery. Its purpose is to avoid turning a loading problem into unnecessary progress loss while establishing what actually changes after an update or relaunch.
Keep other Bronto blockers separate
The second Bronto hunt also had a reported invisible wall after falling rocks. Steam 1.0.9 explicitly lists a correction for that blocker. An invisible barrier across otherwise visible terrain is not the same symptom as missing ground followed by a repeated fall.
Likewise, the gift-shop basement door involves floodlights and progression state in an earlier area. Reported shelf-jumping advice for that door is not a rock-gap solution. Trying unrelated collision bypasses at an unloaded cavern transition has no verified benefit.
What to include when the loop remains
Give the exact sequence leading into the failure: the Bronto chase, the narrow gap, the missing floor, and whether respawning repeats the fall. Add your platform, storefront where relevant, installed version, and whether the problem began before or after an update. A short recording showing both the first fall and the next respawn is more specific than describing the entire level as broken.
State separately which recovery actions you tried and what each changed. If reopening the game leaves the checkpoint unchanged, say that directly. If terrain returns but you still fall during movement, that is a different result and should not be described as the same missing-floor state.
No verified save repair, guaranteed alternate route, or confirmed console patch mapping is available for this exact rock-gap loop. Until one is established, retaining the save and documenting the trigger is more defensible than presenting a speculative jump sequence as a working solution.