-
Notifications
You must be signed in to change notification settings - Fork 437
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
[Question] How to use renderdoc with vulkano for debugging? #924
Comments
RenderDoc on Windows just works, and it's supposed to be the same on Linux. It's not impossible that there is a problem in RenderDoc. |
RenderDoc doesn't automatically support all vulkan extensions, only a certain subset, and for device extensions they are filtered automatically to only the supported list. Up until recently RenderDoc had no ability to filter out instance extensions due to how the loader worked (it returned the full list, regardless of whether RenderDoc would then support all of them). As a half-way compromise, if the application tried to create an instance with an unsupported extension I print an error message and return So my best guess is you're using an instance extension that isn't supported yet. That's nothing vulkano specific, just a limitation of how things worked and the best I could do is an error message & vaguely accurate return value. I mentioned 'until recently' because the latest loader (1.0.68.0) added the ability to query layers for extension support before returning to the application, so any renderdoc |
@baldurk I am on arch linux. The latest version of renderdoc available on AUR is 1.0.1 released in March. I get the same renderdocmd Output
Nvidia Driver version 390.48 All of my code is here |
I don't know rust or vulkano, so maybe I'm missing something, but the code there still doesn't show exactly which extensions you're trying to load (some are implicit from Also FYI you shouldn't directly activate the renderdoc layer like that, it's not an explicit layer that should be referenced by the application, instead you should run your program through the renderdoc UI or CLI tool to make sure it's initialised properly. |
@baldurk I am sorry, I forgot to mention all the information. I am on X11. The loaded instance extensions are
Okay, Got it, And Thank you so much for your time. |
If you're loading Also on X11 I'm not sure why it's asking for |
@baldurk You are absolutely correct! The program was crashing when I enabled I tried it again but this time I disabled The fix for this should be added in Thanks again. Correction: |
If I try to launch one of the examples to inspect with renderdoc I get the following error:
Just running the executable does work.
Happens both on Wayland and XOrg. FYI
The text was updated successfully, but these errors were encountered: