Search Issue Tracker
Fixed
Won't Fix in 2022.1.X
Fixed in 2020.3.43f1, 2021.3.15f1, 2022.2.1f1
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.21f1
2022.2.0b13
Issue ID
UUM-18489
Regression
No
Unity builds not deterministic when using a different machine or a floating license
Zendesk: [1375743|https://unity3d.zendesk.com/agent/tickets/1375743]
Jira (previous): [LIT-1973|https://jira.unity3d.com/browse/LIT-1973]
Slack discussion [here|https://unity.slack.com/archives/CHT3UUH9D/p1655881286540529]
The customer reports that building the project results in project files being modified differently, depending on which machine it was built on (using floating licenses).
Resolved in this [PR|https://github.cds.internal.unity3d.com/unity/unity/pull/17220], which landed in this batch: [3a9dae98|https://evergreen.ds.unity3d.com/unity/trunk/batch/3a9dae98-3f88-4e50-af1b-b08da5c8b719] (on Nov 1st)
Probably fixed in [2023.1.0a18|https://saihai.hq.unity3d.com/build/1780].
We now need backports for this -bug- fix.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- The property of a component becomes read-only when it is bound to "PropertyStreamHandle"
- Physics.Raycast does not work when used on the whole model
- Shader Graph changes the Position of Prefab instances in Play mode
Resolution Note (2022.1.X):
2022.1 Cutoff