Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
1
Found in
2018.4.0f1
2018.4.2f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1178561
Regression
No
Screen.fullScreenMode is always returning a default value even though it is set to be a different one
How to reproduce:
1. Open "SampleScene" Scene in the attached "Repro1178561.zip" Project
2. Enter Play Mode
3. Observe the console
Expected Behaviour: The Screen.fullScreenMode is set to 0 and logged in the console as 0
Actual Behaviour: The Screen.fullScreenMode is logged to be a default -1
Reproducible with: 2018.4.7f1, 2019.2.2f1, 2019.3.0b1, 2020.1.0a1
Comments (1)
-
KirbyFan
Sep 29, 2024 15:07
This exact thing happens to me in Unity 2022.3.44f1
I've been able to reproduce it by
- creating Universal 3D project,
- adding an empty object to the scene,
- attaching a c# script to the empty object
- in `start()` adding `Debug.Log(Screen.fullScreenMode)`and it returns -1 in play mode
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
- Text render issues and various exceptions in TextCore when using TextSettings option "Match Material Presets"
- NullReferenceException error is thrown when unpacking multiple instances of the same UI Document
- URP Decal Projectors don't render when they are hidden in the Hierarchy, unlike other GameObjects
- Reflection Probe “adjusting number of stops to over or under expose the texture” setting does not update in Scene realtime
- UI Toolkit rendered text breaks when toggling FontWeight styles through code
Resolution Note (fix version 2020.1):
fixed in 2020.1.0a4, backported to 2019.3.0b4, 2019.2.6f1, 2018.4.10f1