2019.1.3 - Most unstable bugged release yet.

Its basically made any progress come to a stand still.

-Lights randomly lose their direction and bounding gizmos.
-Attempting to open Lighting settings causes continual crashes
-Objects in scenes randomly have position, rotation data change for no reason
-many un-reproduceable errors logged in console, stemming from internal unity issues.

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.InspectorWindow.ShouldCullEditor (UnityEditor.Editor[ ] editors, System.Int32 editorIndex) (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorWindow.cs:1528)

image here…
https://drive.google.com/open?id=1cMXYbV5p72WeFD1h_KgfbaQyYvdCuHaV

-and new issues popping up every time i glance another direction.

I really dunno what to say here. This version is absolutely one of the worst i’ve used. It has definitely crippled progress. Nah, i wont bother filing a bug report, as there’s not just one, there’s many. And, i’ve seen the feedback around reporting bugs and getting resolve. not promising.

Unity is an awsome tool, but this version is terrible. Please patch.

Pic of useless lights…
https://drive.google.com/open?id=1w_1Np_R82obFUlPdGLffVVhHQhPqu-TK
No direction display makes for a pretty useless light.

And here’s what happens about 19 out of 20 times attempting to open the Lighting Settings Window…
https://drive.google.com/open?id=1MUsEskt822skHlGwHDq1xcUBnoxQmpIH

The worst part about all this, there’s no where to go now. Cant go back to a previous unity version, cant go forward in production, as too much crap is broke. (Well , ok… i CAN go back… luckily, sigh.)

Regarding filing bug reports… I just read another recently posted thread about filing bug reports being bugged. Lol :frowning:

You right.

You will see some guys without real project and/or game release telling you that 2019.x is the best and have no problem but i have a real project and i can tell you that 2019.x is not usable in production yet.

I have started a topic already about this stupid situation here Share your Unity 2019.1.0f2 experience .....

In all cases, you do not get any answer from Unity staff and like everybody is scared to move on 2019.x we are only few guy telling the truth.

This bug ( In 2019.1, changes to Image.color are not displayed after changing its sprite via C# ) will be fixed in Unity 2019.3 and in theory released in December 2019 Funny no? not for me …

I don’t really have a horse in this race because while I am using 2019.1.3f, I’m currently using it as an uber novice and probably not even using a fraction of the functionality, and so far it works fine.

But from a general perspective, did you guys have a particular reason to upgrade in the first place? Was a particular bug from a previous version fixed? A required feature added?

I’m not exactly a sticker for “it ain’t broke so don’t fix it” as I generally believe that an effort should be made to keep software up to date, though with something as significant as Unity which is being used in production, some more due diligence is probably required before upgrading to the latest version.

It takes more effort to have a testing environment for such things, but in the long run, maybe less time consuming and less problematic if you aren’t fighting against new bugs on live projects.

This is wise for many software applications btw, not just Unity. Though arguably even more crucial with Unity as it has so many moving parts and variables that could break something between versions.

I would agree with you. But to answer your question, yes. There was indeed many bugs in previous versions that were *supposedly addressed and fixed in current versions. Thus the need to upgrade. But this new version is proving absolutely problematic.

Cheers mate.

1 Like

Fair enough, that’s frustrating and I have experienced similar issues with other software.

Though it’s astonishing to me in some cases how quickly some people are willing to adopt new versions, even sometimes major versions or beta versions in production environments.

Not always the best move but definitely when you’re waiting for existing stuff to be fixed, and in actuality, things are just getting worse, I can definitely understand the frustration.

I don’t get it. Isn’t it wise to use the LTS release for production projects?

Correct you would be. And part of this is on me for not creating backups along the way, but the initial LTS version i was using actually had a known bug with android and InputFields. I chased version after version looking for fixes to that issue, with no luck.

Luckily, my project is not littered with scenes, crafted and tuned over long periods of time. Opposedly, the entire game is generated at runtime. Ultimately, the only thing i have to do is start a new older version and drop my code in the project. Mostly good to go, barring a few layer entries and a bit of prefab setup. (Well, a few hours worth of prefab setup)

That said, it does not change my point of view, that this version seems like it shouldn’t have been released at all, as it throws errors just for opening the editor. (exaggerating for point),

Anyways, you are correct in your general assessment. Cheers.

I need to move forward because in my case , i need the Multithreading with WebGL in order to give the best experience for my players, so i have to be ready.

I understand your point of view and i agree but sometime we have to upgrade in order to use some new features.

The real problem, it’s that most of the bugs that we complain about has been reported before the official release and some of them will be fixed in December (according the release date of 2017.3).

( Share your Unity 2019.1.0f2 experience ..... ) will give you an idea.