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
- "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.2):
Fixed in 2020.2.0a8