Share your Unity 2019.1.0f2 experience .....

Hello everybody,

I just created this thread with a correct title according this post : https://forum.unity.com/threads/unity-2019-reuined-my-game.670804/

Please share your experience !

For me, the Unity 2019.1.0f2 is completely broken !

First, if you do not have tried it, be ready to lose a complete day for fixing script errors , prefab problems, models problems ect ...

This is 3 bug's already reported before the official release, but they have released the version without fixing them !

UI broken when you assign a sprite by script :
https://forum.unity.com/threads/sizedelta-broken-on-unity-2019-1-0f2.663268/
Reported the 3 April !!!!!!!!!!!!! Too late????

PlayerPrefs not working in WebGL :
https://forum.unity.com/threads/playerprefs-in-2019-1.665254/
Reported the 26 March !!!!!!!!!!!!!!!!!!! Are you serious???

The best one :
Inspector input field is broken :
https://forum.unity.com/threads/edi...field-is-broken-with-unity-2019-1-0f2.665479/
How you can release it with a bug like this?????? really ??????

You can't do anything just because of the Inspector input field bug ..... just browse here and see how much problems everybody have with this version of Unity : https://forum.unity.com/forums/editor-general-support.10/ it's incredible ....

I have see a lot of bug's other than the bug's listed above but i will not fill any report anymore.
We lose our time for them and for nothing.
You can see on all post that they ask for bug report but they make official release without fixing them.

Free for you to share your Unity 2019.1.0f2 experience ..... maybe someone can show me that i'm wrong ...

Have a good day !

 

I didn't have a single script break from latest 2018 to 2019. Though it feels very unstable. Editor is slow. Also for some reason materials change from solid cyan colour to their real material when moving camera in play or eiftor mode (haven't tried stand alone)

 

That's a feature and was stated in the blog post. Shaders are compiled in background now and the cyan is the placeholder color.

 

Thank you for pointing out this.

 

I only ever take a look at new 20XX.1.0 releases out of curiosity regarding new features. I never use them to get any serious work done. I start looking at them for actual project work around 20XX.1.3 once the most obvious bugs have been shaken out.

 

2019f1 gave me numerous package errors etc each time I opened it. I eventually figured out after numerous other people posted the same issue how to fix it, but realised then it came back each time I opened the editor.

I noped back to 2018 very quickly. I'm not confident in Unity releasing new software at the moment.

 

I've created my project when 2019.1 was alpha (just released), there were things went broke and things needed to wait for, but overall, it wasn't a bumpy ride. My project is working properly, maybe I'm lucky I don't use things which easily break? I don't know. And also my project is not too big yet (<1GB), I guess will see when it grows.
Overall, I'm happy with 2019.1, with HDRP and ECS/Job System things. It was easier ride so far than I anticipated.

 

I was using 2019.1, but after coming across two crucial bugs, I has decided to downgrade my project to 2018.4, one is the image color not changing through script thing, the other is IAP being broken when the installation path of Unity contains space, both have been confirmed by Unity staff. However, there are still some issues in 2018.4, for example, the grey list warnings in the pre-launch report of Google Play Console, which would cause errors on some devices. Unity staff has identified this issue and has been contacting Google about these warnings since last week.