Search Issue Tracker
By Design
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
Votes
0
Found in
2020.3.32f1
2021.3.5f1
2022.1.0b13
2022.2.0a9
Issue ID
UUM-1042
Regression
No
Shader is not set correctly when using Custom Render Pipeline Asset
How to reproduce:
1. Open users attached project
2. Navigate to Assets > __Dev > Matt > Environment > test_asset_master > Models
3. Expand the TextureTest.fbx asset and select temp_asset_03 (material)
4. Observe selected Shader
Expected result: Shader is set to Vonnegut/Lit
Actual result: Shader is set to Standard
Reproducible with: 2019.4.36f1, 2020.3.32f1, 2021.2.16f1, 2022.1.0b13, 2022.2.0a9
Note: Shader should be set to Vonnegut/Lit because the project uses Custom Render Pipeline Asset that has Default Shader set to Vonnegut/Lit
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
- Texture Map Viewer shows "Loading..." text instead of indicating users that Baked Texture Maps are missing
- "Analyze Import Process" button misaligned in Import Activity window
- Text in “Baked Shadowmask” mode is difficult to read in Baked Lightmap Viewer when Editor theme is set to Light
- Mesh wireframe is difficult to see in Baked Lightmap Viewer window when texture opacity is maximized
- Informational text does not wrap and does not fit when the Viewer Window is opened by default
Resolution Note:
URP and HDRP are changing their shader because they have custom implementation of AssetPostprocessor.OnPreprocessMaterialDescription that tests for the active render pipeline and change the shader to their default, along with the required properties on each material.
When using a custom render pipeline, we're expecting this pipeline to do the same and implement its own postprocessor to set the correct shader and properties on each created material during a model import.