Unity 2022.3 is now available as the latest LTS version on the download page and in the Unity Hub.
As always, you can learn more on our website and the release blog post. The Unity Documentation also has all the details about what’s included in this release. I know some of you may be worried about upgrading, and we have you covered with some handy upgrade guides to help you from your current version of Unity to Unity 2022 LTS. Now for you folks with complex productions with a high number of dependencies, find out how Unity Support and Services can help make the upgrade process easier.
And always remember to back up your projects before opening them in a new version of Unity. If you encounter any issues, we want to know, so please submit a bug report so it can reach our developer for them to squash it.
If you have any questions related to 2022.3, please feel free to ask them in this thread and we will do our best to follow up on them.
Just for clarity, technically speaking 2022.3.0f1 is essentially equivalent to 2022.2.22f1 as in: bump minor version to 3 and reset patch version to 0. That means it should be relatively safe (or perhaps even recommended) to upgrade from 2022.2 to 2022.3. Correct?
That’s the theory, but in reality I have yet to see an Unity LTS release that isn’t buggier and less stable than the last TECH it was supposed to iterate on.
I have been running automated builds and tests, as well as manual tests, with Unity versions 2021.2 through 2023.1 typically using the patch 0 release and the latest patch release of each minor version. That’s five different major/minor versions (will now be six).
So far I haven’t noticed anything out of the ordinary EXCEPT for two things:
2021.3.0 through 2021.3.2 (== just three patch releases) do not have a Type defined that Visual Studio and Rider plugins rely on, so I cannot test these particular versions without downgrading both of these IDE packages.
Unity.Serialization package for 2021.2 installs an older version which breaks my code, but the version that’s compatible with 2021.3 also works for 2021.2 so I’m actually using that even for 2023.1 despite that version still being experimental.
One thing to keep in mind is that packages commonly install a different version when the minor version changes. For example between 2021.2.latest and 2021.3.0 you may have the same package defaulting to two different versions, which can cause issues if you’re not prepared for that. Usually you can downgrade such a package but more often than not, analyzing that you are in such a situation and taking the right steps (eg package downgrade) takes some effort. So it’s easier to just blame it on the buggy release.
i’m not particularly happy with unity right now but, i must say it, i was waiting for this release and it feels like a solid base for at least better years for unity, i hope so
Seeing the “Unity is running with Administrator privileges…” dialog whenever I launch the Editor. No Hub installed and certainly not ran as admin. Clicking “Restart as standard user” results in a dialog loop.
The long standing iOS export bug on windows is still in 2022.3.0f1 LTS ( not that i expected different )
seriously guys, you should not let such essential issues slip through … XCode build error after upgrading to 2022.2.0 page-3
Because Unity likes to show off these things months before they’re ready. Releasing them at the same time as the LTS would make sense but they really struggle to synchronise things like that.
Also
There are features being added: Full Screen Master Nodes Fog Materials
And more
And these have no samples or even video about how they work or are supposed to be used?
That does not instill confidence about their actual production viability or testing
Really?!
Even the first image on the Unity 2022 LTS page is from the new sample. Later also the Zen garden. First get people excited and then say: “Please don’t touch”
