-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Failed to work on Intel HD since pixels v0.5 #224
Comments
There are two issues here. First I'll address why you see a segfault:
Lavapipe is a Vulkan implementation built on LLVMpipe. The second issue here is that you should probably not be using You may need to install a Vulkan driver for the GPU if you want to use it. The file is named
And there might be one more catch to be aware of: There are a bunch of open tickets on the |
Thank you for the references. Now I have a better understanding what's going on. While I have So I'll stick to the OpenGL (thanks again for the
|
Awesome! Glad you were able to find a workaround. I haven't tried the OpenGL backend, I just know it's a work in progress. |
Hi.
I have issues with pixels on
Intel HD 3000
(yeah, I know it's an old hardware).OS is Ubuntu 20.04 LTS.
Last working version for me was pixels = "0.5".
When I execute
The game of life
example with latestpixels
from Github, it shows the window for a second and then crashes:GIF recording is a bit misleading - it shows Conway window first and then breaks with the Segmentation fault.
With gdb:
RUST_LOG=trace log is 76 kb so I put here the ending:
Speaking of WGPU, the
cube
andhello-triangle
examples work just fine with the latest WGPU, while e.g.texture-arrays
and a few others fails with:Is this the
pixels
issue or it's on theWGPU
side? Appreciated for any workaround suggestions.The text was updated successfully, but these errors were encountered: