Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.0b16, 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
- Development build hangs when spamming Debug.Log messages to the Console and Autoconnect Profiler is enabled
- Cannot attach or debug the Player when using Rider IDE
- Fields in "Scene Template Pipeline" section look messy
- Can't import asset via Package Manager when it consists of sub-packages and one of them is already imported
- CubemapArrays and Cubemaps take up significantly more memory than on other platforms when working with a Windows project
Resolution Note (fix version 2023.1.0a19):
https://github.cds.internal.unity3d.com/unity/unity/pull/14905