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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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.