Wyldheart
Home › Demo fixes

Wyldheart Demo Not Working: What to Check

On first launch, a long loading screen with a countdown can be shader compilation: the official workaround is to wait. If a campaign keeps loading instead, check service status and updates. Offline progress is lost on exit.

Reviewed · Demo 0.7.2; official notes through October 9, 2026

Choose the branch that matches your problem

Troubleshooting by symptom
What happensFirst checkNext action
First launch; loading with a number countdownOfficial issue WYL-999: shaders compilingAllow compilation to finish; no fixed waiting time is published.
Game never reaches the menuSteam installation and PC requirementsUse the client checks below.
Menu opens; campaign will not loadOfficial online-service statusUpdate, then retry when services are available.
You need to try solo during connection troubleWhether you accept losing that session’s progressRead the offline warning before changing save settings.
Host loads; friend cannot joinHost Lobby/Roster join codeFollow the multiplayer guide.

First launch: a countdown can mean shader compilation

The official known-issues page lists WYL-999: first startup can show a very long loading screen with a numerical countdown and no explanation while shaders compile. The team’s workaround is to wait; clearer explanatory text is planned.

This is a different symptom from a campaign connection loop after the menu. There is no verified maximum compilation time, so this guide does not tell you that it must finish within a specific number of minutes.

What the official hotfixes actually changed

The October 9 CL39302 hotfix addresses host join-code visibility and the frontend Online Save checkbox. The same announcement warns that solo play can be affected by online-save connectivity.

CL39317 targets login and reconnect reliability and reduces server traffic. Its wording describes expected improvements, not a promise that every loading issue is fixed. The October 9 maintenance notice is historical; check the status page for conditions now.

If the game fails before the menu

These are general Steam and PC checks, not confirmed Wyldheart-specific cures. Change one thing at a time so you can tell what helped.

  1. Finish the update. Check Steam Downloads for pending updates to Wyldheart Demo and let them complete.
  2. Verify the installed files. In Steam, open the demo’s Properties, choose Installed Files, then Verify integrity of game files. This checks the local installation; it cannot repair the game’s servers.
  3. Compare your PC with the store listing. Review the current Windows, RAM, GPU, DirectX and SSD requirements. The store lists Windows 10/11 64-bit, 16 GB RAM and DirectX 12 at minimum.
  4. Record the failure. Note whether the application closes, displays an error, or stops at a specific screen. Keep the build and relevant hardware details for a support report.

Before trying offline mode

The 0.7.2 notes refer to the frontend Online Save checkbox as the offline workaround. Their description of the checkbox is counterintuitive: they say to tick it for offline play. Use the current menu’s actual indication of mode rather than assuming the label guarantees saving.

Offline saves are unsupported in this demo, and progress with saving disabled is lost on exit. If preserving a campaign matters, wait for online services instead of treating offline play as a safe replacement.

If the problem continues

Report the exact symptom, build, whether you were hosting or joining, and whether online saving was enabled. The official team points players to its Steam forums, Discord and Reddit.

Do not delete saves, disable security tools, or install unofficial fix downloads to follow this guide. If the status page is healthy but the same campaign cannot load, that is useful context to include in your report.

Sources and version notes