Wyldheart Demo 0.7.2 has controller support, but the developers describe it as incomplete and recommend mouse and keyboard. A controller can be tested, yet players should expect missing polish or actions that are easier to diagnose with keyboard and mouse. Verify essential controls before entering a dungeon or hosting co-op.
Test the full action set in safety
Do more than move and attack. Open the controls menu and check camera movement, interaction, inventory, character information, map or compass access, the skill interface, active-skill selection, and any action needed to use light. The opening dungeon combines darkness and targeted interaction, so a missing menu or crosshair action can look like blocked progress.
Center the crosshair on an object before pressing interact. The official tips call out aiming as part of looting and interaction. If the object still does not respond, compare the controller binding with the keyboard command and test whether the same target works with mouse and keyboard.
Diagnose the layer that failed
First confirm the game sees the device. Then inspect in-game bindings. If Steam Input is involved, note the selected layout and whether the displayed prompts match the physical device. Change one layer at a time; changing the game binding, Steam layout, and hardware connection together hides the actual cause.
If only one object fails, consider the game state. Some hidden items or locked doors depend on skill levels. A non-responsive door is not automatically a controller bug. Try another known interactable target, center the crosshair, and compare input methods.
If performance feels like input delay, use the developers’ current 60 FPS cap recommendation and retest. Record performance and control symptoms separately. A frame-time problem can make a working input feel inconsistent.
Use mouse and keyboard as the reference path
The developers explicitly recommend mouse and keyboard for the current demo. Under the default documented layout, hold T to open the skill wheel. Use that reference when a controller action or prompt is unclear, especially for inventory management, skill setup, or precise interaction.
This recommendation is limited to the current demo. It does not prove that the final game will lack complete controller support. Conversely, a store feature label or one successful device does not prove every controller and menu path is fully supported today.
Steam Deck has its own caution: the team says the demo is playable there but does not recommend it while optimization remains pending. Built-in controls therefore should not be presented as a fully verified Deck experience.
Sources checked for controller support
The incomplete controller status, mouse-and-keyboard recommendation, hold-T skill wheel, crosshair interaction tip, 60 FPS cap, and Steam Deck caution come from the official Wyldheart Demo FAQs. Product and platform identity are checked against the official Steam listing. The team’s Demo 0.7.2 hotfix notes provide the current revision context but do not announce complete controller coverage.
Make a reproducible controller report
Include the controller model, connection type, operating system, Steam Input state and layout, demo version, exact screen or object, displayed prompt, expected action, and observed result. State whether mouse and keyboard succeeds at the same point. Add whether the problem survives a reconnect and clean relaunch.
A precise report helps separate device detection, mapping, game state, interface completeness, and performance. Retest the same action after changing only one setting, then record whether prompts and behavior changed together. Until controller work is described as complete by the developers, keep mouse and keyboard available for important Demo sessions.