This also works at overcoming the problems (points) above.) (This is a proof that the download is properly cached and its package are identified because, when pause, the connection is severed and resumed when unpaused which then check what has been done and what remains. We'll know when it will be done by having a "Pause" and "Resume" button added to the downloads in the HUB. The team is supposed to be working on adding a proper package management and I have seen it being pointed out since the early stage of HUB.
hence the original reason is foolish and useless at this point. But because the HUB fails miserably for many users, Unity is forced to keep the Installer around or they would loose quite a big chunk of their users in a single night. In other word, no practical reason for the user. The reason that was given why the HUB wasn't done the same way as the Installers is to reduce the stress on Unity file's server. This what is done with the Installer version and this is why almost nobody have any issues with using the Installers. The solution is actually quite simple and has been known by Unity since day 1 of the release of Beta HUB.īuild a proper package management that can locate missing package and requests packages individually from the server as well as properly caching them when something goes wrong so that it can be resumed afterward.
Click to expand.The Unity HUB is basically useless for some of us because it's really badly made.
0 kommentar(er)
