Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.10f1
6000.4.0b8
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135524
Regression
Yes
Shader breaks and throws an invalid GBufferFragOutput to FragmentOutput type cast error after switching Render Path to Deferred
Steps to reproduce:
- Open the attached project
- Open the Sample Scene
- Observe how the bush object is rendered, as well as the errors thrown in the console window
Actual results: Shader throws a type conversion error and does not compile
Expected results: Shader compiles and visuals match compared to when using forward rendering
Reproducible with versions: 6000.2.0b1, 6000.3.10f1, 6000.4.0b8, 6000.5.0a8
Not reproducible with versions: 6000.0.68f1, 6000.2.0a10
Tested on (OS): macOS 26.3, Windows 11
Notes:
- The issue only occurs when using Deferred/Deferred+ rendering paths
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:
Hello.
It is correct that this is a problem, but unfortunately we are not able to fix this. Even if it was possible to do so, we cannot back-port changes to deprecated functions, as it might break shaders for users who have already fixed the issue themselves.
Resolution Note (6000.6.X):
Hello.
It is correct that this is a problem, but unfortunately we are not able to fix this. Even if it was possible to do so, we cannot back-port changes to deprecated functions, as it might break shaders for users who have already fixed the issue themselves.