Search Issue Tracker
Fixed in 2018.3.X
Votes
4
Found in
2017.3.0b9
Issue ID
969107
Regression
No
[ScriptedImporter] "SetMainObject" does not set "ScriptableObjects" as main Asset
Reproduction steps:
1. Open "ScriptedImportedTest2017.3.zip" project
2. Compare "CubeImporter" and "FooAssetImporter"
3. See the created Assets by the importers
Expected Result: "SetMainAsset" sets the Scriptable Object as the main asset
Actual Result: "SetMainAsset" doesn't set the Scriptable Object as the main asset
Fixed in: 2018.3.0a8
Reproduced with: 2018.1.0a6, 2017.3.0f1, 2017.2.0p4, 2017.1.2p3
Note:
Change these functions from the importers for 2017.2 and below
"AddObjectToAsset" -> "AddSubAsset"
"SetMainObject" -> "SetMainAsset"
From 2017.2 and down it's broken not only with ScriptableObjects
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Add comment