Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Resolved The 2019.3 beta disappeared from the hub

Discussion in '2019.3 Beta' started by 5argon, Nov 28, 2019.

  1. 5argon

    5argon

    Joined:
    Jun 10, 2013
    Posts:
    1,555
    The Hub was removing old sub-versions which is not ideal since installing those manually I cannot easily select or add components later. But now also the beta disappeared.

    Screenshot 2019-11-28 13.51.26.png

    To install, I must go to the site and click the install from hub button

    Screenshot 2019-11-28 13.56.27.png
     
    menderbug, WolveX and mkracik like this.
  2. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    880
    And no option to select rc either
     
  3. bugfinders

    bugfinders

    Joined:
    Jul 5, 2018
    Posts:
    1,596
    My hub offered 2019.3 as a download for a released version....
     
  4. siggigg

    siggigg

    Joined:
    Apr 11, 2018
    Posts:
    247
    Yep I have the same issue right now. Could download the RC at home last night, but currently no 2019.3 (beta or RC) on Hub atm. But yes the "download with Hub" link on web works.
     
  5. andybak

    andybak

    Joined:
    Jan 14, 2017
    Posts:
    569
    I think 2019 release is near. It appeared as f1 in my hub then disappeared again.
     
  6. bugfinders

    bugfinders

    Joined:
    Jul 5, 2018
    Posts:
    1,596
    I must have gotten in when it was on and then taken off again
     
  7. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,132
  8. DeepShader

    DeepShader

    Joined:
    May 29, 2009
    Posts:
    682
    Any timeframe for Hub 2.3?
     
  9. Paul-Swanson

    Paul-Swanson

    Joined:
    Jan 22, 2014
    Posts:
    317
    you can also trick hub into grabbing it by going here
    https://unity3d.com/unity/beta/2019.3
    Then push the button that says "Install Version from Unity Hub"
    It opened my hub then downloaded it despite it not being present.
    No need for the new hub if you go this way. Guessing is a local index or something even though its actually accessible. This does for the record work with with hub version 2.2.0
     
  10. DeepShader

    DeepShader

    Joined:
    May 29, 2009
    Posts:
    682
    That works - thank you :)
     
  11. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,132
    Update: the plan is now to release 2.2.1 with the fix today.
     
  12. StaggartCreations

    StaggartCreations

    Joined:
    Feb 18, 2015
    Posts:
    2,237
    charlesb_rm likes this.
  13. Galandil

    Galandil

    Joined:
    Oct 28, 2016
    Posts:
    13
    My Hub just updated to 2.2.1, but still no trace of any 2019.3.
     

    Attached Files:

    RogDolos and Lars-Steenhoff like this.
  14. route1rodent

    route1rodent

    Joined:
    Dec 8, 2018
    Posts:
    2
    Is there a button for "check for updates" in hub? I am still on 2.2.0
     
  15. charlesb_rm

    charlesb_rm

    Joined:
    Jan 18, 2017
    Posts:
    485
    Unity 2019.3.0f1 should now appear again in the Hub. You can quit the hub and restart it to make it refresh the list.
     
  16. Kichang-Kim

    Kichang-Kim

    Joined:
    Oct 19, 2010
    Posts:
    1,008
    charlesb_rm likes this.
  17. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    I feel that release candidate showing up as full release is a big mistake from Unity Hub team, you guys really should figure out some way to indicate it's RC and not full release.

    Because of the f1 suffix (and Unity hub showing it for some on full release list), people have been posting 2019.3 gotten released everywhere I go on Unity communities and this is hugely misleading for users.

    Just having a dedicated page for that version alone that says it's RC is not enough because most people won't even open that link in normal conditions (nor many know how to even find that link unless others post it like happened now when Hub lost the RC).
     
    TextusGames, Khan_Yasin and BTStone like this.
  18. andybak

    andybak

    Joined:
    Jan 14, 2017
    Posts:
    569
    @rizu Isn't it usually only a couple of days before an RC is promoted to release?
     
  19. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    @andybak I can't remember seeing that ever happening on this current release model Unity has. Even if they turned RC into release for some reason as is, fairly certain it would still get additional f-version for the sake of making it clear to users it's a full release now.

    They haven't always done RC's though, like for example 2019.2 didn't get one but 2019.1 did (https://unity3d.com/unity/beta/2019.1.0f1).
     
  20. TextusGames

    TextusGames

    Joined:
    Dec 8, 2016
    Posts:
    429
    Release candidates should be named with different suffix. Unity 2019.3rc1. Why do you use "f" - suffix for both release candidate and final release?
     
  21. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    I think the suffix thing is to not create additional things to break on the current package system versioning. Do remember that packages can have dependencies not only on the major version but also on the suffix so adding one more variant to the mix could cause more issues there (we already saw bunch in past when public alphas arrived).
     
  22. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
  23. bugfinders

    bugfinders

    Joined:
    Jul 5, 2018
    Posts:
    1,596
    I also wish the hub allowed you to default the version you worked with rather than needing to click on the drop down each time of a beta/alpha is the oldest install then it defaults to what is oldest and not the production build.
     
  24. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    I think it remembers your last pick now, but it's still useless IMO as you actually have to click on the thing first to see what it will use. It's all backwards and really bad UX.

    There's would be a "simple" solution for this: put the version selection on the new project section like it was on Hub 1.x but additionally refresh the template list immediately if user swaps to different engine version. This is what most users would want to see but yet it's not implemented this way.

    This is again one of the things that feel it's done all backwards just to make some internal process simpler but this is not what Hub should be about, it should make things easier for the end user rather.
     
    bugfinders likes this.