Search Issue Tracker
Fixed in 2021.3.17f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a19
Votes
0
Found in
2021.3.9f1
2022.1.15f1
2022.2.0a18
2023.1.0a3
Issue ID
UUM-8358
Regression
No
Nodes using derivatives are not stripped out in Raytracing, even when using the Raytracing Quality keyword
Repro:
- Open scene in attached project
- Look at the rendering in game view
Actual:
!image-2022-07-08-11-36-08-320.png!
Expected:
!image-2022-07-08-11-35-59-727.png!
Notes:
- Screenshot of the shadergraph:
!image-2022-07-08-11-37-41-618.png|width=968,height=434!
- Affected nodes that I've found: DDX, DDY, DDXY, NormalFromHeight
- Especially frustrating as the compilation error says to use the Raytracing Quality keyword to avoid this issue :/
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2023.1):
https://github.cds.internal.unity3d.com/unity/unity/pull/14905