Forever Ago lists full controller support on Steam, with controller metadata for Xbox-style input and PlayStation DualShock/DualSense hardware. Steam’s current hardware categories flag the PlayStation entries for USB use, so a wired connection is the documented starting point for those devices. Exact glyph switching, wireless behavior, and per-action bindings still need confirmation in the current PC build.
Begin with one controller and one input layer
Connect the intended controller before launching Forever Ago. In Steam → Settings → Controller, confirm that Steam sees the correct device. Then open the game’s Properties → Controller and leave the per-game setting at its default for the first test.
Disconnect extra gamepads, wheels, virtual controllers, and remapping tools. Multiple devices can change player order or cause one physical input to appear twice. A clean test with one pad tells you whether the game, Steam Input, or device connection is the failing layer.
For DualShock or DualSense, use a data-capable USB cable rather than a charge-only cable. The current Steam metadata is the reason for this conservative recommendation; it does not prove that every wireless route fails. Test Bluetooth only after the wired baseline works.
Check the actions that matter in Forever Ago
This is a slow exploration and photography game, so controller validation must cover more than walking. Test normal movement and camera rotation, then a nearby object interaction. Raise the instant camera, frame a subject, use focus or zoom if the current tutorial exposes it, take a photo, and leave camera view.
Open the journal and navigate its pages or photo selection. Enter the pause and settings menus, back out, and resume. During a prompted scene, confirm that glyphs remain consistent rather than changing to keyboard labels after one stick or trigger input.
Do not publish a button map copied from a console screenshot. Steam Input profiles can differ, PlayStation and Xbox labels use different names, and a patch can adjust bindings. The live on-screen prompt under the current layout is authoritative.
Decide when to use Steam Input
Steam Input can translate controller types, provide a community or official layout, and help a generic pad appear through a common interface. It can also conflict with DS4Windows, reWASD, virtual HID tools, or a game’s own device handling if two layers are active.
Start with Steam’s default. If the controller is detected by Windows and Steam but not the game, test the per-game Steam Input setting once after fully closing Forever Ago. If the game works natively but glyphs are wrong, compare a Steam Input-enabled and disabled launch using the same wired device.
Change one layer at a time and restart the game between tests. Hot switching in the middle of a camera prompt or journal screen can make the UI state look like a persistent mapping problem.
No input at all
Confirm Steam sees the device, close other mappers, unplug extra controllers, restart the game, and test the default per-game setting.
Double inputs
Remove one translation layer. A physical pad plus a virtual copy often produces two menu movements or repeated interactions.
Wrong glyphs
Reconnect before launch, stop touching mouse or keyboard during the test, and note whether Steam Input is translating the device type.
PlayStation pad not detected
Use USB first, try a known data cable and direct PC port, update firmware through official tools, and retest with Steam alone.
Diagnose connection and prompt problems
If Windows does not detect the controller, the problem is below the game. Test a direct USB port, data cable, battery state, and official firmware updater. Avoid an unpowered hub for the baseline. Steam cannot pass a device to Forever Ago if the operating system never exposes it.
If Steam detects it but the game does not, close the game, set the pad as the only controller, and restart with the default layout. Then test the per-game Steam Input override. Record which state works instead of leaving several remappers active.
If prompts flicker between keyboard and controller, move the mouse away and check for stick drift, virtual mouse mappings, or a wireless device sending input. If one action fails while menus work, inspect the active layout before assuming a game-wide controller bug.
Avoid transferring console claims to Steam PC
Forever Ago is sold on consoles as well as PC, but a console build’s prompts, platform features, and connection rules do not automatically describe the Windows executable. This page uses Steam AppID 1215940 metadata and Valve’s controller categories.
Similarly, Deck Verified supports the built-in Steam Deck controller path; it does not prove every third-party Bluetooth pad on Windows. Full controller support is a broad capability label, not a list of every vendor model, firmware, adapter, or wireless mode.
When asking for help, include controller model, wired or wireless transport, Windows version, Steam Input state, other mapping software, which actions work, displayed glyph type, and game build. “Controller broken” omits the information needed to reproduce the fault.
Protect progress while testing input
Do not disconnect devices during a save, journal commit, or scene transition. Reach a stable pause or main menu first. Controller troubleshooting should never require deleting saves or disabling Steam Cloud.
For a photo or interaction that appears blocked, test the same prompt once with keyboard and mouse. If the objective advances there, preserve the save and report the controller-specific binding state. If neither input works, use the puzzle or known-issues guide because the cause may be scene progression rather than the pad.
Sources and verification boundary
- Forever Ago on Steam — official AppID, current controller and Deck presentation, and product scope.
- SteamDB configuration for AppID 1215940 — third-party rendering of full-controller, DualShock, DualSense, and Deck compatibility metadata.
- Steam Support — official client and controller troubleshooting entry point.
Controller metadata was checked on October 10, 2026. Exact PC bindings, wireless behavior, prompt switching, and device-specific faults remain current-build tests rather than assumed console parity.