Identify what is actually blank
A black scene, a white embedded window and a visible launcher that is still downloading are different symptoms. Note whether text, a progress indicator, a menu or a connection message is present. A page around the game can load successfully while the third-party project still needs assets or a server.
If progress continues to change, let it finish before restarting. This guide does not promise a fixed waiting time: first loads depend on the connection, browser profile and project. The App’s “window loaded” message confirms an iframe load event, not successful gameplay.
Find the next stage for your player
- QuakeWorld: the name field and Play button come before an arena connection. A connection message can involve a live server; it is not the same as a missing game-data file.
- Uplink: WebXash starts with its demo selector. Choose Uplink (45M), then Start Demo. A game menu is followed by New game and a difficulty.
- Diablo: Play Shareware downloads the limited version. Once the menu appears, choose Single Player and create a hero. Select MPQ is a different branch for an owned full-game archive.
Compare the same project outside the embed
Use Open original beneath the game window. Choose the same version in that separate tab so you compare like with like. If the original works and the embed remains blank, a browser storage restriction or a change to project embedding may be involved. That is a possible explanation, not a diagnosis this App can prove.
Use the working original tab for the session. If both contexts fail at the same stage, the result points toward project, asset, network or device conditions shared by both. RadiantGames cannot repair a remote server or inspect a third-party project’s private storage.
Restart once you have a useful comparison
Restart replaces the current embedded window and begins its launch sequence again. Close removes that window and restores the ready screen. Neither action exports a game save. Use them when you are ready to leave the current attempt, rather than repeatedly refreshing a download that is advancing.
Keep one active player while troubleshooting. Two game tabs can have different versions, focus or session states. If you compare an original tab, close the unused attempt before continuing so you know which scene you are controlling.
Protect progress before changing stored data
Clearing browser data can remove information belonging to the game project and force another asset download. A RadiantGames bookmark is separate from that information. Check the original project’s save and export instructions before removing anything.
When reporting the issue, include the project URL, chosen version, visible screen, whether progress changed, device/input method and whether the original tab behaved differently. These observations are more actionable than “the game is broken.” Do not include personal game archives in a public report.