Search Issue Tracker
Third Party Issue
Votes
2
Found in
2022.3.7f1
2023.1.8f1
2023.2.0b4
Issue ID
UUM-46333
Regression
Yes
[Linux][New Input System] "Select" and "Start" buttons are switched when running the Build with Proton
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the Build Settings window, change “Target Platform” to “Windows” and press Build
3. Open the Steam application
4. Add the Build to the Library (Add a Game > Add a Non-Steam Game)
5. Right-click on the Build in the Library and select “Properties”
6. Open the “Compatibility” menu
7. Make sure the “Force the use of a specific Steam Play compatibility tool” is enabled and the selected version is “Proton Experimental”
8. Press the Play button in the Steam library
9. Press the “Select” and “Start” buttons on the Controller
10. Observe the Screen
Expected result: Pressing the “Select” and “Start” buttons light up their respective representations on the Screen
Actual result: Pressing the “Select” and “Start” buttons light up each other’s representations (switched)
Reproducible with: 1.4.1, 1.5.1, 1.6.3 (2022.2.0b7, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4)
Not reproducible with: 1.4.1, 1.5.1, 1.6.3 (2021.3.29f1, 2022.2.0b6)
Reproducible on: Ubuntu 22.04
Not reproducible on: No other environment tested
Note:
- If the Build target is set to “Linux”, this issue does not reproduce
Comments (1)
-
datablob
Nov 10, 2023 14:08
Valve is fixing this in the next Proton Experimental release:
https://github.com/ValveSoftware/Proton/issues/6861
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
After investigation, we have concluded this is a third-party issue with Proton emulation of Windows.Gaming.Input API