Lag, GPU support and crashes in the WoW Forever beta: three problems, three checks
Laggy actions, a stuttering image and a game that shuts itself down had three different causes in the beta. This report covers Blizzard’s EU routing update of 21 Sept, the graphics-feature cutoff for GPUs, and the lighting tip players passed around for crashes.
After EU testers reported stalled movement, sluggish interaction and disconnects, Blizzard rerouted their traffic into the beta. That was a network fix and nothing more. A crash on entering the world or a poor frame rate points elsewhere: to whether your GPU is supported at all, and to the client’s graphics settings.
Performance at a glance
- EU routing update
- 21 Sept 2026Posted by Kaivax
- GPU cutoff
- GCN 1 · Maxwell · SkylakeAMD · NVIDIA · Intel, or newer
- Required feature
- RGBA16F UAVSupport in compute shaders
- Crash tip
- Secondary Lighting: FairPlayer tip from 18 Sept
From Blizzard’s routing post and GPU notice, plus one player-reported workaround; checked 14 Oct 2026.
| Symptom | Separate this out first | Go to |
|---|---|---|
| Actions land late | Animations may stay smooth while the client is still waiting on the server’s reply. | |
| The image stutters | Note frame rate and latency as two numbers; they measure different things. | |
| The game shuts down | Pin down the moment: before character select, on entering the world, or mid-play. |
Kaivax’s post Addressing EU Beta Routing Issues (opens in a new tab) explained that the early routing problems hit three things: moving, interacting with the world and staying connected. Over the 24 hours before the post, Blizzard had been changing how EU testers’ traffic reached the beta.
It also cautioned that some trouble could persist for reasons outside Blizzard’s control: a fault at your internet provider, indirect routing further upstream, or firewall software. What Blizzard committed to was continued monitoring, not a latency figure. There was no new regional data center and no target ping, only the route changes and the promise to keep watching.
A useful report sticks to observations, not guesses: the time, where you connect from, what stalled (movement, interaction or both), whether you were disconnected, and how often it recurs. Low frame rate and a slow server reply are two separate problems, even when one session shows both.
Connection report
Two separate numbers; note both.
Your report
Fill in the fields and the report appears here.
Nothing you type here leaves this page.
According to Blizzard’s GPU notice (opens in a new tab), a card needs at least AMD GCN 1, NVIDIA Maxwell or Intel Skylake architecture, or something newer. The deciding feature is RGBA16F UAV support in compute shaders.
| Maker | Oldest supported architecture | Passes the cutoff | Not supported |
|---|---|---|---|
| AMD | GCN 1 | Radeon HD 7850 | Radeon HD 6950 |
| NVIDIA | Maxwell | GeForce GTX 750 / 750 Ti | GeForce GTX 760 / 770 / 780 |
| Intel | Skylake | HD Graphics 530 | HD Graphics 6000 |
The passing examples are still below the game’s minimum specification, so meeting the cutoff promises nothing about frame rate. On Windows, look up your card under Advanced display settings, or under Display adapters in Device Manager, and check it against the full requirements that Blizzard’s notice links to.
Model numbers can fool you, as the NVIDIA row shows: the GTX 750 clears the line and the GTX 780 does not. Look up your exact card. If the feature is missing, turning settings down will not help; no slider can add hardware support.
One tip travelled fast: from the character select menu, set Secondary Lighting to Fair. For some players who crashed on entering the world it worked; for others it did not, and Blizzard never described it as a fix. To test it properly:
Stay at character select
Open the graphics options from the menu on the character select screen.Set Secondary Lighting to Fair
Leave every other setting as it is.Enter the world with the same character
Use the character that crashed, so you are comparing like with like.Still crashing? Keep the details
Keep the error text, and write down the build and the time, before reporting it.
Not a way around the GPU cutoff
The first days had their own causes, which Tom Ellis described and the beta guide records: a login limit, database delays and memory problems on the world servers. This report adds the later EU routing change and the checks you could run on your own PC. Read together, they show why no one “performance fix” could cover everything that went wrong in the first week.
The method that works: choose a problem you can reproduce, change one thing per attempt, and write the build and date next to each result.
OfficialBlizzard forums (EU)
Addressing EU Beta Routing Issues (opens in a new tab)
Kaivax’s post on the route changes, causes Blizzard cannot control, and continued monitoring.
OfficialBlizzard
World of Warcraft: Forever GPU requirements (opens in a new tab)
Architecture cutoff, required feature, example cards and a link to the full requirements.
CommunityBeta players
Secondary Lighting workaround, shared by beta players
Players who crashed on entering the world; results were mixed and Blizzard never confirmed it.
On this siteThis site
WoW Forever beta guide: access, what was open at level 30 and known bugs
The first week: login limit, database delays and memory trouble on world servers.