-
Notifications
You must be signed in to change notification settings - Fork 25
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
Improve error handling for gfxCreateGraphicsPipelines #129
Comments
The backend often spews out errors/warning and other messages via rust standard logging mechanisms. They are hooked up to the console output in our debug builds and can be enabled when running with But in this case, we first need to make sure the errors returned by the backend are not ignored. So minor changes to the portability lib are needed. |
I'll check RUST_LOG output tomorrow, thanks. It would be great to mention this in the error message, similarly to how panic says that you can enable backtraces to see more output. |
Ok - RUST_LOG didn't work in release builds but it did work in the debug build:
|
Ok - I see - this is a bug in gfx (filed here gfx-rs/gfx#2324): This code doesn't handle location in attribute descriptors properly, instead assuming that all attributes have linear locations 0-count-1. |
Closing this since the issue is stale and probably doesn't need addressing anymore. |
We are getting VK_ERROR_INCOMPATIBLE_DRIVER when calling CreateGraphicsPipelines for any pipelines in our application; looks like it's coming from here:
portability/libportability-gfx/src/impls.rs
Lines 2103 to 2107 in 7650048
There's no error logs so I'm not sure what the problem is. Would it be possible to communicate the reason for the error via a TTY or something along these lines? These are most likely bugs in portability/gfx/etc. but it's unclear why they happen.
The text was updated successfully, but these errors were encountered: