Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0a4
Issue ID
893179
Regression
Yes
Player jumps to primary display when setting resolution when secondary displays scale is not equal to primarys
Steps to reproduce:
1. Open attached project "893179.zip"
2. Build Windows Standalone Player
3. Open Windows Display Settings
4. Make sure that second displays scale differs from primary displays (eg. 100% and 125%)
5. Run the player
6. Drag the player to secondary display
7. Press space to activate Screen.SetResolution()
Expected result: resolution is set
Actual result: resolution is set, however player jumps back to primary display
Reproducible with 2017.1.0a4
Not reproducible with 2017.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment