Loading screens are cloud gaming's underrated failure mode

One of the bullet points in early cloud gaming marketing: no install times, no patch downloads, no waiting. The game runs on a server that's always warm and you jump in instantly. The friction of local PC gaming — download, install, patch, launch — was supposed to vanish on the cloud side.

The reality five years in: cloud gaming sessions still take 30-90 seconds to start, in-game loading screens still take 10-60 seconds, and reconnection after a session timeout costs another 30-60 seconds. The cumulative friction is sometimes worse than a fully-installed local game.

Cloud session warm-up. When you click 'play' the cloud service has to allocate a VM, attach a GPU, sign in to the game platform (Steam, Epic, Xbox), launch the game, and start streaming. This is the 30-90 second wait at session start. It cannot be parallelised with playing because the game isn't running yet.

In-game loading screens. Once the cloud session is running, the game itself loads levels, assets, and shaders. These loading screens are roughly the same duration as on local hardware because the cloud GPU has to do the same disk reads and asset decompression a local rig would. The cloud doesn't accelerate this.

Reconnection. When a cloud session times out (4-8 hours typically) or the user reconnects from a different device, the warm-up cycle repeats from a paused state. Some services preserve the session VM for a few minutes; most don't.

The cloud service can't pre-warm a session for a specific user without paying for an idle GPU. The economics of cloud gaming depend on packing many users onto a smaller GPU fleet, which means a user-specific warm session is a cost the cloud service can't bear at consumer pricing.

Some services pre-warm 'pools' of generic sessions and assign them on demand. This drops the user-visible warm-up from 60s to 20s but doesn't eliminate it because each session still needs game-specific setup (sign-in, game launch).

The hidden constraint: every minute of GPU time the cloud service spends on warm-up is a minute they could be selling to a paying player. Aggressive pre-warming is bad cost discipline at current prices.

GeForce Now Ultimate's session start time on a previously-played title is meaningfully better than it was in 2022 — typically 20-40 seconds for an established Steam library title. The improvement came from VM pool optimisation and Steam pre-authentication.

Game Pass Cloud's session start has gotten worse, oddly, as the catalogue has grown. The session-spawn logic now has to make a catalogue-specific routing decision and the routing adds 5-10s on average. Microsoft hasn't acknowledged this regression.

PS Plus Premium's session start is competitive on PS5 hardware clients and slow elsewhere.

Cloud session timeouts are inevitable — the cloud service has to cycle GPUs through the user base. But the user-visible reconnection penalty is poorly handled. The session 'pauses' from the user's perspective and 'ends' from the cloud service's perspective and the reconciliation between those two views is messy.

What I'd want: a 5-minute grace window where the session VM is preserved and reconnection is sub-5-seconds. After 5 minutes, the VM is recycled and reconnection means a full warm-up. None of the major services ship this cleanly. GeForce Now's Priority tier comes closest with a roughly 2-minute grace window.

Cloud gaming has not eliminated waiting. It's eliminated one kind of waiting (install/download) and added a different kind (session warm-up, reconnection). For some players the swap is favourable; for others it isn't. The 'no waiting' marketing was always going to be partially false because game-level loading is independent of where the game is running.

If you're considering a cloud subscription primarily to avoid install times, the actual time savings are smaller than the marketing implies. You'll wait less to start a new game; you'll wait roughly the same amount once you're inside a game; you'll wait more across the boundary between sessions.