Question AssetReference in ScriptableObject that is always loaded(Preloaded assets in PlayerSettings)

Is it possible that addressable assets that are serialized as AssetReference in a preloaded ScriptableObject are always loaded into memory?

I am unable to find this information anywhere, if someone could point me to the correct location I would very much appreciate it.

I've tried with profiler and memory profiler, however the references they show do not provide anything tangible.

 

You will need to load them into memory yourself.

Last I remember though, the point at which pre-loaded assets are loaded into memory is too early for the addressables system to be called. It's best to manually load them in with a boot-strap scene (you'll need one using addressables anyway).

That's how I work it anyway.

 

I don't want to preload them. I am trying to figure out what is causing them to be loaded into memory without manually loading them. I cannot find any useful reference info from profiler.

 

I've tried also with memory profiler package but nothing helpful was shown as to what is holding/loading the assets into memory.

Also it was an editor capture.

 

Thanks Martin, will do that in the following week. But just for information sake: Would an AssetReference in a ScriptableObject that is included in the PreloadedAssets in PlayerSettings cause the addressable asset to be loaded into memory?

 

No I don't believe it would. I haven't experienced this at least.

Most likely some editor-specific behaviour is at play here.