What the result actually measures
The finder does not probe a console. It filters a maintained evidence dataset by game, console and support level, then displays the source, verification date, scope and exact uncertainty.
Measurement boundary: Game patches, console firmware, region and game mode can change behavior. “Unverified” means Keymap lacks a current primary source, not that support is absent.
How to interpret the output
Native play
A current primary source documents mouse/keyboard control in gameplay for the stated platform scope.
Limited
Only menus, chat, one device, one mode or another constrained path is documented.
Unverified
No adequate current primary source is in the shipped dataset; no yes/no claim is made.
Troubleshooting unexpected results
Device works in console UI only
System-level recognition does not prove a game implements gameplay input. Check the game-specific source and settings.
Prompts switch repeatedly
Disconnect unused devices, inspect game input-lock settings and test the mouse, keyboard and controller separately.
Frequently asked questions
Why is the list intentionally small?
A short sourced list is safer than a large copied list with stale or mode-specific claims.
Does an adapter count as native support?
No. The finder tracks documented native input and does not endorse translation adapters.
Can support change?
Yes. Every row includes a verified date and source so readers can recheck the current state.
