Search Issue Tracker
By Design
Votes
2
Found in
2022.3.17f1
2023.2.4f1
2023.3.0b1
Issue ID
UUM-59995
Regression
Yes
No warnings are thrown when RenderPipeline tag is incorrect
Reproduction steps:
1. Open the attached “PixelTestSimple1.zip“ project
2. Observe the Console
Expected result: Warning about incorrect RenderPipeline tag is thrown
Actual result: No warnings are thrown
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
Note: Couldn’t test with HDRP due to errors in the Console
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There's no such thing as "incorrect render pipeline tag". It's matching a string against another string. An empty string is used for Built-in Render Pipeline, any other string is a valid render pipeline identifier.