The checklist takes up space
Use Focus view; it keeps the same player window.
RADIANTGAMES APP · SESSION SUPPORT
Make room for the game: focus view and fullscreen
Make a browser player larger using Focus view or fullscreen. Understand mouse capture, Escape, narrow screens and the original-tab fallback without restarting.
Start with what you can see.
You want the browser display filled
Use Fullscreen after a deliberate button click.
The view is large but aiming fails
Click the scene and follow its mouse-capture prompt.
KEEP THE PLAYER IN REACH
Which session are you working on?
Choose the player so you can return to the same launch instructions.
Choose a player →
The guide works without selecting a player.
THE NEXT USEFUL CHECK
Keep one clear step in view.
Focus view keeps the same running window
Focus view expands the player layout and hides the side checklist. It does not replace the embedded window or restart the project. Use Show checklist when you want the launch instructions beside the game again.
This is useful when screen space is limited but you still want the surrounding toolbar. On a narrow screen, the checklist already follows the player vertically; enlarging the page does not add touch controls to a keyboard-focused game.
Fullscreen changes display, not the game version
The Fullscreen button asks the browser to enlarge the game window. It needs an intentional user action and browser support. Exit fullscreen or use Escape when you want to return to the page. The game’s own menu may also have a fullscreen option.
If the request is unavailable, use Focus view or Open original. Neither a larger display nor a new tab supplies missing game files or changes shareware into the full version.
Aiming still needs the game’s input context
Mouse capture and fullscreen are separate capabilities. The browser can show a large game while the pointer still belongs to the page. Click the actual scene and follow the project’s own capture prompt. After Escape releases the pointer, focus the scene again.
If movement remains unresponsive, check the input guide and project bindings. Repeated fullscreen toggles cannot fix an arena connection or an incomplete demo start sequence.
Keep the working context instead of restarting
Use Open original to compare the same version in its own tab. If that context gives you a usable display, continue there. The embedded session and original tab are separate attempts; decide which one you will control.
Return with the player selector below when you need the launch checklist. Protect current progress before pressing Restart or clearing stored game data. The save-progress guide explains that separate decision.
Questions about this session
Does Focus view restart the game?
No. It changes the surrounding layout while retaining the same embedded player.
Does fullscreen capture the mouse?
Not by itself. Follow the original project’s mouse-capture prompt inside the scene.
What if fullscreen is unavailable?
Try Focus view or the original project in its own tab. The App cannot force browser fullscreen support.
A NEXT STEP FOR EACH SYMPTOM