Search Unity

Unity Hub does not recognize Patch Releases

Discussion in 'Unity Hub' started by Din0m1te, Mar 18, 2018.

  1. Din0m1te

    Din0m1te

    Joined:
    Sep 9, 2015
    Posts:
    34
    Hi,

    here's how to repdouce:
    - Install 2017.3.1f1 e.g.
    - Locate the installation in the hub
    - Install 2017.3.1p4 at the same destination as a Patch
    --> The hub will still think its 2017.3.1f1
    --> Locating the same Editor executable again will create a 2017.3.1p4 entry in the hub
    --> But it keeps the 2017.3.1f1 entry too, which points to the same editor version

    What'd I suggest:
    Solution 1: Add an option to remove a located editor version from the hub manually
    Solution 2: The hub should update the 2017.3.1f1 entry to be p4
     
    Din0m1te, Mar 18, 2018
    #1

  2. AbrahamDUnity

    AbrahamDUnity

    Unity Technologies

    Joined:
    Jun 28, 2017
    Posts:
    431
    Hello,

    Thanks for the feedback. I think the "Locate" feature is not really achieving what you expect. What it actually does is locate an editor in a given path. It doesn't bind to a certain version in the sense that it won't follow 2017.3 up to the last installed patch. If you go through a new install you have to re-locate that version (and remove the initial version through the Hub).

    I hope this clarifies it.

    Cheers,
     
    AbrahamDUnity, Mar 23, 2018
    #2