Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0a6
2019.3.0b1
2020.1.0a1
Issue ID
1182109
Regression
Yes
Script Execution Order values are cropped when using certain UI scaling values
Steps to reproduce:
1. Open project attached by the user "19.3.zip"
2. Edit -> Preferences -> UI Scaling
3. Make sure that "Use default desktop setting" is selected
4. Edit -> Project Settings -> Script Execution Order
5. Add a few scripts into the Script Execution Order
6. Right-click on desktop -> Display settings -> Scale and layout
7. Change Scale (Change the size of text, apps, and other items)
8. Observe Script Execution Order values
Expected result: Order values are not cropped
Actual result: Order values are cropped
Reproducible with: 2019.3.0a6, 2019.3.0b3, 2020.1.0a4
Not reproducible with: 2019.3.0a5
Notes:
- Was not able to test with versions before 2019.3.0a3, because they don't have UI Scaling in Preferences
- In the first affected versions, the values are cropped only when scaling is set to 125
- In latest versions (2019.3.0b3 and 2020.1.0a4) at scaling 100, 125, 200, 225 all order values are cropped
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a12