Question When can we get a LTS version of Unity 2022?

I am working on UGS on Unity2022.
But I have got a warning like this:

"Warning: There's a known issue with Unity Editor version 2022 that prevents the SDK from working. If you use version 2022, ensure you use version 2022.2.3f1 or later."

And I have a bad experience of working with non LTS version in production.
So I want to use LTS version of Unity 2022.

Could you let me know when I can use LTS version of Unity 2022?

 

"Unity download archive"
https://unity.com/releases/editor/archive

However, it appears that currently 2022 is not LTS.
You can download LTS versions here:
https://unity.com/releases/editor/qa/lts-releases?major_version=&minor_version=&version=&page=0

 

Thank you but I don't ask you where: I just want to know When?!

 

Apologies. I misread your question.

Unfortunately, I have no reliable information about planned LTS release schedule.

 

There's this handy site: https://endoflife.date/unity

Unity keeps roughly a 1-year cycle and 2021 LTS came out 22 march last year. So I'd expect 2022 "rather soon".

 

Current tech release is 2022.2.12 i think. So when LTS comes out and it’s versioned 2022.3.0 LTS what you actually get is 2022.2.13.

So by all means go with the 2022.2 tech stream. It only makes a difference if it’s a 20xx.1 tech stream, the more earlier in the year the less stable. Likewise, an LTS version requires several updates to be as stable as last year’s 20xx.3.30+ is.

It’s all relative, there is no clear divider between tech and LTS. LTS aren’t automatically far more “stable” (whatever that may mean) than a former tech release.

 

Thank you @DragonCoder and @CodeSmile
I have one question further.
@CodeSmile, Which version is more stable in Unity 2022.2.x according your experience?
2022.2.2 gave us tons of crash in production release on Google Play Console.
So I want to use more stable version in Unity2022.2.x.

 

You'd have to test that yourself. I would always use the latest tech stream version. If that has issues that appear in your workflow and on your platform, it makes little sense wasting time trying different versions of the same tech stream (ie between 2022.2.2+ and below the latest 2022.2).

You could try the 2023.1 beta just to see if that particular issue persists, because if it does, you're almost guaranteed to experience it in any version between 2022.2 where you had that issue and the 2023.1 beta. But again, first try the latest 2022.2.

If you have a reproducible crash issue that appears in 2022.2.2 then you can and should check each 2022.2.3+ changelog in the FIXES section for anything related to that particular issue or crashes. You only have to scan for Android/Mobile keywords and read over the fixes and see if that may relate to your issue. If there's nothing under FIXES in those changelogs even close to the issue you experience, then it's very unlikely that the issue has been fixed.

Still, like I said above, I would just update to the latest tech stream and give it a try just to be sure the issue just went away. It would be fatal to test only with 2022.2, notice crashes, and then shy away from any further attempts at upgrading because "2022.2 is unstable". That is not how software in general works, or how developers are supposed to think about versions.

Also, there's one other thing to consider: crashes may not be related to the Unity version directly. It may be caused by an updated Android SDK version that the new Unity version uses (often: "has to use" in order to support latest devices) that 3rd party code (or even yours) isn't compatible with and causes these crashes.

Or a build/player setting that used to default to "On" but now defaults to "Off" because it is known to cause some issues, but since you work with an existing project that flag may still be "On" and you just ran into that particular issue. So it often helps to check over Player settings once again when doing a major Unity version upgrade and experiencing issues. Ideally reset all player (among other) settings to defaults, and focus on the ones that may be related to the crashes. Ie if the crash is with something like rendering according to callstacks then I would reset all graphics and quality settings to defaults as well and test the build.

It is similar to the best practice of resetting BIOS settings to defaults after applying a BIOS update and ensuring the system runs stable. If that is the case, you can then go back into BIOS and change the settings away from defaults as needed.

 

While there's nothing wrong with the question, do keep in mind that mileage will vary from project to project.

Unity is huge and different projects and teams use different parts of it. So even if it's crashing daily for one team, the exact same version may work perfectly for another team who just isn't using the same parts of the engine in the same way to cause the crashes. Same deal goes for any other bug.

 

It's dependent on the packages you use too. Some packages are tied directly to specific releases of Unity. A more stable release of the engine might require you to accept a bug in one of your packages and vice versa. Currently Unity 2021.3 has been very stable but I'm encountering minor bugs with the input system which is stuck at 1.4.4.

 

When can we get a stable, performant, optimised and efficient version of 2022?

 

Probably when it hits LTS, which it hasn't.

So if you wanted stable, probably shoulda stuck to 2021 LTS.

 

I want performant and optimised, first and foremost, which is why I'm using a MUCH older version of Unity.

 

Good luck with those requirements.

 

For reference, here the release dates of all previous LTS versions:

Code (LTS):

1. 2017.4 2018/04/24 LTS
2. 2018.4 2019/05/10 LTS
3. 2019.4 2020/06/09 LTS
4. 2020.3 2021/03/11 LTS
5. 2021.3 2022/04/12 LTS

So the answer is somewhere between "any day now" to "within the next few months"...

 

It will release May 31st at 11:59pm

 

There’s this - https://create.unity.com/2022-lts-interest-sign-up
“Mark your calendars!” Yeah but for what date

 

Just want to remind everyone that early LTS versions aren't really that different (if at all) from late TECH releases. So barring some miracle happening, if the current 2022 TECH release doesn't do it for you, LTS won't do it either, at least for many more months.

 

Before 23.59pm on December 31st 2023 (Maybe)

 

You know, 23:59PM means it is gonna be 35:59, of December 31st, 24 hours format.

And somehow it feels like it might actually be the planned release time.

/joke

 

You can see this too if you look at the Unity 2021.3.0 release notes. It had all of one bug fix.

https://unity.com/releases/editor/whats-new/2021.3.0

 

https://blog.unity.com/engine-platform/unity-2022-lts-is-coming-in-june

 

Unity 2022.3 LTS has been released already!

 

No release notes yet, although I doubt much has changed since the last 2022.2 and I also doubt the showstopper (for us) bug that I submitted 4-5 months ago has been fixed.

 

TIL that they look at the current date from New Zealand.

 

Unity just released 2022.3.0 LTS. Expecting much stability. Checking out.

 

I tried it. The showstopper bug with custom post and stacked cameras is still there, there are numerous pop-ups for shader compilation during play mode that are very distracting (and the editor setting to suppress pop-ups isn't there on a Mac), and the editor froze and had to be force quit within 60 seconds.

Overall, good release.

 

Is it just me or is this version not available in the Hub?
I was able to manually download it but also need to manually install all the platform modules.

 

Erm... checking sarcasm detector. I mean hopefully they fixed the bug I reported back in 2019 LTS finally...

 

This one too https://issuetracker.unity3d.com/is...ine-warning-is-thrown-when-creating-a-new-vfx

under consideration??

 

Make sure you look under "Long Term Support" at the top of available versions and not at the bottom where the newest versions usually are.

Latest build was far more stable, hoping this one is even better.

 

Thanks I got it now, I had to update my Unity Hub version to get it to show up.