Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a1
2020.1.0a1
2020.1.0a14
Issue ID
1200127
Regression
No
[Preset] Changing properties of a terrain preset also changes the properties of the terrain GameObject and viceversa
Changing properties of a terrain preset also changes the properties of the terrain in the instance and prefab. If prefab wasn't made, preset changes the properties of the terrain GameObject with that component. Refer the attached video
Steps to reproduce:
1) Create a new project
2) GameObject > 3d Object > Terrain
3) Create preset for Terrain
4) Uncheck Fill Heightmap and in Address mode dropdown select Clamp
Actual result: The changes in the Terrain preset can also be seen in the Terrain GameObject
Expected result: A preset is a template for default properties for new components and Asset importers. Changes in the preset should never be reflected on the GameObject with that component
Occurring on: 2020.1.0a14, 2019.3.0b12
Note: Terrain preset cannot be modified for 2019.2.11f1
Environment: Both Windows and Mac
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2020.1.X):
This is an unfortunate result of using an Inspector as a Tool window.
The tool settings are stored as user preferences, so they don't react to presets.
The terrain-specific settings are stored on the terrain, and do use presets properly.
The ideal solution here is to move tool behaviors outside of the inspector window.
We are in the process of building the systems for first-class tools and tool windows.
Once we have that, we can move these tools to use the tool windows instead of the inspector, and solve the confusion in the UX.