I don’t think there’s need to roll back, since probably no files changed outside the Library in the upgrade process (apart from the unity version txt).
Do a Library delete or Reimport All (these are similar), then, once it is done, close Unity without pressing play, then open it again.
I reported a bug with unity 2021.2.10 which still persists in the new LTS-Version ([Worker0] Tried select unknown importer for id ‘-2’ ‘00000000000000000000000000000000’).
The bug report is still open should I create another bug report in the new version or should I just wait?
Did you get a case id and a confirmation from QA that they can recreate the bug for the previous bug report?
So far I did only receive the automatic confirmation mail with the case number, but no confirmation from the QA yet.
We’re getting off topic. If it has been more than 3-4 weeks, it could be worth submitting a bug report again. If it’s less than that, I’d wait.
Using Reimport All has fixed the problem. The game runs in play mode now, and seems to be just the same as before the update. Thanks for the help.
If that happens again, right click on Unity.exe in task manager, press “Create dump file”, compress it to 7z/zip and send it to me. I will be able to look at it and see what’s going on. Make sure to capture the main Unity.exe (one that is started with -projectpath argument). If you are not sure which one it is, you can capture all of them.
It seems that 2021.3.0f1 release note is almost empty. So does it mean that 2021.3.0 is almost same to 2021.2.19?
Yes.
When I was on the release note page yesterday there was more on it.
Not having a smooth upgrade here: upgrading from 2020LTS to 2021LTS has made my Android project hang on loading without throwing any error in the android logcat or anything. It just hangs in there, loading forever.
It runs perfectly in editor on 2021LTS, but the built apk just hangs on load.
Of course, the build was working great on 2020LTS.
I have just deleted the library folder to force a full rebuild of the project. Let’s see if that fixes it…
-edit: deleting the library folder inside the project folder fixed all issues.
I understand Unity’s support timeline for 2020 LTS, and that they will be supporting it with monthly updates until mid-2023. But I would be interested to know what experienced users of Unity recommend regarding this release?
I am quite new to Unity so I am not sure whether I should just jump to 2021 LTS now that it is out. I’ve been working on my first game in 2020 LTS for over a year, using the standard render pipeline and no need for things like Shader Graph. Do you guys think I should just stay with 2020 LTS? I don’t want to unnecessarily risk things breaking for no real gains.
I’m also not sure how this synchronises with device/OS releases. For example when iOS 16 drops in September, I am assuming my game made in 2020 LTS will still run? Though I would assume 2021 LTS might get specific features targeted to exploit newer OS capabilities that the older 2020 LTS won’t get. Any recommendations from experienced users (or Unity) would be really appreciated!
Thanks, I will do.
Indeed, this fixed it.
Hey @Tautvydas-Zilys , maybe you should just automatically delete the library folder when upgrading a project from an LTS version to the next. I have needed to do that every time I switched LTS versions or jumped from yearly unity versions for the project to work. It’s an hassle to rebuild everything, but the project gets reimported anyway and takes 80% of the time it would take for a full rebuild.
Also, now my game runs in a jerking motion compared to 2020LTS. I’m not sure why it does that and I’ll have to check it out.
edit: the jerkiness was because of manually updating the physics engine. Using fixed update is fine.
You’re up for a ROUGH upgrade.
2021LTS is supposed to be faster both in editor and in build.
If I were you, I would make a copy of the whole project folder (except for the “library” folder, that will be reconstructed anyway) and upgrade that new project folder to 2021LTS.
Then you will know if it upgrades correctly, if it goes faster, etc…
And if it’s a nightmare to upgrade and it doesn’t work, just delete the new project folder and stay in 2020LTS with the old folder.
For one thing, I can already tell that the editor is WAY faster than 2020LTS for everything, but specially entering Play Mode, which is VERY MUCH APPRECIATED GUYS! THANKS!
Also, compiling for Android is MUCH faster now.
And reimporting my assets (ASTC textures) is also much faster.
Just so that you know that your work is VERY MUCH APPRECIATED and doesn’t go unnoticed!
I’m glad I upgraded! 
edit: Seriously, it feels SO GOOD to be able to iterate my build so quickly! :):)
Edit: LOL NO, It seems I have been over enthusiastic: [the editor keeps crashing at me]( Unity 2021 LTS Is Now Available page-2#post-8052380)…
Hello guys,
Thank you for the release!
I’m curious about why you didn’t update the Emscripten?
It is more than one year behind the current version.
Thank you
Oh… BUMMER…
Compute Shaders are not working correctly on Built-in, both in editor and in build… They were working before the upgrade… now I’ll have to dig in and check what’s happening, but there are no errors anywhere.
Also, there is still that jerkiness in motion that wasn’t there before and I can’t get rid of it. (it’s not the GC)
edit: the jerkiness was because of manually updating the physics engine. Using fixed update is fine.
Ok, I got it to work, but no amount of reimports of the compute shaders would fix it, instead, I had to go inside the compute shader, put a [space] character in there inside the kernel code, save it, and now the compute shader has been willing to recompile.
So, something is wrong with compute shaders caching.
The jerkiness is still there in build, though, and it wasn’t there before…
edit: the jerkiness was because of manually updating the physics engine. Using fixed update is fine.
Has anyone found that even with a empty project the power useage is “very high” in task manager, CPU is 14.5% and GPU 41.8% and yes I have set target frame rate to 60
It was the same with the 2020 version but with 2019.4.17 I have moderate power usage ( 3.6 % CPU and 7% GPU)
Has anyone tried building with il2cpp set to master instead of release? 2021.2.* with il2cpp set to master caused endless building for Android.