Fix CMD Key Issue with useKeyboardControls in Player Component #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While exploring the
useKeyboardControls
hook fromreact-three/drei
for Player component, I discovered an issue exclusive to macOS users. The hook fails to ignore the CMD key, leading to a scenario where the character begins to move non-stop in one direction after a player uses a combination of the CMD key and a movement key (e.g., CMD+S for fullscreen). This behavior disrupts the gameplay experience and conflicts with common macOS shortcuts, causing unexpected and confusing behavior for the players.Steps to Reproduce
Solution and Implementation
To address this issue, I added a feature to the custom hook that intercepts and processes keyboard events, explicitly ignoring any inputs involving the CMD key. Additionally, the hook resets the controls state whenever the CMD key is pressed, immediately halting any ongoing movement commands. This ensures the character does not move indefinitely, allowing macOS users to use system shortcuts without triggering continuous movement in the game.