Remember to back up your projects before opening them in a new version of Unity. If you encounter any issues, please let us know by submitting a bug report so it can reach our developers.
If you have any questions related to 2020.1, please feel free to ask them in this thread and we will do our best to follow up on them. This thread will remain open for questions until August 21.
I would like to ask for a Mac native title bar option. in 2020 the title bar changes depending on the light or dark theme.
Iâm using the light theme and the title bars is now a different grey color that does not follow the OSX UI standard.
I can understand why it happened, but please make it optional. I prefer to have the light theme with OS native title bars ( in my case black )
There was an update to the Jobs system somehow between 2020.1.0b16 and 2020.1.0f1 which deprecated WithDeallocateOnJobCompletion. Now thereâs WithDisposeOnCompletion instead.
However, using it throws Invalid IL Code exceptions like this: InvalidProgramException: Invalid IL code in Somenamespace.Somesystem/Somenamespace.<>c__DisplayClass_SomeJobName:RunWithoutJobSystem (void*): IL_0000: ldarg.1
As soon as I just remove WithDisposeOnCompletion, the error is gone. The error itself points strait to the line where I define the âJob.WithCodeâ. In my case, what I want to dispose is just some EntityQuery.ToEntityArray with allocation type TempJob.
/edit: I know whatâs up: For some reason I had this in a job I used â.Run()â on which totally doesnât make sense. It works on scheduled jobs. However, this was working before but I guess this is a âfixâ then?
/edit2: This actually happened in another Entities Package update. The weird thing is that I was using 0.11preview4 all the time and the package managed didnât show me any newer versions. However the version introducing it was actually released just some days after 11p4? What⌠also the documentation url com.unity.entities@latest was pointing to 11p4 until 2020.1 was released. Confusing stuff.
Anyone else notice a pretty significant speed increase with 2020.1, at least as far as editor fps reporting is concerned? All the projects Iâve tested here have about a 10-20% boost. It seems particularly impactful on CPU processing, whereas the places where GPU was being challenged are still getting bogged down in a similar fashion in 2020.
I also noticed that setting the vSync count doesnât seem to have any effect. Frames are not getting locked to 30, or 60, they are just full on as fast as possible.
We tried to update our project to 2020.1.0f1 but we get âThe type or namespace name âTMProâ could not be found (are you missing a using directive or an assembly reference?â.
Thanks I didnât know about either of those new options. I still think vsync is bugged. Turning it on sets frames closer to 60, but not exact, and setting every other blank doesnât seem to do anything. The debug doesnât seem to affect performance (at least in my single test scene), but Iâm happy to see any kind of performance boost in the editor.
In this Editor Version there are missing packages not shown in the Package Explorer.
Like for âUnity Physicsâ in my case. I even have it installed now but its still filtered out in the Registry view.
This would block users to locate and install it via Package Manager.
I had it uninstalled and could not find it. Its installed as a dependency to Havok physics now in my case.
I think this is not intentional !?
