Official Unity 2020 LTS Is Now Available

Cannot seem to find this out by other means so I'll ask here...
Does LongTimeSupport, LTS, apply to LTS versions that are earlier than the final LTS build?
Or is LTS only apply to the latest updated LTS version.
I have 2019LTS but there are many, many "updates" of 2019LTS.
Which one is actually LTS, or are they all supported?

 

LTS is for major "year" version. Like Unity 2019. The "many versions" comes from development and bug fixes (in other word: support). You always should choose the latest if you decide to use that.

 

Thanks. Sorry for the confusion and probable "off topic" but does it mean the earlier LTS versions are no longer "supported long term"?
Or to put it this way..does my very early 2019LTS version still have LTS? I'm asking 'cause I read many posters who have updated to newer LTS versions with less than good results and outcomes!

 

You can always find the answer on Unity's release page: https://unity.com/releases/2019-lts
Unity guarantees the two year support for LTS versions, 2019LTS was shipped in early 2020, so it will retire in early 2022. But this doesn't mean everything ends there, only the guaranteed bugfixes will end. You can use it moving forward if you want and can take the chance. And LTS versions are fairly stable at the end of their cycle thanks for the extensive in-house and user tests and continuous bug-fixes.

You do not have "early LTS" version. 2019LTS. End of story. No late or early. The support means it gets bug fixes with new releases (currently 2019.4.29f1) - the 29 means it got a lot of bug fixes already. 2019.4 is the LTS version of the 2019 line, it gets the support, .29 contains the most bug fixes.

 

Many thanks, Lurking-Ninja. Cleared things up.

 

It appears that a bug has now been filed for this. If anyone else has this issue, go vote for it! https://issuetracker.unity3d.com/issues/findkernel-doesnt-work-when-player-built-in-server-build

 

Why is Unity installer so bloated? If you could install Hub then whatever you need or want after that there would be a lot less problems.

 

Cannot upgrade from either Unity 2020.3.19 LTS or 2020.3.17 to Unity 2020.3.20.
It gives error and the project gets corrupted.

I also tried deleting the library folder and perform the upgrade but the issue persists.

 

Wow, they pulled the update from unity hub.
Another half assed, broken update.

What a mess dealing with Unity has become

 

Did they? I still see it.

 

I just checked and it is back up now as you said.
It was not available when I made my post.

 

Good evening. I have a problem. Unity 2020 is not installed.3.20 via Hub 2.4.5. Win7 64bit system

 

And do you have the KB2533623 update as the Unity Hub informs you?

 

I hope it is not only me who gets a 403 error when trying to access the latest (2020.3.28f1) release notes: https://unity3d.com/unity/whats-new/2020.3.28

 

@MiTschMR not the only one.

@LeonhardP can you at Unity please make this release for 2020.3.28f1 notes public ?

 

They are accessible now. Thank you.

 

One question tough. Everytime we update to a newer version, we still have to trashcan the previous projects 'cause of the message "the project you are trying to open was done with a previous version and cannot be opened with this"? Still no backward compatibility on the horizon?

 

There have been backward compatibility since forever, you just misread the message that appeared.

 

well, what to do then.

 

Backup your project before update, then.
Or use version control systems. Simply using Git would be enough to be able to revert back.

Is Unity upgrades the only issue? You've never made a mistake that you had to revert? A scene merge? A reference update in scenes? How do you handle these kind of things?

 

Is there an issue with unity and Visual Studio? Keep loosing namespaces and having to have to "Regenrate Project Files"?

 

Happens for me too from time to time, but its rare enough for me to not loose my mind over it
For me this started after i switched to VS2019 from VS2017, I think it did'nt happen with VS2017 back then ...

 

Unity version naming getting a little too elaborate at this point.

 

Are lists still broken for custom data types?