Search Issue Tracker
Won't Fix
Won't Fix in 6000.2.X
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
Issue ID
UUM-109246
Regression
No
Game View's scale slider bar gets set to 2.5x when entering Play Mode
How to reproduce:
1. Create any new project
2. Open the Game view
3. Set the scale of the Game view to 1x
4. Enter Play Mode
5. Observe the scale slider bar
Expected result: The scale remains 1x
Actual result: The scale changes to 2.5x
Reproducible with: 2022.1.0a6, 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproducible environments: Windows 10
Not reproducible environments: No other environments tested
Notes:
- After reproduction, it is impossible to revert the scale back to 1x; 2.5x becomes the minimum setting
- When creating a new project after the first reproduction, it is initialized with a scale of 2.5x already set
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. We know each case is different, so do please continue to log any issues you find, as well as provide general feedback.
Resolution Note (6000.2.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. We know each case is different, so do please continue to log any issues you find, as well as provide general feedback.