Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.3
2020.1
2020.1.0a24
2020.2
Issue ID
1223623
Regression
No
.preset file's properties' value changes are not reflected when the values are modified in the Inspector window
How to reproduce:
1. Open the attached 'project-1223623.zip' project
2. In the Project Folder open 'Assets' > 'TemplatePresets' > 'Transform.preset' with a text editor
3. Observe the value of 'propertyPath: m_LocalPosition.x'
4. In the Project Settings select 'TemplatePresets' > 'Transform'
5. In the Inspector window change the Position X value to '123'
6. Repeat steps 2-3
Expected result: changes are reflected in the 'Transform.preset' file
Actual result: changes are NOT reflected in the 'Transform.preset' file
Reproducible with: 2018.4.19f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2
Could not test with: 2017.4.37f1 (presets not available)
Note: same behavior can be noticed when modifying the .preset file in a text editor and then observing it in the Inspector window
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a8