Hop.Earth Not Loading, Black Screen or Stuck Parachuting

MOST COMMON

The world is loaded — it's just night there

"I spawned in and the screen is basically black. Did it fail to load?"

Hop.Earth runs on real-world time in the real-world place you're standing. Drop into a city where it's currently 2am local and you get an authentically dark planet. Nothing is broken, and reloading won't help — it'll still be night when you come back.

We hit this ourselves. The official lobby starts you in Monte Carlo, and on our first run the screen was almost completely black — two things stacked: it was night in Monaco, and the terrain hadn't finished building.

What to do: open the world map with M and move to the daylight side — if Europe is dark, try the Americas or East Asia. Full key list on our Hop.Earth controls page.

Still looks empty in daylight? There are no buildings

Plenty of people land in a major city, see roads and hills but no skyline, and conclude the map is half-loaded. It isn't. Buildings were cut deliberately, and the developers are blunt about why: "There are no buildings. Who needs them anyway? You can't drive on them."

So an empty-looking Manhattan is Hop.Earth working correctly. A missing road is a loading problem. Learn that distinction before you start changing settings.

TESTED BY US

You're not descending slowly — you're frozen at 2,000 m

"I've been falling for what feels like a minute and there's nothing below me."

On 8 August 2026 we went in with a real account to measure this properly, reading the game's own internal player state rather than judging by eye. What we found is worth spelling out, because as far as we can tell nobody else has published it.

You spawn at exactly 2,000 metres. That is the drop height, and it's why the parachute ride is long even when everything is working.

But it can stop being a ride at all. In one session the player object reported spawned: true, frozen: false, vehicle: null, and a position of x=1060, y=2000, z=-433. We sampled the altitude eight times, once every half-second:

Zero metres of descent in four seconds. Not a slow fall. Not a low frame rate. A complete stop.

And nothing gets you out of it. We held X for three seconds, pressed F twelve times and held W for two seconds — altitude, player state, vehicle and seat were unchanged after every one. Suspecting the game might be filtering out scripted input, we then drove the browser at a lower level and sent twenty genuine keypresses of W. Before: x=1060, y=2000, z=-433. After: x=1060, y=2000, z=-433. The character had not moved a single centimetre.

We also picked flat ground on purpose for that run — the Port Hercule waterfront in Monaco (43.7342, 7.4253) rather than the default hillside spawn — to rule out awkward terrain as the cause. It froze anyway.

How to tell which one you have: watch the ground for ten seconds. Getting closer, however slowly? Terrain is still building and waiting is correct. Absolutely nothing changing, and no key producing any response at all? You're stuck, and no amount of waiting will fix it.

What to do: if you're genuinely descending, wait it out — refreshing throws away everything your machine has already built and queues up the same long fall from scratch. Give it 20 to 30 seconds. If you're frozen, the opposite applies: reload hop.earth and rejoin, because there is no in-game key that recovers from it. Be warned that a fresh session can freeze too. Of our three attempts that day, two ended pinned in the air and the third never connected at all.

Why this matters more than it looks

A frozen character explains a whole category of complaints that normally get blamed on the controls. If every input is being ignored, then whichever key you happen to be pressing appears broken — so one player concludes F does nothing, another concludes holding X does nothing, and both walk away with a confident, contradictory answer. Both are describing the same silence.

So before you go looking for the right key, establish that the game is listening at all. Our full write-up of the evidence, including what the in-game help screen claims and what other players report, is on why your car won't spawn.

And to be clear about scope: this is not everyone's experience. The public race list carries real recorded runs at 186.34 km/h and 281.31 km/h, so plenty of people land and drive perfectly well. Treat the freeze as a bad roll of the dice, not a broken game.

You landed, but somewhere useless

If you do touch down off-road or somewhere hopeless, tap X to reset, or hold X to be returned to the nearest road. On foot with no vehicle in sight, the in-game prompt says holding X does something different again — it summons a car.

Two different failures that look identical

"The road just disappears, or my car drops through the world."

Tell them apart by looking around you:

• Nothing renders at all — blank in every direction, no road ahead or behind. That's a generation backlog: bandwidth and graphics horsepower. Stop moving and let it catch up.
• The road renders fine but you clip through at a junction. That isn't loading, it's broken geometry — a documented limitation.

The developers put a number on the second one: roughly 95% of roads and intersections render correctly, but many intersections are still broken. Fixing one bad intersection tends to fix many others at once, and the long-term target is 99.99% — so expect to meet a bad junction occasionally, on any hardware.

The official workaround is a key: "press and hold J to make your car jump over the broken geometry. It makes sense, because the game is called Hop.Earth!" That's not a community trick — the game's name is a reference to it. Hold J, clear the junction, carry on.

Where you drive changes how hard your machine works

The planet isn't rendered evenly. Terrain runs at a 30 m base resolution nearly everywhere, but France and Spain — including Corsica, the Balearics and the Canary Islands — go up to a 2 m grid, with more countries being upgraded over time. That finer grid carries vastly more elevation points per square kilometre, so those regions are both the most detailed places to drive and the heaviest to build. Our where to drive guide covers which areas earn the load.

OFFICIALLY ACKNOWLEDGED

Tile jank — the developers say so themselves

"It runs smooth, then freezes for a fraction of a second, then smooth again, over and over."

The world is divided into tiles, and each time you approach the edge of one your device has to build the next. The developers state plainly that "there's still some jank when approaching the next tile". The tell-tale sign is that the stutter is rhythmic and speed-dependent: drive faster and it happens more often, stop and it stops.

What to do: you can't remove it, but you can space it out. Ease off the throttle in a new area, hold off on Shift for extra engine power until the region has settled, and use M to travel long distances rather than driving them.