-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Unity to 2019 LTS #655
Comments
I suggest updating to version 2019.4.28f1 or version 2020.3.10f1. They are both LTS versions of Unity. Furthermore, I noticed that Visual Studio sync way better with Unity when I update the project to version 2019.4.28f1, it's pretty much out of the box from my tests. With the actual version, I had quite a fun time trying to sync Visual studio and had to give up eventually. That's one of the perks I see from upgrading into this version, and I'll try with 2020.3.10f1 too. |
Many of us want to update to at least 2020 due to the integrated (free) dark mode. |
Ok so here's my experimentations with Unity 2020 so far. I downloaded Unity 2020.3.11, the present LTS version. I downloaded a clean clone of the project, and upgraded it to 2020.3.11. First thing after the upgrade, Unity asks for urp material upgrade. I accepted as it's mandatory. I tried launching the main station scene, and run into a few errors :
They're both network related errors as shown below, Mirror is involved (I'm showing only for the second one, but the first one is similar) :
That's pretty obscure to me as of what's going on there. It just reminded me of the link posted by @Ryan089 warning about Mirror stability in 2020 versions of Unity . Fixing those errors is beyond my understanding for now, so maybe someone else can take a look into it ? I also found this guide to update from 2019 to 2020 , which could be useful to someone with a better overall understanding of the project. That's where I'm at with the 2020 version attempt to update. |
Decided on 2019 LTS for now. |
Summary
We're still on like 2019.3.12.... wth... time to update!
The text was updated successfully, but these errors were encountered: