Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.0f1
2019.2.14f1
Issue ID
1214006
Regression
No
Reading from PS4 controller fails after the built project loses focus if "Visible in Background" is disabled
Repro steps:
1. Open the user's attached project "crap.zip"
2. Make sure that "Visible in Background" is disabled in Project Settings > Player > Resolution and Presentation
3. Connect the PS4 controller to the computer
4. Build and Run
5. In the newly opened window, press Play!
6. Alt+Tab to lose focus of the app
7. Go back to the app and try moving the left joystick
Expected results: Controller's input is read and different lines of the list are highlighted accordingly
Actual results: Controller's input is ignored
Reproducible with: 2019.2.0f1, 2019.2.20f1,
Not reproducible with: 2019.3.0b2, 2019.3.0b12, 2019.3.0f6, 2020.1.0a1, 2020.1.0a20
Could not test with: 2017.4, 2018.4, 2019.2.0a1, 2019.2.0b10, 2019.3.0a1, 2019.3.0b1 due to missing scripts and errors
Notes:
-The issue does not reproduce with the Xbox One controller
-Even once the controller is unplugged, the app is impossible to close unless stopped by Task Manager
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
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Resolution Note (2019.3.X):
2019.2 is no longer supported and it works with 2019.3 and 2020.1