-
Notifications
You must be signed in to change notification settings - Fork 946
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
Raspberry Pi 4 support #1467
Comments
I imagine the Vulkan driver for Pi 4 is still fresh new, it may have gotchas depending on the code path taken, and we may be using Vulkan slightly differently from the demos you tested on previously. |
See also: #1069. I've reported one of the corruption bugs to the Mesa bug tracker, but I haven't heard anything back from it, so I'm not too optimistic this will work any time soon. The gles backend is likely to work in a shorter time frame. |
Thanks for your fast response! |
Let's figure out what the problem is with Vulkan first. If the Vulkan demos work, we should be able to get it to work as well. |
I have tried it for hours now... VkTrace is a pain to find and build, it just keeps throwing compiler errors at me 😡. CMake does its best to avoid recognizing pthread, are there build instructions for Debian out there? Edit: Attached CMake output |
Last time I tried, building VkTrace was a pain as well, and I failed :) Anyhow, it was deprecated recently in favor of https://github.com/LunarG/gfxreconstruct . Would you want to try it? |
It worked ... after modifying |
As far as I can see, they seem to use a completely different vulkan surface type: The working one uses a |
I wouldn't expect Xcb/Xlib difference to show up in frame times, but it's remotely possible, given that Window System Integration affects the delays in presentation and frame acquisition. |
Some posts on reddit etc. suggested to me that Xlib causes many performance issues on the Raspberry, is there a way to check whether that is the problem? I also noted that the wgpu version didn't enumerate the device properties, how does it then get the correct surface? When running |
Technically speaking, wgpu-rs is not responsible for picking Xlib vs Xcb. You are feeding the
What call exactly do you see us missing? AFAIK, we are enumerating everything. |
Thanks, that clarifies things, I was just wondering why the backtrace recorded |
Maybe you can try one of the SDL wrappers? Somebody must be able to create an XCB window. Perhaps, even using the |
The issue for winit adding support for xcb is here rust-windowing/winit#5 (just adding to link these two issues together). |
I think, from reading this, this is closable. |
Hello guys,
I have recently installed the vulkan broadcom driver for the raspberry pi 4 and tested it by running the Sascha-Willems demos. They ran without issue at high performance, the ImGui example ran at ~200 FPS. Relieved to move away from old OpenGL 2.1 to your modern library using the vulkan backend, I launched an example from imgui-wgpu-rs. It runs at 20 FPS with visual artifacts such as shapes flickering or tearing. I don't know where to start searching for the bug, whether the driver is to blame or the ash vulkan loader, so please help me fix that issue.
These examples were run on a fresh build from the recommended OS (32-bit) using the latest cargo and mesa driver available. I was able to reproduce the same effects using my other raspberry pi with an old build, so it doesn't seem to be local to my device.
Thanks in advance!
The text was updated successfully, but these errors were encountered: