Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2021.2
2021.2.8f1
Issue ID
1400486
Regression
No
CRC values of AssetBundles are the same when HDRP Asset's Lit Shader Mode is changed and AssetBundles are built
How to reproduce:
1. Open the attached project "tests.zip"
2. Click Bundles>Build
3. Open <project-path>/AssetBundles/<platform>/tests.manifest
4. Take note of CRC value
5. In the Editor select Assets\HDRPDefaultResources\HDRenderPipelineAsset.asset
6. In the Inspector window change Lit Shader Mode to "Forward Only"
7. Repeat steps 2 to 4
Expected results: CRC values are different
Actual results: CRC values are the same
Reproducible with: 2021.2.13f1
Could not test with: 2019.4.36f1, 2020.3.30f1, 2022.1.0b9, 2022.2.0a5 (errors in the Console window)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.1.X):
What you are observing currently is due to the inability to express that a change in settings affects the behaviour of OnProcessShader resulting in build data change. Allowing to express this change of behaviour with our build callback system is something we have in our future roadmap but which cannot be easily introduced. The workaround would be to detect those changes and force clean the build.