I would like to request adding an Assets Loading System, that will take responsibility to load any requested assets.
I have an in-depth knowledge of how to set up such a system. Maybe it’s too early for this, but just to start the discussion of what needs to be available in the future.
That’s actually a good piece of code .
One thing I would like to say: try to make it as Generic as possible to handle other AssetReferences (Textures, Sprites, etc.)
I will try to publish my version this weekend but this is already a good start for this thread
Hey @GhAyoub , it was definitely part of the plan to introduce Addressable assets, even though this project doesn’t have dynamically changing assets, but it can still benefit from it in terms of loading times and build times.
The only thing that pushes me back is that introducing Addressables on a project of this scale means everyone now HAS to know how to use them to work on the project.
Hey @cirocontinisio , I totally agree with you and that’s what made me think, before making a pull request, that I’m actually forcing a system that we will not benefit from it too much for the time being.
I will wait for the time that we can discuss it together and make a system that fits what we need.