Start Wyldheart demo troubleshooting by confirming the exact client and symptom. The public Demo is AppID 4475270, reached through the Steam page for base game AppID 3642910. The separate Beta AppID 3643050 was not updated into the public demo. Once identity is correct, isolate launch, performance, interaction, save, input, and co-op problems instead of applying every fix at once.
Confirm version and product identity
Open the official Wyldheart Steam listing and verify Wayfinder Studios is the developer. Choose the public Demo download. Do not use WILD HEARTS AppID 1938010, and do not launch the older Kickstarter Beta when following Demo guidance.
Update the demo and record the version shown. This guide covers 0.7.2 on October 10, 2026. Official hotfix posts use labels including CL39302 and CL39317; treat those as public client revision labels, not as a base-game semantic version or an independently verified Steam BuildID.
Fix apparent progress blocks
For loot, dialogue, or environmental actions, center the crosshair and use the configured interaction control. Add light in dark rooms. Breakable mushrooms can reveal paths, while some hidden items or doors depend on skill levels. A locked interaction can therefore be progression state rather than a technical failure.
Near the opening exit, a current player report identifies an easily missed “…” dialogue choice after speaking with the injured character. Exhaust the exchange before diagnosing the rope or exit as broken. This is community-observed help for the current demo, not a universal engine fix.
If an active ability is missing, check whether it was equipped. Under the default keyboard setup documented by the team, hold T for the skill wheel. For controller trouble, remember that support is incomplete and mouse and keyboard is recommended.
Protect saves and reconnect co-op
The demo does not save offline. Play online when progress matters and confirm the Online Save checkbox state; the 0.7.2 hotfix notes say it now works. Run a short controlled test before investing in a long session. Demo saves are not planned to transfer to Early Access or the full game, but they should still persist within supported online Demo play.
For co-op, ensure every player runs the same current Demo client, then have the host generate a new join code. Share it privately. Confirm the party before earning experience, because shared experience currently applies only to members who are online. Do not expect progress to be held for an absent player.
Sources checked for troubleshooting
The 60 FPS cap, interaction aiming, offline-save limitation, incomplete controller support, mouse-and-keyboard recommendation, Deck caution, skill wheel, and progression-gated discoveries come from the official Demo FAQs. Online Save and join-code fixes come from the team’s Demo 0.7.2 hotfix notes. The Beta-versus-Demo distinction is confirmed in the official launch discussion. The ellipsis dialogue tip is explicitly sourced to a current player help thread.
Escalate with a clean report
Record the Demo version and revision label, Windows version, CPU, GPU, memory, storage, display resolution, frame cap, input method, online state, party size, and exact reproduction steps. State what changed after the 60 FPS cap or an input swap. For a save issue, say whether offline mode was used. For co-op, say whether a fresh code and matching versions were tested.
Avoid reinstalling or deleting data as the first response. A precise symptom and controlled comparison preserve evidence. If the same fault survives identity checks, an update, a clean relaunch, and the relevant official workaround, send that report through Wayfinder Studios’ current support channel.