After spending some time in Unity, the whole Assets ‘thing’ in the Store and inside Unity is really getting on my nerves.
First of all, why is there NO way to define a download folder for Assets? Now I have to hunt down the asset files in some obscure folder somewhere hidden in the user folders on my C:\ drive.
So much diskspace lost here, we don’t all have 1Tb SSD’s…
There’s a way to set the Unity cache, so why not set a download folder for assets?
Second, Why can I see an update button for Assets ONLY inside the Unity Store window, and not in the Store when accessed from a browser?
Thirdly, why CAN’T I just download Assets from the Store straight to disk, instead of going through the whole Unity loop? It all makes moving files around so much more cumbersome.
This is more than likely the Internets inability to route through your computer and check the status of files. It’s only a guess, but I’d imagine it’d be relatively risky to give a webpage the ability to check through your C drive. As I said, only a guess.
I think this is just something Unity haven’t gotten round too yet. It looks like their design around the packages features expects users to just access them through Unity Editor’s UI, rather than playing with them directly. This is something it’d be good for them to address eventually.
I think for the time being you need to just accept it is what it is, but some ‘points’ on the feature request, and see how you can work around it. In this case symbolic links seem like the way to go. That’s how I share assets with the same meta information between multiple projects.
It’s not the ‘on disk’ check I care about, but on the web I cannot see if there’s an update available on one of my Assets.
The webpage just has to compare the downloaded version to the one available in the Store. (metadata?)
Yes, it would be awesome if there’s a bit more control on these things.
