Godot Version
4.5 stable
Question
I’m not sure how I can have joystick input working in the embedded game window on MacOS. The key equivalents work fine but the wired USB joystick seems to be being ignored in the embedded window (either floating or not). Input works fine if the game’s in a separate window as in 4.4.
I’ve clicked ‘Allow game input’ and I’ve tried the demo joypad project too. The joypads are detected but no input shows up in any embedded game.
In the console, I see a warning:
<C++ Source> platform/macos/embedded_debugger.mm:180 @ parse_message()
<Stack Trace> joypads.gd:14 @ @implicit_new()
MacOS 26? This seems to be a known issue, although I am getting this error in embedded game view and windowed mode.
opened 02:26PM - 13 Sep 25 UTC
bug
platform:macos
topic:porting
confirmed
### Tested versions
- Reproducible in: v4.5.rc2.official.2dd26a027, v4.5.rc1.of… ficial.6c9aa4c7d
- Not Reproducible in: 4.5-beta7 - 4.4
### System information
GodotEngine v4.5.rc2.official.2dd26a027(macOS_arm64,Forward+), Mac Studio M4 Max, 36 GB RAM, macOS Tahoe 26.0 (25A353), DualSense Wireless Controller (connected via Thunderbolt)
### Issue description
Joystick/controller input is no longer functional when testing games in the embedded game view within the Godot editor. The issue appears to be specific to the embedded debugger on macOS, as evidenced by the error message.
**Error output**
```
W 0:00:00:194 app.gd:3 @ @static_initializer(): Unknown message: joy_add
<C++ Source> platform/macos/embedded_debugger.mm:180 @ parse_message()
<Stack Trace> app.gd:3 @ @static_initializer()
```
### Steps to reproduce
1. Connect a controller (DualSense Wireless Controller via Thunderbolt)
2. Run the project in the embedded game view (not as a separate window)
3. Observe the output in the debugger console
4. Attempt to use controller input
### Minimal reproduction project (MRP)
A simple project with basic controller input detection would be helpful, but an empty project will output the same warning.
1 Like
I’m on 26/Tahoe yes. Ah that explains it then, thanks.