Search Issue Tracker
Fixed in 2020.3.43f1
Won't Fix in 2022.1.X
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 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
Jira (previous): LIT-1973
Slack discussion here
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, which landed in this batch: 3a9dae98 (on Nov 1st)
Probably fixed in 2023.1.0a18.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2022.1.X):
2022.1 Cutoff