You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running `/home/luke/Projects/floem/target/debug/counter`
warning: queue 0x559c196f8870 destroyed while proxies still attached:
wl_registry@2 still attached
thread 'main' panicked at 'Error in Surface::configure: invalid surface', /home/luke/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.15.1/src/backend/direct.rs:316:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: queue 0x559c196fa3f0 destroyed while proxies still attached:
wl_display@1 still attached
…/examples/counter on main is 📦 v0.1.0 via 🦀 v1.69.0
❯ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia cargo run
Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Running `/home/luke/Projects/floem/target/debug/counter`
warning: queue 0x55c4fb38de40 destroyed while proxies still attached:
wl_registry@2 still attached
warning: queue 0x55c4fb38fe00 destroyed while proxies still attached:
zwp_linux_dmabuf_v1@6 still attached
Per output above, the first block is Intel GPU. Second is offload to Nvidia. When offloaded to Nvidia the example runs fine (and so does lapce floem branch).
I've not much experience with wgpu, but usually when I've encountered this it's been to do with pixel colour types or maybe blending.
The text was updated successfully, but these errors were encountered:
Per output above, the first block is Intel GPU. Second is offload to Nvidia. When offloaded to Nvidia the example runs fine (and so does lapce floem branch).
I've not much experience with wgpu, but usually when I've encountered this it's been to do with pixel colour types or maybe blending.
The text was updated successfully, but these errors were encountered: