Steam currently lists Full controller support for both Rain98 base AppID 3498720 and the playable Rain98 Demo AppID 3738760. The Demo listing also exposes DualSense support categories. That confirms controller-oriented play at the store-metadata level; it does not document every controller model, connection method, button glyph, rumble feature, or minigame prompt.
For the cleanest setup, connect one controller before launching Steam, close duplicate input mappers, start the Rain98 Demo from its library entry, and test menus plus one ordinary scene before changing Steam Input.
Know what Steam’s label guarantees
Confirmed by Steam
Base game: full controller support is listed for AppID 3498720.
Demo: full controller support is listed for AppID 3738760.
Platform: both listings currently target Windows.
Shown for the Demo
Device category: DualSense support appears in the Demo's Steam categories.
Also available: keyboard and pointer interaction remain useful for diagnosis.
Scope: store metadata, not a complete hardware matrix.
Not established by the label
Wireless parity, cable requirements, adaptive triggers, haptics, rumble, native glyph sets, hot-plug behavior, remapping, and activity-by-activity support all require current-device testing.
“Full controller support” is not a promise that no keyboard or operating-system prompt will ever appear. It is also not evidence that the Demo and unreleased retail build have identical input code.
Establish one working baseline
Connect the controller and verify Windows sees it before opening the game. In Steam, select Rain98 Demo, open its controller settings, and note the current Steam Input state without changing it. Launch the Demo and test directional movement, confirm, cancel, pause, and dialogue advance where the game exposes them.
Do not publish or memorize a button map from this page: the correct glyph depends on the active device and current build. Follow the on-screen prompt. A story scene, point-and-click apartment interaction, city segment, bead task, capsule job, and rhythm activity can each ask for different kinds of input.
Once ordinary navigation works, save that configuration as the baseline. Only then test another device, wireless connection, or custom layout.
Fix duplicate or changing prompts
Prompt flicker usually means the game is receiving more than one input source. Disconnect unused controllers, close remappers that create a virtual pad, and avoid moving the mouse while testing. Relaunch from Steam with one physical device.
If prompts still alternate, inspect Steam’s per-game controller page. Test the existing state first, then change Steam Input once and relaunch. Do not layer a vendor mapper, a virtual controller, and Steam Input unless you know which one is supposed to own translation.
For a DualSense, compare one supported wired connection before diagnosing wireless behavior. Steam’s Demo categories expose DualSense support, but the public metadata returned on October 18 does not provide a dependable feature-by-feature wired/wireless matrix.
Diagnose by symptom
After each change, repeat the smallest scene that showed the problem. A successful main menu test does not prove the capsule or Dance Dance Dream sequence is fixed; a failed rhythm result does not prove the controller is disconnected.
Handle object and pointer interactions
Rain98 includes tactile activities that can use selection, dragging, placement, or grid movement. With a controller, wait for a visible focus or highlight before confirming. With a pointer, release near the target center. If an object returns to its source, check whether it was assembled, filled, or otherwise prepared before submission.
If the full frame is not visible, correct resolution or display scaling before blaming aim. A pointer offset can make a valid controller action look like a missed task state.
Keep one normal save before repeating a troublesome activity. Do not use macros to automate a result: they can mask an input problem and create timing that the story state did not expect.
Report a controller issue usefully
Record the exact product—Rain98 Demo AppID 3738760 for the current playable build—plus date, Windows version, controller model, wired or wireless connection, Steam Input state, other remappers, scene, expected prompt, and observed result. Include whether keyboard or mouse worked at the same point.
Avoid saying only “controller unsupported.” Steam’s metadata says support exists; the useful question is which device, layer, and scene failed. Send the minimal reproduction through the official Demo feedback channel and preserve the save.
The base game has not launched, so repeat this check on AppID 3498720 when it becomes playable. Current Demo success is encouraging but does not freeze retail behavior.