from Resource to Asset Bundle

I use Resource a lot for loading streamed dialogue. I see in the doc that Asset Bundles are preferred, does that apply in the case of streamed audio? And how can the new AB graph editor help transition from resource folder (which is so easy to deal with) to AB (not so much)

 

laurentlavigne, thank you for making the good point. This is one of the area we have been targeting to improve. AssetBundleGraphTool does not directly offer API level replacement today. Please look forward for our update.

 

Oh I see, like the script updater does for deprecated API. Access to Resource and AB is very different so this automated updater doesn't sound trivial so thank you for taking that on

The documentation on the asset pipeline (https://unity3d.com/learn/tutorials...tbundle-usage-patterns#Managing_Loaded_Assets) talks about file handle, Object's lifecycle and other things which I don't quite understand. Is this what the upcoming workflow will tackle?

 

This looks like an awesome phase 1. Thanks for sharing the plan. I must admit AB stayed under my radar until I had to pay attention to memory on mobile.
It is probably a bit off topic but for some reason it resonates with me: The distinction between a scene and an instance seems artificial, are there plans to merge those?

 

This looks really cool and a great transition. So, instead of being in sharedassetsX.asset, the option will be available to use something like AssetBundleGraph to package the assets into different locations. Will the option to export assets to a specific path be available like Data/Bundles?

 

Ah ok gotcha! So I can effectively create that on my backend and customise it to my liking. I just feel that more documentation would make it easier for developers to dip their toes into the assetbundle lifestyle

 

Hi! Is #2 still on the works? I am trying to find a simple way of transitioning from my heavy used resource folder to using asset bundles.

Have had no luck Even tutorials are all focused on the use of bundles for patching not for migrating.

Thanks in advance for the answer!

 

first of all:


now addressables, I like how you move the responsibility of building AB to some snap on component, are they in some shape or form available?

 

Me like! Thanks!

Do you know if this would be available by june/july?

 

<3
This will solve all our problems with asset bundles! You and your team deserve a pay rise!

 

Hi @Reichert. Does ResourceManager addressed game object pooling issue too? Refer to: https://forum.unity.com/threads/request-gc-free-gameobject-name-api.517378/#post-3392263

 

@hiroko

Gentlemen, we're in the future now, so, how do I "seamlessly transition" to bundles?

 

If I understand correctly this meant that Unity would auto split a project (even direct references, not just stuff in Resources folder) into asset bundles when building and you could have a reasonably split game for delta patching, without having to change anything?

Has this happened (I’m guessing, no?) will it happen?

 

Text mesh pro still relies on Resources. The future feels far away.

 

The whole Resources API should be deprecated entirely... just a bunch of 3rd party libs use it.

For what it's worth, you never want to use Resources if you can avoid it. Loading anything from there doesn't use threads at all, so it blocks the main execution context. Consider using AssetBundles instead. Even if they are built and shipped along with your application, it's better for load times and asset compression etc.

Shameless plug... if you want to use my AutoBuilder asset, it has a really trivial API that you can swap in without changing any other code. Or change it slightly and get fully async loading.

 

Instead of automatic transition from resources to asset bundles, we got an asset bundle manager that can't even load stuff synchronously out of the box, likes to rebuild bundles needlessly and is somehow slower when dealing with hundreds of bundles.

The future has been canceled.