Bug 2020.3.8 (L T S) Is completely broken

I don't know where to start.
When I am selecting any texture in the editor I get:

and texture preview not showing.

Any selected material looks like this (with variations) in the preview:


Editor crashes on closing.
Prefabs loose their overrides when CTRL+C and CTRL+V them in the hierarchy (while CTRL+D works fine).
Editor sometimes stuck on opening.

It is only a fraction of all problems I have in 2020.3 version.
2020.2 and and especially 2020.1 were much much stable and production ready.

Every time someone will tell you to use only LTS versions of Unity, because THEY ARE STABLE tell them they can go screw.

I am sorry, but this is impossible.
Any good company would have fired the whole QA department after this. And stopped any further development until developers will learn to do simple local verification.

The saddest thing is that I see some of this bugs in the tracker. For example bug with exceptions on selecting texture is there from February 25. For some reason UT fixes bugs for TECH stream first (that should not be usable in the production). And after a half of the year we will finally see the fixes propagate to the STABLE and PRODUCTION READY version.

It
is
so
frustrating.

 

Random UI / UIElements errors when using Unity are part of the norm these days, but they usually don't cause issues as big as what you're describing.

Have you restarted editor?

Deleted library and reimported everything?

 

Yes I restarted editor several times. As I sad I see some bugs in the tracker already, so it is not a local problem.

Unfortunately, deleting the Library folder on any real project is never an option because reimporting will take a day or so and most likely will crash in the middle.

 

Using Unity and not regularly deleting the Library is not an option because Unity tends to F*** things up regularly with its library.

These days I do it once a week over the weekend, or so.

 

https://issuetracker.unity3d.com/is...-texture-inspector-is-overwritten-in-c-number

So the issue was reported on February 25
Today is May 28
3 months have passed and we still have a showstopper in production-ready and stable version of Unity.
Just great.

 

I would say "welcome to Unity" but your account is pretty old.

 

About the errors in your first screenshot, just remove the substance plugin.

 

5 months have passed. Still no fix for the LTS version.

 

Yet another example of bug that was fixed in the TECH stream, but not in the STABLE version: https://issuetracker.unity3d.com/is...uses-invalidoperationexception-on-nativearray

 

It already says "Planned for 2020.3.x". How bug fixes usually work is they are fixed in the latest/greatest branch first, and after they are fixed there, they get backported to older branches. Backporting takes extra time, but it makes no sense to hold off on releasing for 2021.2.x until they had finished the backport to these other branches.

 

It is planned for almost a half of year.
As for this process, it should be reversed. I worked in several software companies, and fixes were always made for the users, not for beta branches. TECH stream and beta branches are used by far less users than stable versions. Unity always told us to use STABLE versions because they are more stable, than TECH. But it is not true if the blockers not fixed for year and more.