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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.