search

Unity-Technologies / Addressables-Sample

Demo project using Addressables package
1.29k stars 298 forks source link

Official untested examples? #53

Open noncom opened 3 years ago

noncom commented 3 years ago

I got to this repo from the Unity's official Addressables how-to page: https://unity.com/how-to/simplify-your-content-management-addressables, where it says:

Where can I learn more about Addressables? If you want to use Addressables in your project, check out the Addressable Asset System documentation to learn how to get started. Read our blog post, check out the GitHub Samples, or join the discussions on forums.

Where the "GitHub Samples" link leads to this repo. And now I get to this repo and what do I see? The first paragraph of the readme literally says:

These are intended as jumping off points for your own development. These have not been tested, and are not guaranteed to work in your situation. They are just examples, to make some concepts easier to understand, or easier to replicate in your own project. Use at your own risk.

At the moment of writing this:

The issue I have with all this is: what am I even implied to think about all this?! Why Unity does not take care to keep a working, verified, updated and guaranteed set of examples of one of its most important new features?

Am I supposed to use these examples, or does Unity know beforehand that they are suboptimal and do not reflect the way of doing things? Why are we left with these examples then? Why doesn't anyone at Unity make real examples that are tested, guaranteed to work and are not risky to use?

Can Unity please make sure that the examples for using its advertised technologies and features are up-to-date, working and are safe to refer to and use when looking to learn the aforementioned technologies?

kirstenpilla commented 2 years ago

Hi @noncom thank you for your feedback! Will share this issue with the rest of the Addressables team!

Inspyro commented 1 year ago

As it stands now the example seem totally unusable. For example the CheckBundleDupeDependenciesMultiIsolatedGroups is using internal code that cannot be accessed from our code.

Has anybody really though this systems through? There seems to be no clear interface or extension points for what should be a rather trivial operation (i.e. analyze addressable dependencies)