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

Add comment

Log in to post comment