Steam Deck and controller questions for Onimusha: Way of the Sword need more detail than “does it run?” The base game is AppID 2638890 and the Demo is AppID 3974650. A storefront compatibility signal, a ProtonDB report or a player comment can guide testing, but none proves a universal Steam Deck preset, native Linux support, readable text, stable frame pacing or correct controller glyphs. Record the environment before publishing a result.
Start with the default configuration
Install the exact product, launch without mods and note the SteamOS, Proton or Windows version. Confirm the game recognises the controller, displays readable prompts and reaches the same scene twice. Record the frame limit, power profile, display mode and whether suspend/resume was used. A first launch that reaches a menu is not enough to prove a combat session is stable.
Test the Demo and base game separately. If a trial works on Deck, keep that result tied to AppID 3974650. The official Steam Community says the Demo differs from the full game, so a later release may use different files, settings or performance characteristics.
Report readability and input separately
A player can have acceptable frame pacing but unreadable HUD text, or readable text but an incorrect glyph. Use separate fields for text scale, HUD contrast, menu navigation, aiming, defence input, camera control and vibration. Take screenshots at the native resolution when possible and note whether the display is external or built in.
For controller reports, compare the default layout with one intentional remap. Keep keyboard, Xbox-style and PlayStation-style prompts distinct. If the button performs the action but the glyph is wrong, report a UI mismatch. If the action cannot be bound or is ignored, report a functional input problem with the controller model and connection method.
Test frame pacing during combat
A quiet menu can hide a performance problem. Repeat the same early combat area, observe camera turns, enemy groups, soul effects and defensive input, and record whether frame delivery or input response changes. Use one setting change at a time. Do not publish a universal FPS value from a single scene or call a Deck preset “recommended” without a source date and build.
If a display option improves frame pacing but harms combat readability, describe the tradeoff rather than choosing for every player. Record resolution, scaling, preset, cap, TDP or power profile, and whether a shader cache or first-run process was active.
Use Proton evidence carefully
ProtonDB is third-party telemetry. It can reveal that players are testing the app through a translation layer, but it does not prove native Linux support or a final Deck verdict. Link the observation, date and rating context, and label it community evidence. A Steam Community troubleshooting post authored by the publisher is a stronger source for a known demo issue, but it still needs the exact product and symptom.
For a complete handheld report, include whether the text is readable at native resolution, whether a 30-minute session changes power or temperature behaviour, and whether the first combat area keeps the same input response as the menu. Record the Deck model, OS image, Proton version, TDP or frame cap, and whether the display is internal or external. If only a desktop controller was tested, do not call the result a Deck result.
When a glyph mismatch appears, try the default Steam Input layout before remapping. If a remap fixes the action, document the exact binding and whether it changes another command. If the issue persists, preserve a screenshot and send it to the Technical update queue. Avoid promising that a community layout will survive a product update.
Sources and check date
Source: Steam Store AppID 2638890
Source: Official Steam Community hub
Source: ProtonDB third-party app page
Checked 2026-08-09 UTC. Steam Deck performance, controller glyphs and Proton behaviour require reproducible testing.