During my usage of 2019.3 (which is pretty much around the clock these days), me and my colleagues encountered a couple of bugs that I consider showstoppers but that I wasn’t able to reliable reproduce. These bugs happened on different machines, different projects, but all with the current beta.
(1) Serialization issues with AssetDatabase v2 and git
In two projects, we have an occassional issue where the same assets on two different machines have separate meta files (without touching these assets, at least knowingly). This causes all kinds of weird stuff to happen; e.g. whenever someone saves a scene and pushes it, the other person now has broken references in their scene, without a clear way to resolve, since the Library seems to have the wrong meta info while the files on disk use the right one. Rightclick > Reimport on those assets sometimes immediately solves the issue (and makes the Library be in sync with the meta on disk again).
(2) Shader keyword issues
In all projects on all machines, changing material options and this affecting the set shader keywords is random at best and downright wrong in some cases. This is happening a lot, but whenever I try to isolate it for a bug report it stops happening. When it happens it’s very clear what’s going wrong:
- create a new Material (e.g. Universal/Lit)
- assign it to a scene object
- add a normal map to it
- note that the material does not update, neither in scene view nor material preview
- click on the “Opaque/Transparent” dropdown and select either (even the same as was previously active)
- material now updates and properly shows normal map
- this happens for multiple different properties. Sometimes it only happens a single time per material, sometimes it happens on every change that internally should cause keywords to change (e.g. turning emissive on), and it can always be “worked around” by changing the material type and then changing it back.
Edit: I tried again and it seems in latest betas it is far easier to reproduce (happens all the time and even persists after Editor restarts and builds):
(Case 1197217) [Shader Keywords] Changing material options does not properly set shader keywords
Also note that I was able to even reproduce that in 2019.2 now.
(3) Prefab serialization issues after Unity upgrades
Upgrading throughout the Beta was painful. Every update broke a subset of our Prefabs, in a way that while a value was overriden in a scene it was not detected as an override, thus couldn’t be reverted, and such the value in scene and prefab where different with no way to resolve. Interestingly, this seems to be v2 Assetdatabase as well - deleting the scene file referencing the prefab from outside Unity, focussing into Unity, then going back to Explorer, undoing the delete and focussing Unity again forced Unity to actually read the file and everything was working again.
We had that on every beta update so far.
(4) Scene Selection issues
On multiple projects on the current Beta, at a random point while working (usually after entering and exiting playmode), selection in the scene stops working. One object is “stuck” being selected, and clicking on other objects does not change the selection.
This can only be fixed with an Editor restart.
(5) Scene Transform Gizmo issues
The usability of the Rotation Transform gizmo strongly regressed in the current beta, or at least it feels like that. 30% of the time, when you try to rotate on one of the axes, it will randomly select another one for rotation, even if the click is very visibly in the right place. A workaround is rotating the scene a lot and finding the right place, but that’s a workflow hell.
Video that shows the bug in action (watch carefully where the mouse cursor is and which rotation ring is highlighted):
I’ll update this as I remember more. This is just off the top of my head as it seems Unity is getting close to leaving beta state and then everyone will have those issues.
@LeonhardP would be awesome to get your input on this - is some of this known / being worked on?
