Why does my game hitch when I enter a new area?

Because it's loading that area's assets on demand at that moment, synchronously during gameplay, which blocks the transition frame and causes a stall. It's often compounded by shader compilation (the new area's effects compiling their shaders on first use). The transition frame gets a big chunk of unbudgeted loading work and hitches.

How do I stop loading hitches when streaming new areas?

Load ahead of time instead of on the transition frame: preload or stream the next area's assets in the background before the player reaches it (or during a loading screen), so they're ready and don't block the frame, and warm up the new area's shaders ahead of time. The principle is to anticipate the load and pay it before the transition, not during it.

Why is the hitch worse on some players' machines?

Because loading time depends on storage and CPU speed, a load that's quick on your SSD is slower on a player's hard drive or constrained device, so the on-demand load blocks the frame for longer there, making the hitch worse. Field performance data shows the hitches on players' hardware. Background/ahead-of-time loading helps all hardware by moving the load off the transition frame entirely.

Why Does My Game Hitch When Loading New Areas?

Quick answer: Your game hitches when loading new areas because it's loading assets or a level chunk on demand during gameplay, which blocks the frame it happens on, producing a stall. It may be compounded by shader compilation (shaders for the new area compiling on first use). The fix is to load ahead of time or in the background rather than during the frame the player crosses into the new area.

A hitch when entering a new area, a stall right as you cross a threshold, is the game doing loading work during that frame instead of ahead of time. It's a frame-pacing problem tied specifically to area transitions, which makes it predictable and fixable.

Why New Areas Cause Hitches

When the player enters a new area, the game needs that area's assets, and if it loads them on demand at that moment (synchronously, on the main thread), the loading work blocks the frame, causing a hitch. The bigger the load, the worse the stall. Shader compilation often compounds it, the new area's effects/materials compile their shaders on first use, adding more hitch. So the transition frame gets a big chunk of unbudgeted work (loading plus possibly compiling), and stalls.

It's predictable, tied to crossing into new areas, which is exactly what makes it diagnosable: the hitch correlates with the transition, pointing at on-demand loading there.

How to Diagnose and Fix It

Profile frame time around an area transition, you'll see a spike on the transition frame, and the profiler shows it's loading (and possibly shader compilation) consuming that frame. Bugnet's performance monitoring captures these hitches and where they occur, confirming they correlate with area transitions on players' hardware (worse on slower storage).

Fix by loading ahead of time: preload or stream the next area's assets in the background before the player reaches it (or during a loading screen), so they're ready and don't load on the transition frame, and warm up the new area's shaders ahead of time. See our guides on fixing stuttering and spikes/hitches for the details. The principle is to anticipate the load and pay it ahead, not on the transition frame.

Hitching at area transitions is on-demand loading (and shader compiles) blocking the frame. Preload or stream the next area in the background ahead of time, and warm up its shaders.