Check whether you installed the full game or demo
The full release and the demo have separate Steam listings and separate support descriptions. The full-game website explicitly presents controller play as an option alongside keyboard and mouse. The demo's partial-support label should be read as information about that product, not as a correction to the full game's advertised feature.
Before troubleshooting, open the listing for the product you actually launch. This is especially important if both versions appear in your library or you are comparing an early demonstration with a recent recording. A difference between the two listings is not resolved by assuming that every control limitation transfers unchanged between versions.
Use Steam Big Picture for the naming procedure
The developer FAQ gives a specific answer for entering a custom hero name with a gamepad. Launch the game through Steam Big Picture, reach the hero-name menu and press Y to open the virtual keyboard. These are the supported steps in the collected explanation, rather than a general claim that any button will summon text input.
Follow the steps in that order when the naming field is the problem. Starting in the documented Steam mode matters because the answer explicitly includes Big Picture. If another guide only says to press a button without naming the menu or launch mode, it leaves out part of the developer's instruction.
Read historical demo feedback in context
The research includes early demo discussions about item visibility and controls. Those posts describe the experience of particular demo builds, and later demo updates changed controls and other features. They are valuable historical reports, but they are not a current full-game button reference.
If you encounter a similar symptom, compare the versions before trying an old workaround. A report from an earlier demo can explain why a player was frustrated without proving that your current installation has the same limitation. Start from the advertised support of the correct product and the developer's later instructions.
Separate text entry from exploration controls
A hero-name field is a text-entry interface, while moving through Underkeep uses the game's grid-based navigation. The existence of a naming workaround should not be treated as evidence that ordinary movement requires the same sequence. The developer's answer solves a specific menu interaction rather than redefining the entire controller scheme.
When troubleshooting, identify the exact screen on which input stops doing what you expect. Describe a problem in character naming separately from a problem during exploration or combat. That makes the issue clearer than saying that the controller does not work when only one menu action is affected.
Controller support is different from platform availability
The released game is a Windows PC title available through Steam and GOG. The developer website describes console ports as a plan for 2027. Full controller support in the PC version therefore should not be read as a statement that a console edition has already launched.
Use the release-date guide if your question concerns which device can run an available edition. Use this page for the documented controller support and naming procedure inside the PC game. Keeping those questions separate avoids turning an input feature into a platform announcement.
Build a useful troubleshooting report
For a controller problem, record whether you are playing the demo or full game and include the build you are using. State whether you launched through Steam Big Picture and identify the affected menu or action. If the naming procedure is involved, describe what happens after pressing Y in the hero-name menu.
That report is more useful than a general statement that an old video worked differently. The official Steam discussions provide a place to compare the same version with other players and developer replies. Keep observed behavior separate from assumptions about controller certification, vibration or another device you have not tested.
Compare like-for-like control reports
When another player describes a fix, identify whether the same product, menu and launch method appear in both situations. A report about hero-name text entry through Steam Big Picture addresses a narrower problem than a report about moving through the dungeon with a gamepad. Matching those details makes a comparison useful even before anyone has identified the cause of the difference.
Keep a short account of what the interface shows and what you pressed. For the naming procedure, include whether Y opens the virtual keyboard in the specified menu; for another action, describe that action independently rather than assuming it shares the naming issue. This avoids reducing every input question to the broad claim that full support either works perfectly everywhere or does not exist at all.
The published support label and your observation answer different parts of the discussion. The label describes the product's advertised feature, while a detailed report describes what occurred in a particular setup. Keeping both statements precise gives the official community a stronger starting point than borrowing a control conclusion from a different edition or device.
The short setup checklist
Start by matching the Steam product to the support label: full game or demo. For a custom name, use Big Picture and the developer's Y-button procedure in the hero-name menu. If another control behaves unexpectedly, record the exact screen and version before searching for a fix.
This approach keeps the confirmed support information and the documented workaround together. It also lets you use older demo feedback appropriately without treating it as the final word on the release game. Once text entry is working, return to the beginner guide for party planning and the exploration systems that the controller is used to navigate.
Sources and further reading
- Official full-game Steam listing
- Separate demo Steam listing
- Developer FAQ: controller hero naming
- Official controller feature description
Information checked November 5, 2026. Report a correction.