Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-211
Regression
No
[Linux] [Input System] Unable to bind some of the controller buttons when using a wireless PowerA GameCube style controller
Reproduction steps:
1. Open a new or an existing project
2. Make sure to have the Input System package installed in the project
3. Connect the wireless PowerA GameCube style controlller
3. Go to Windows > Analysis > Input Debugger > Gamepad
4. Press all of the button on the controller and check the Input Debugger window
Expected result: You can see all of the button values change upon pressing
Actual result: Only some of the button values change upon pressing
Reproducible with: Input System 1.3.0
Notes:
- Unable to test the issue ourselves since we do not have this particular controller at the moment
- The user reported that the controller works on Windows and macOS
- The user also reported that the controller works if set up with the Legacy Input System
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.