The practical question: console keyboard mouse compatible games. This field note answers it through a defined workflow rather than a copied setting list.
System recognition is not game support
A console may recognize a keyboard in its interface while a game ignores it during play. Keymap requires a game-specific primary source before labeling gameplay support.
Rows name the exact platform scope and avoid treating a franchise as one product. If support differs by title, mode or device, the record is limited or unverified until the source says more.
Positive and negative claims need current evidence
“Supported” and “unsupported” are both claims that can become stale after patches. Each shipped record includes a verification date and links to a publisher or platform support page when it makes either conclusion.
Unverified is deliberately neutral. It means the current dataset lacks adequate primary evidence; it does not mean the device cannot work.
Protocol checklist
- Check the exact title
- Open the primary source
- Confirm the verification date
Adapters are outside native compatibility
Input translation adapters can make a device appear as another input class and may conflict with game rules or platform policies. The finder does not count an adapter path as native support or recommend bypassing a game’s input design.
Test direct connections first and follow the current publisher rules. Reports should include console, game build, device model and whether play, menus or chat were actually controlled.
Measurement boundary: Compatibility can change by game build, firmware, platform, region and mode. The finder is a dated evidence index, not a live console probe.
Use the result, then repeat it
Keep the device, platform, connection, browser or game build and the previous setting beside the result. If the observation changes, restore the baseline and change one variable. That procedure is more valuable than a precise-looking number without context.
