Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2017.4
2019.3.0b11
2020.1
Issue ID
1200397
Regression
No
[Linux] [Editor] Available screens are not detected with Screen.resolutions
How to reproduce:
1. Open the attached project '1200397repro.zip'
2. Open SampleScene
3. Enter Play mode and observe the console
Expected results: Screen.resolutions.Length returns the number of available screens
Actual results: Screen.resolutions.Length always returns 0
Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a14
Note: Not reproducible in build and not reproducible at all on Windows.
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2020.2):
Fixed in version: 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in version 2020.1.3f1
Resolution Note (fix version 2019.4):
Fixed in version 2019.4.9f1