Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2019.4
2020.3
2020.3.12f1
2021.1
2021.2
Issue ID
1343776
Regression
No
Preset is not applied to ScriptableObject created from context menu when using a glob filter
How to reproduce:
1. Open the attached project
2. In the Project Window, open the 'FilterTest' folder
3. In the folder, create the 'Test Scriptable Object' asset (Create->Test Scriptable Object)
4. Inspect the created Scriptable Object's property values
Expected result: Scriptable Object property values are equal to 'TestScriptableObject-Filtered.preset' values
Actual result: Preset is not applied
Reproducible with: 2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1
Workaround: Use Preset.ApplyTo in an AssetPostprocessor
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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a7