If the Emberville demo is stuck on a loading screen, first check your demo version and identify whether it is a long load, a black screen, or a failed world creation. Long loading on some setups remains a known issue in Demo Alpha 0.20.18.x. There is no verified universal wait time or guaranteed fix for every affected machine.
An older patch fixed black-screen loading on some Windows configurations, while the later patch fixed rare world-creation failures. Those changes are relevant checks, but they do not prove that all loading symptoms share one cause. Preserve your save and use the reversible checks below before considering changes to local files.
Identify the stage that stops progressing
Write down what you selected immediately before the apparent stall. Starting the application, creating a new world, and loading an existing character are different entry points. A report that says only loading is broken loses the detail needed to compare your case with the known issue.
Watch for visible changes rather than assuming that a static screen establishes a permanent freeze. Note whether a loading indicator moves, whether music continues, and whether the application responds to normal window controls. These observations help describe the symptom; none of them alone guarantees that the game will eventually finish loading.
If the screen is completely black, say so explicitly. If an illustrated loading screen remains visible, describe that instead. If a world never appears after character creation, include that sequence. The latest documented fixes distinguish black-screen behavior from world creation, so the distinction can affect your next useful step.
Keep the duration as an observation rather than turning it into a rule for everyone. If you waited a certain length of time, record it. Do not assume another player's shorter load means your save is corrupt, or that waiting indefinitely is required because the issue is acknowledged.
Check the public demo version
The latest verified public demo update as of October 28, 2026 is Demo Alpha 0.20.18.x. Check the version shown by your installed build if available, and allow the distribution client to finish any pending demo update before repeating your test. Make sure you are launching the public demo rather than relying on instructions written for an earlier creator preview.
Alpha Demo 0.20.17.x fixed an issue that made the game load to a black screen on some Windows configurations. Demo Alpha 0.20.18.x fixed an issue preventing worlds from being created in some rare cases. The same later patch still lists long loading on some setups as an open issue.
That means updating is a reasonable first action, but a newer version is not proof that your particular symptom is resolved. If you are already on the current verified demo line and still encounter a long load, you may be experiencing a case that remains under investigation.
| Situation | Relevant version information | Practical next check |
|---|---|---|
| Black screen while loading on Windows | Some configurations were addressed in 0.20.17.x | Confirm the installed demo includes that update |
| Failure during world creation | Rare creation failures were addressed in 0.20.18.x | Record whether the problem occurs while creating a world |
| Long loading on a particular setup | Still listed in 0.20.18.x known issues | Use a controlled retest and document the result |
| Existing character fails while another entry point works | No universal cause established | Preserve the character and describe the exact difference |
Use a controlled restart
A restart is a diagnostic check, not a confirmed repair for the known loading issue. If the application clearly stops responding or the wait is no longer productive, close it through normal controls if possible. Avoid repeatedly launching additional copies while an earlier process may still be running.
- Record the loading stage and how long the current attempt has lasted.
- Close the demo and confirm that the session has ended.
- Allow any pending client update or file operation to finish.
- Relaunch the same public demo build once.
- Repeat the same entry action so that the result can be compared with the first attempt.
- Note whether the symptom occurs at the same point or whether the game reaches the menu or world.
Do not combine this test with several unrelated changes. If you update the demo, replace an input layout, remove configuration, and start a new character together, a successful launch will not tell you which action mattered. A single controlled restart gives you a clearer result and avoids unnecessary interference with your existing setup.
If a repeat attempt reaches the game, check your character and recent progress before treating the issue as solved. A successful second launch establishes that this attempt loaded; it does not establish that a known intermittent problem has permanently disappeared.
Verify installed files without treating it as a guaranteed fix
Using your game client's file verification or repair facility is a general installation check. It can help identify missing or damaged installed content, but it is not a confirmed fix for the acknowledged long-loading issue. Keep that distinction clear when deciding how much time to spend on it.
Close the demo before running a repair operation, then let the client complete it fully. If the client replaces installed files, record that result. If it reports no change, that is also useful: you have checked the installation without proving that the remaining problem is caused by your computer or your save.
Retest the same loading path after verification. Do not immediately delete local progress because repaired installation files did not change the outcome. Installation content and saved character data serve different purposes, and a failure in one area cannot be inferred solely from a general loading symptom.
A complete reinstall is more disruptive than a file check and still does not guarantee a fix for a known build issue. Preserve local data before considering that escalation, and avoid reinstalling repeatedly without a new reason to expect a different result.
A playable world with a responsive HUD is distinct from a loading screen; this preview is not a demonstration of a fix.
Protect the save while testing entry points
Do not delete the Saves folder as a generic loading fix. The current known-issue guidance does not provide a blanket instruction to erase progress, and the public demo's intended future save carryover makes unnecessary deletion particularly unhelpful.
If you compare loading an existing character with another entry point, retain the original character. A new world loading successfully would help identify the scope of the symptom, but it would not automatically prove that the earlier save is irrecoverable. Describe the difference before taking further action.
Likewise, a failed attempt to create a world does not establish that an existing character is damaged. The later demo patch specifically mentions rare world-creation failures, making the exact stage valuable evidence. Keep the result tied to what you actually observed instead of labeling every failed start as corruption.
A precautionary backup is sensible before any local-data operation, but there is no need to invent a manual save migration procedure to perform basic loading checks. If you do not know which files contain progress, stop before moving or deleting them and seek instructions for the specific build.
Keep the language workaround separate
The same demo patch lists an options-file workaround for language selection failing. That advice concerns options.eopt, a configuration file, and it is not published as a universal loading-screen repair. Do not apply it simply because both symptoms appear in the same patch notes.
If language selection is also failing, record it as an additional symptom and use the language-specific instructions deliberately. If loading is your only problem, changing unrelated configuration can obscure the result of your test. A targeted check is more informative than removing files in the hope that some setting is responsible.
This distinction also applies to controller fixes. A gamepad navigation problem can stop you choosing an option on a menu, but that differs from a world that has started loading and never appears. Check whether you can actually select the intended menu action before diagnosing the resulting transition as a loading stall.
Reaching character creation and loading an existing character are different checkpoints.
Prepare a useful report if the long load remains
After an update check and a controlled retest, a persistent long load needs a clear description more than another identical restart. Report the version, platform, entry action, screen state, and observed duration. Include whether this is a new world or an existing character, and whether any other entry point works.
A concise report might state that Demo Alpha 0.20.18.x reaches the main menu, begins loading an existing character, and remains on the same screen for the measured duration. Another might say that the application shows a black screen before the main menu appears. Those reports identify different stages without assuming a cause.
If you changed one thing during testing, include it and the result. For example, note that the client completed file verification and that the next attempt stopped at the same stage. Do not claim that a check fixed or disproved a cause unless its result actually supports that conclusion.
Stop repeated testing when the same behavior returns and you have no new variable to check. Preserve the character, retain the useful observations, and wait for build-specific guidance or an update. There is no verified maximum load duration, universal launch flag, or guaranteed local-file deletion that closes every current case.
Recheck after the next build change
These checks apply to the public demo as documented on October 28, 2026. Early Access is planned for January 7, 2027 and has not yet launched. Its future loading behavior cannot be established from a demo workaround or an old preview recording.
When the demo receives another update, compare the installed version with the notes before reusing an older diagnosis. The useful success condition is concrete: the intended character or world loads, ordinary input works, and your progress remains available. Until that happens, a partial change such as reaching a different screen is progress in diagnosis, not proof that the whole problem is resolved.