Search Issue Tracker
Fixed in 2020.3.42f1
Fixed in 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a12
Votes
0
Found in
2019.4.39f1
2020.3.37f1
2021.3.6f1
2022.1.10f1
2022.2.0b2
2023.1.0a4
Issue ID
UUM-10016
Regression
No
Lightmap Streaming Priority field's value doesn't change when an unacceptable value is entered
Reproduction steps:
- Create a new project
- Enable the “Lightmap Streaming Enabled” option (Edit > Project Settings > Player > Other Settings)
- Enter a value below -128 or above 127 into the “Streaming Priority” field located under the “Lightmap Streaming Enabled” option
- Observe the field’s value
Expected result: The value gets set to -128 if it’s set to less than -128 and to 127 if it’s set to above 127
Actual result: The value remains higher or lower than the limit
Reproducible with: 2019.4.39f1, 2020.3.37f1, 2021.3.6f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproducible on: Windows 10 (21H2)
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 2023.1):
Resolved in PR: https://github.cds.internal.unity3d.com/unity/unity/pull/13631