Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.3.0a12
2019.4.0f1
2020.1
2020.2
Issue ID
1258969
Regression
Yes
[Terrain] Modifying only 'Control Texture Resolution' or 'Base Texture Resolution' will not save the modification
How to reproduce:
1. Open attached project "Terrain Bug.zip" and scene "Test"
2. In Hierarchy window, select "Terrain" object
3. In Inspector window, change 'Control Texture Resolution' or 'Base Texture Resolution'
4. Save Scene and Project
5. Change scenes
6. Observe changed values
Expected result: the values are changed and saved
Actual result: the values were reverted and not saved
Reproducible with: 2019.3.0a12, 2019.4.2f1, 2020.1.0b14, 2020.2.0a17
Not reproducible with: 2018.4.24f1, 2019.3.0a11
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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b2
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.6f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.11f1