Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.55f1
6000.1.16f1
6000.2.1f1
6000.3.0a5
6000.4.0a1
Issue ID
UUM-114616
Regression
No
Shader asset bundles differ depending on whether they are built with a clean library or not
Reproduction steps:
1. Extract the attached “IN-112307_ShaderBuildTest_Alpha“ project
2. Delete the “Library“ folder inside the project
3. Open the project
4. Select “Tools > Build” in the Menu Bar
5. Build to a new folder (suggest calling it 'A')
6. Close the project
7. Delete the “Library/ShaderCache” folder inside the project
8. Select “Tools > Build” in the Menu Bar
9. Build to a new folder (suggest calling it 'B')
10. Diff the shaders bundle for each build (“<BuildFolder>/AssetBundles/”)
Expected result: The built shader bundles are identical
Actual result: Diff returns that the built shader bundles are not identical
Reproducible with: 6000.0.55f1, 6000.1.16f1, 6000.2.1f1, 6000.3.0a5
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
Note: It appears that there might be two 'states' of the bundle, one of them if the project is built with a 'fresh' Library, and another if the Library is not 'fresh'. Deleting the whole Library between builds results in the same bundle, and deleting just the ShaderCache results in a different one
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment