THE HENRY STICKMIN COLLECTION · DISPLAY HELP
How do I play in fullscreen?
In The Henry Stickmin Collection, open the glasses icon at the bottom-right of the main menu and select fullscreen. Developer Forte's edited Steam answer says the option is off by default and warns that some scenes may still crash in fullscreen. If it becomes unstable, return to windowed mode.
The question is Rhinestone's actual Steam thread title. The menu instruction comes from the developer's marked answer, checked September 30, 2026. We have not tested the commercial game on this computer. This independent guide is not published by its developer.
Start with the right version
This instruction is for the desktop Collection. A browser episode such as Escaping the Prison runs inside its host website; do not expect it to have the Collection's menu. Check the title and launch location before changing anything. Our edition guide separates the browser episodes from the Collection.
The developer's edited reply supersedes its older beta-only advice. We are not recommending a beta branch, a replacement executable, or an unofficial download to obtain fullscreen. A larger picture is not evidence that crashes have been fixed.
ORIGINAL SMALL ESCAPES WORKSHEET
Compare the same scene
Use this after you have observed the game, not before. Record one scene in windowed mode and the same scene in fullscreen. Leave an untested result untested. The worksheet builds a report from your selections; it does not inspect your computer, run the Collection, or diagnose a graphics driver.
Your entries stay in this page's memory. They are not sent by this tool or saved after a reload. Nothing is submitted to support automatically. Do not include passwords or personal account details.
A comparison you can actually explain
- Choose a stopping point. Use a familiar menu or scene you can reach again. Write its name before testing so you do not compare a quiet menu in one mode with a different animation in the other.
- Make a baseline note. In windowed mode, record whether you reached that stopping point. A successful launch alone is not a completed scene. If you do not want to repeat a crash, leave the other condition untested.
- Change only the display mode for this comparison. Keep your chosen scene and route the same. If you also changed another setting, note that in the report instead of attributing the difference solely to fullscreen.
- Record what happened, not the suspected cause. “The window stopped responding before the menu appeared” is more useful than “my computer is too slow.” You can add an exact error message, but do not invent one if there was no message.
- Choose a usable fallback. If your windowed observation succeeded and fullscreen failed, use the working windowed setup for now. That is a practical choice from your observation, not proof of the underlying cause or a permanent fix.
Your observationFULLSCREEN
Your observation
Original diagram: the boxes describe a test plan, not screenshots of the game.
Read the result without overclaiming
Windowed works; fullscreen fails
The worksheet recommends the observed working mode. Your report preserves both outcomes and the scene name. It deliberately does not identify a driver, memory problem, or broken installation from this pair of observations.
Both modes work
You have evidence for that scene in those conditions. Keep the report scoped to the stopping point you chose. Do not turn one successful comparison into a statement that every route or later scene is stable.
Both modes fail
The comparison cannot isolate fullscreen as the cause. Record the common failure point and any actual message. Repeating the same crash to fill in more rows is not required by this worksheet.
A result is missing
The report stays incomplete. It never treats a blank or untested field as success. You can still copy a partial report that clearly says which mode was not tested.
These are examples of how our tool interprets user-entered observations, not reports from people who played the game.
Use game-specific evidence first
The developer's warning concerns fullscreen stability, so fullscreen should not be presented as a cure for freezing. Generic keyboard shortcuts and instructions for other games are not confirmation of how this Collection behaves. If the menu differs from the cited answer, record your edition and what you actually see before asking for help in the game's Steam discussions.
Black space around an image, a game running inside a browser, and a game process freezing are different observations. Describe the visible symptom in your report. This guide does not promise to remove borders, change the game's internal resolution, or recover progress after a crash.
Sources and scope
Primary source: Rhinestone's question and Forte's developer reply. Our contribution is the local comparison worksheet, its interpretation rules, the observation protocol and the original diagram. These are tested page features, not a hands-on review of the commercial game. Browser availability and fullscreen stability are separate topics.