I was working in a 2D Game for 6 months in Unity 2018.2. My coworker discovered new animation features in Unity 2019 and migrate our game to this version. I works perfectly on his Asus computer running windows 10.
My Dell computer running Windows 10 (i7 7th, NVIDIA GTX1050Ti) , cannot play the game in Unity Editor 2019.2 no longer. It opens the project. Executes the first two scenes (very simple splash scene), on the load of a 3rd scene, Unity Editor hangs. All code lines are executed but when loading the 2nd scene Editor hangs. I have to end the process using Windows task manager. I made dozens of tests, using 3 more different Dell Computers and Windows 10 64bit ? Same behaviour in all 4 Dell Computers, desktops and laptops having very different hardware. Observing carefully I found that the same problem happens in Unity 2018 also, if Graphics Emulation is disabled. I have been using (DX11 on DX10) or (DX11 on DX9) on Unity 2018.2. Since Graphics Emulation was disabled in Unity 2019 editor, the problem apperared.
It’s very strange, testing DirectX (dxdiag) on all Dell computers they support DirectX12, so Graphics Emulation should not be needed. I tried to configure many other Graphic API for Windows (Direct3D11, Direct3D12, Vulkan, OpenGLCore, OpenGLES2, OpenGLES3) same behavior and hang, only in Dell Computers. I cannot use Unity Editor 2019.
Do you have the latest graphics drivers installed?
Absolutely. I even reinstalled completely windows 10 and latest drivers.
I have to install a windows 10 development enviroment on a Virtual machine in order to keep working. But performance is awful.
i haven’t had any issues on dell machines,
just tested disabling graphics emulation also (and loaded few scenes back and forth)…
Problem Solved.
Actually my code was reading saved objects position from a JSON service. Since Unity 2019 was installed, and graphics emulation disable, string parsing function AsFloat changed the way it performs string to float conversion. It now considers CultureInfo. It used to read a float considering default english number format (dot as decimal), but it now considers comma, my windows environment CultureInfo. Then a saved number 4.999999999999 was read as 4.9 E12 a giant number, and unity hangs when drawing such object in a far, far away coordinate.
Using graphics emulation (possible in Unity Editor 2018 only) Asfloat function parses numbers format considering default English number ??!! This should be a fixed C# behavior and not change depending on Unity Editor version/configuration.
The misleading clue: all Dell computers had the same windows environment cultureInfo, other computers don´t, so It seamed to be the hardware issue.
Since I had dozens of objects in the scene, and only one object got a wrong coordinate, I did not notice the problem, until I got deep in debugging details. That was painstaking, since every try I got Unity Editor hanged, have to kill the process and restart all over again.
Sharing info here if anyone else has the same problem. Float conversion changes its behavior in Unity 2019.