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
- [Android] [iOS] [UnityWebRequest] Requests with "UnityWebRequest" are open for SSL Proxying
- SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
- Crash on GetEffectiveBc7TextureCompressor() when loading and unloading all Assets in the Project
- Terrain Masks do not ignore the mipmap limit
- "Build And Run" the project for Web is allowed even though the directory for the non-default browser is not selected
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.