Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.2f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130256
Regression
No
Installing HDRP package throws Shader Graph validation warning about Exposure node when installed in Universal 3D Template
Steps to reproduce:
1. Create new Unity project using Universal 3D Template
2. Open Package Manager
3. Find High Definition Render Pipeline package
4. Install High Definition Render Pipeline package
5. Once installed, observe Console window
Actual results: “Shader Graph at Packages/com.unity.render-pipelines.high-definition/Runtime/Tools/ColorChecker/ColorCheckerShader.shadergraph has 2 warning(s), the first is: Validation: Exposure Node is not allowed by Universal implementation” warning is thrown in the Console window
Expected results: No warnings are thrown in the Console window
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b1, 6000.5.0a3
Tested on (OS): Ubuntu 24.04, macOS Tahoe 26.1 (M1)
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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note:
Sadly, we don't want to invest in making HDRP stuff works on URP and not generating warning so there's absolutely no solution on that as we can't "branch" shader graph value for nodes that are not supported in the other pipelines.
Resolution Note (6000.5.X):
Sadly, we don't want to invest in making HDRP stuff works on URP and not generating warning so there's absolutely no solution on that as we can't "branch" shader graph value for nodes that are not supported in the other pipelines.