-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cornell Box scene dark & RenderDoc launch fails at Dx12 ray tracing feature tier 1.1 not supported #4
Comments
RenderDoc doesn't support DXR, so it can't be used for debugging here. I mainly used PIX and Nsight Graphics. Make sure the debug layer is disabled (ZetaCore/Core/Device.cpp, line 11) as it can sometimes cause problems with these tools. |
Glad it's working! Here's something else to try: In the debug window, go to Settings -> Parameters -> Display -> Final Render—there, you can view various intermediate results (such as G-Buffers, raytraced lighting, etc). This should help you narrow down your search to identify the source of the problem. Let me know if you figure out what's causing the issue on the RTX 2080 super system, I'm definitely curious! |
Hi,
I was running this project with latest commit 3c57d8166f7044eef7b151797508892714fab1ee
1,
But I found that the already preprocessed gltf cornell box scene mentioned in the README fails to render with complete darkness
2,
So I was trying to debug this scene with RenderDoc v1.28 (latest stable release), but when launching from renderdoc, I got this
Triggerd by this line of code
ZetaRay/ZetaCore/Core/Device.cpp
Line 97 in 3c57d81
I tried to change it to,
and it still fails with renderdoc but pass the ordinary launch. I guess it is a problem regard to renderdoc not supporting dx12 raytracing? But I cannot find any solutions online.
I wonder what tools you used to debug shader in this case. I am pretty sure it is problem with ray tracing shaders but I am not sure where to start at this embarrassing moment.
My rig is RTX2080super desktop.
Thanks!
The text was updated successfully, but these errors were encountered: