Wyldheart Wiki - Tech: PC Requirements, Steam Deck and Demo Fixes

ProductBase game listing AppID 3642910 and public Demo AppID 4475270 kept distinct VersionDemo 0.7.2 and current Steam requirements checked 2026-10-10 PlatformWindows 10/11 64-bit through Steam; Deck is a compatibility observation, not native Linux support

Wyldheart’s current Steam requirements target 64-bit Windows 10 or 11, DirectX 12, 16 GB RAM, broadband internet, 10 GB of available storage, and an SSD. The minimum profile names 1080p at Medium settings and 30 FPS; the recommended profile names 1080p at High settings and 60 FPS. The developer marks the requirements as work in progress, so use them for the current demo and pre-release planning rather than treating them as the final optimized base-game specification.

Most launch-week demo problems fall into three different groups: the PC does not meet or cleanly run the client, the input or compatibility layer is incomplete, or Wyldheart’s online services are under load. Diagnose the group first. Changing graphics settings cannot repair a server outage, and playing offline cannot preserve a demo run because offline saving is unsupported.

Current support matrix

AreaCurrent answerPlayer decision

Windows PCOfficial Steam platform; 64-bit Windows 10/11 and DX12Compare exact CPU, GPU, RAM, SSD, and target profile before installing.

Steam DeckOfficial FAQ says the demo can run, but recommends PC and mouse/keyboard while optimization continuesDo not call it Deck Verified or native Linux; record model, OS, build, and settings.

ControllerSteam lists controller support; developer guidance says the demo implementation still needs improvementCheck live prompts, Steam Input, device duplication, and current bindings.

Online servicesDemo saving and login normally use online services; 0.7.2 improved reconnects and capacity groundworkCheck status and hotfixes before destructive local troubleshooting.

Offline optionAvailable after CL39302, but offline demo sessions do not saveUse only for disposable practice when persistence does not matter.

Compare hardware against the correct target

The System Requirements guide lists the full official profiles and explains how to find your hardware. Model names matter: “i7” or “RTX” alone does not identify performance. Laptop parts can also run at different power limits from similarly named desktop parts.

Minimum is a 1080p/Medium/30 FPS goal on the current listing, not a guarantee for higher resolution, high refresh, or every scene. Recommended is a 1080p/High/60 FPS goal. Both require an SSD and 16 GB RAM. Close heavy background work when memory is tight, install on the SSD rather than merely owning one, and leave update headroom beyond the listed 10 GB.

The requirements are explicitly unfinished. If an upgrade decision depends on a stable 60 FPS, a particular controller, or Steam Deck performance, wait for a test from the same demo version and comparable hardware.

Check service state before touching local files

When the campaign hangs during login or loading, open the official status page and Steam news. The demo’s first two hotfixes addressed join-code visibility, the offline checkbox, login and reconnect reliability, server load, and preparation for more capacity. Those changes confirm that some failures are service-side.

If an outage is active, preserve the installation and wait. If status is normal, restart Steam and the demo, allow updates, verify installed files, and test again. Record the UTC time, region, version, exact error, and whether a fresh solo campaign behaves differently. Do not delete save or configuration folders based on an unverified path.

Offline mode is a limited diagnostic route. It can show whether the client reaches solo play without online saving, but the official warning says progress disappears on exit. Do not use it as a fix for a campaign you expect to keep.

Make input problems reproducible

Connect one controller, launch the demo, and inspect displayed prompts. If prompts switch unexpectedly, disconnect duplicate gamepads, virtual devices, or unused input tools, then review the per-game Steam Input setting. Change one layer at a time so you know whether the game, Steam Input, the connection type, or the device caused the difference.

Test movement, camera, interaction, defense, weapon access, quick items, and the skill interface near the beginning. A controller can be supported while a particular prompt or action remains rough in the demo. Report the exact device, wired or wireless connection, Steam Input state, Windows version, demo version, and failing action.

Mouse-and-keyboard is the developer’s current recommendation for the demo, not proof that every player must use it. Choose the device that produces readable, consistent inputs on your system.

Scope Steam Deck claims carefully

The official FAQ says the demo can run on Steam Deck but still recommends PC with mouse and keyboard. That is not a Valve Verified badge, native Linux release, or performance guarantee. Steam currently lists Windows as the native platform.

For a useful Deck report, state LCD or OLED model, SteamOS version, compatibility layer version, demo label, resolution, preset, frame limit, power limit, input layout, online state, and the tested area. Distinguish “launches” from “maintains a chosen performance target.” Do not convert one community success into a compatibility rating for every build.

Troubleshoot graphics and performance in a stable scene

Start from the preset appropriate to your hardware. Use a repeatable room or encounter and watch frame pacing, not only an average counter. Lower one expensive setting group at a time if the current menu exposes it. Keep the resolution, frame cap, and upscaling state recorded so comparisons remain meaningful.

If performance worsens only during server or login trouble, do not assume the GPU caused it. If it worsens in the same offline-rendered scene, capture CPU, GPU, memory, temperature, driver, and frame-time behavior. Remove unsupported overlays or injectors only when you knowingly installed them, and restore them one at a time.

Report a problem without exposing private data

Include Demo AppID 4475270, version 0.7.2, Windows build, hardware, driver, input device, online-save state, region, UTC time, exact action, error text, and steps already tested. For a join problem, add party size and whether solo login works. For a rendering issue, add resolution, preset, and a repeatable location.

Remove account names, join codes, local usernames, and private messages from screenshots and logs. Use the official feedback channel named by the developer. Recheck the report after the next patch because server, controller, and compatibility behavior can change quickly.

Reverify at Early Access

The base game is not released. At Early Access, recheck operating systems, CPU/GPU pairs, storage, presets, network requirement, controller status, Steam Deck badge, compatibility layer behavior, server architecture, save locations, crossplay, and language support. Do not carry a demo workaround into the base game without reproducing the problem there.