Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b2
2020.1.0a7
Issue ID
1186833
Regression
No
[DXR] Changing an include file used by a raytrace shader doesn't trigger a reimport of the raytrace shader.
Changing an include file used by a raytrace shaders doesn't trigger a reimport of the raytrace shader.
How to reproduce:
1) Have a ray tracing ready system - Nvidia RTX GPU (latest graphics drivers) and Windows 10 version 1809+.
2) Open attached project - RaytraceIncludeBug.zip.
3) Open scene SampleScene.
4) Change to GameView and notice the screen is yellow. This is the output of the raytrace shader RayTracingTest.raytrace. The color is hardcoded in the include file TestIncludeFile.hlsl - GetColor function.
5) Change the color returned by GetColor function to another color, save the file and return to the Editor. The screen color in GameView should change to the new color.
Actual result:
The raytrace shader is not reimported automatically (the screen in GameView is still yellow).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment