AssetDatabase.AddObjectToAsset doesn't seem to work with ScriptableObjects

Adding sub-objects (a material, texture, animation clip, etc...) to a ScriptableObject using AssetDatabase.AddObjectToAsset doesn't seem to work. As you can see in the attached image, both the ScriptableObject and in this case an animation clip are instead added to a new empty object.



Adding sub-objects to a Material or Texture or a .fontsettings object works as expected.




According to the documentation, "Please note that you should only add assets to '.asset' files" ... ScriptableObjects are .asset files and this doesn't work (for me anyway).

Can anyone else confirm this?

 

Is this a bug or am I missing something here?

 

Just updating this thread with additional information.

As per the attached pictures, AssetDatabase.AddObjectToAsset doesn't work either with objects Animation clips either.

Before


After

 

Having the same issue here.

I'm trying to add a Texture2D to a ScriptableObject.
No matter what I do, the best thing I can get is the ScriptableObject added to the Texture.

Any news on this?

 

Filed a bug report over 2 months ago but haven't heard anything yet

 

Would it be possible to get an update from the Unity Gods on this?

 

My last info: The bug has been reproduced, the ticket's still open.

 

QA team have reproduced this problem, and it's with Devs for a fix.

 

Thanks

 

any fix?
any news?
any workaround?
or working as intended?
thanks

 

No news, it's sat with Devs for over a year. :-(

 

i guess it is easier to manage separate files in folders anyway
but thousands!?
should i use this broken & forgotten code to transform my assets into malformed anomalies or just use files?

 

Still not fixed? wtf !?

 

Still having this problem. Can I go somewhere to vote on this being fixed soon?

 

Wow this is a bug?! I thought that was how it was meant to work.
It still kind of works, except my last added item somehow loses all data when I press "Play" on the editor.

 

http://issuetracker.unity3d.com/iss...asset-with-assetdatabase-dot-addobjecttoasset

Here's the tracking issue if you want to vote it up.

@DarkMeatGames

 

Not sure if this would be a workable solution for everyone, but I've found that if I set the hideFlags for the object to be embedded to "HideInHierarchy", everything seems to work correctly.

I had a scenario where ScriptableObject1 had a list of another ScriptableObject2. Instead of having hundreds of ScriptableObject2 assets lying around, I wanted to embed them directly into ScriptableObject1. Using AddObjectToAsset, I found that as reported above, the hierarchy shows up incorrectly, and I couldn't change the name of the asset.

But if I set ScriptableObject2's hideFlags to HideInHierarchy, it draws correctly in the project view and doesn't throw any weird errors. I can verify that ScriptableObject2 is being successfully embedded in ScriptableObject1 by opening the ScriptableObject1.asset file and seeing the ScriptableObject2 data in there.

This works for my needs, but of course a downside is that the inner asset doesn't show up in the project view. For my purposes, that's fine.

 

Not resolved in U5.3.3p2. Shame on you. For me this if no Top priority is High priority. Why is closed? I've come to same solution as @kromenek (HideFlags.HideInHierachy before add and losing show up in Project view, which is very important when u developing somthing to check, u not do grabage)

 

This still appears to be an issue in U5.3.4f1.

I created a ScriptableObject container and saved it to an .asset. I have another ScriptableObject class. Using CreateInstance I then add this new ScrtiableObject to the container using AddObjectToAsset. The hierarchy is all messed up in the editor. HideInHierarchy at least keeps the container visible at the root. It looked like there was a "fix" back in 5.3.3p1. But it isn't working in the version I've listed in this post.

[EDIT]
Apparently there is still a bug but it is related to the ScriptableObject name. If the object has no name before using AddObjectToAsset the hierarchy will become messed up. If you give the object a name the before using AddObjectToAsset the hierarchy works.

 

FYI, setting the ScriptableObject name didn't work for me in 5.3.3

The HideInHierarchy hack did, tho.

 

I am pretty sure this is not really a bug, but more a "quirk" about how objects are stored and retrieved in assets.

I talked to Richard Fine (@superpig) about this on Unite Europe and the main problem is, that there is currently no way of identifying the "main asset". Both objects inside the same file are equally capable of being the "main" asset, so Unity groups them together under one empty icon.

For the same reason, you can't just add a GameObject to another GameObject asset (because the "main asset" on an asset file containing any GameObject is defined as "the GameObject, that has no parent")

Cheers,
Imi.

 

Yes, any "HideInHierarchy" is per-Unity-Definition never a main asset, so if there is only one asset inside a file that has not HideInHierarchy, that one is the main asset.

 

I use AssetDatabase.AddObjectToAsset to add animations to animation controllers (to avoid having that many animation files...). Worked fine with 5.4, now with 5.5, it still works, it just doesn't show up in the project window until we save the project. It's kind of annoying...

 

AssetDatabase.ImportAsset(AssetDatabase.GetAssetPath(path));
is your friend here.

 

I'm currently having this bug, the asset that is supposed to be the root simple becomes a child of a random asset that was supposed to be its child instead when I hit save... Version 2019.4.7f1.

 

bumping this thread

 

Same here. AssetDatabase.AddObjectToAsset doesn't work with scriptable objects