Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
1
Found in
2020.3.36f1
2021.3.5f1
2022.1.7f1
2022.2.0a18
2023.1.0a1
Issue ID
UUM-6762
Regression
No
Deterministic builds have different files when built from the same project
How to reproduce:
1. Open the user’s attached “DeterministicBuilds” project
2. Create a copy of the project
3. Build the project
4. Open the copy project
5. Build the copy project
6. Compare the files of both builds (by using WinMerge or a similar application)
Expected result: All files are identical
Actual result: Some files are different, e.g., GameAssembly.dll or Data/globalgamemanagers
Reproducible with: 2020.3.36f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a18, 2023.1.0a1
Reproducible on: Windows 10
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:
Our compiler uses absolute file paths, so it is expected that if they are in different folders it produces different results.
If you destroy the Library folder, and the project stays in the same place, it will produce the exact 2 builds, and that would be the purpose of this setting
Resolution Note (2023.1.X):
Our compiler uses absolute file paths, so it is expected that if they are in different folders it produces different results.
If you destroy the Library folder, and the project stays in the same place, it will produce the exact 2 builds, and that would be the purpose of this setting