I’ve been using Resources.Load() since ever, and now that I’ve read about Addressables and their advantages I decided to try them out. I noticed that marking something in the resource folder as an addressable takes it away from that folder. So, it’s either one or the other. For what I read it seems that Addressables are better in any possible way.
So, before taking everything away from resources my question is if we should abandond completely the Resources folder or if it’s still better at doing something?
Interesting, and thanks for the information. I hadn’t looked into addressibles just yet.
Based on your information, I can make one recommendation however: don’t give up on Resources.Load<>() completely just yet… there are a LOT of other packages out there that rely on Resources.Load(), and that’s gonna continue for a while yet.
If you want to do it, I would start with one particular small group of assets in one of your games, mark just those as addressibles, and after getting comfy with it, expand it from there.
And it really isn’t “better” or not; it’s more about maintaining existing code and interoperating with existing code.
Well, they say that it is better. That it’s async, and that it just halves your loading times, that it’s more scalable, practical, etc. etc… I’m not talking about deleting the Resources folder or anything like that either, just moving the assets that should be loaded into the addresable system.
Though, I believe your advice of moving with caution is really good: just trying to build this thing crashed my pc (something that seems to be happening almost once per hour after updating to 2019.2.15)