Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
2
Found in
2022.3.3f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-40768
Regression
No
Scriptable Objects do not get created when generating from Source Generators
Reproduction steps:
1. Open the attached “Test Project” project
2. Create a new Asset by right-clicking in the Project window and selecting Create > Scriptable Values > ClassTest
3. Observe the newly created SO in the Inspector window
Expected result: The “Script” variable is set to an appropriate Script
Actual result: The “Script” variable is not set to anything
Reproducible with: 2022.3.3f1, 2023.1.1f1, 2023.2.0a20
Couldn’t test with: 2021.3.27f1 - No support for “GenerateScriptableValue”
Reproducible on: Windows 10
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Today we only support this kind of behavior when the cs file are imported.
The reason is that is how we deterministically track its ID, the ID are part of the *.cs.meta file.
Hopefully we can solve this at a later time, but currently this is sadly not something we can handle.
Resolution Note (2023.2.X):
Today we only support this kind of behavior when the cs file are imported.
The reason is that is how we deterministically track its ID, the ID are part of the *.cs.meta file.
Hopefully we can solve this at a later time, but currently this is sadly not something we can handle.