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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a7