Skip to content

Default to wgpu renderer#210

Closed
emilk wants to merge 2 commits intomainfrom
emilk/default-wgpu
Closed

Default to wgpu renderer#210
emilk wants to merge 2 commits intomainfrom
emilk/default-wgpu

Conversation

@emilk
Copy link
Copy Markdown
Owner

@emilk emilk commented Oct 10, 2025 •
edited
Loading

Unfortunately, just switching glow to wgpu causes build errors for web, and runtime errors on native.
Apparently we also need to turn on some wgpu features, but that… sucks. And it is not obvious from the eframe docs.
This needs fixing.

Native

> cargo run
thread 'main' panicked at /Users/emilk/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-27.0.1/src/api/instance.rs:65:13:
No wgpu backend feature that is implemented for the target platform was enabled. See `wgpu::Instance::enabled_backend_features()` for more information.

Web

error[E0433]: failed to resolve: could not find `web_sys` in `wgpu`
   --> /Users/emilk/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/egui-wgpu-0.33.0/src/setup.rs:58:31
    |
58  |                         wgpu::web_sys::window().is_some_and(|w| w.is_secure_context());
    |                               ^^^^^^^ could not find `web_sys` in `wgpu`
    |
note: found an item that was configured out
   --> /Users/emilk/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-27.0.1/src/lib.rs:143:9
    |
143 | pub use web_sys;
    |         ^^^^^^^
note: the item is gated here
   --> /Users/emilk/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-27.0.1/src/lib.rs:142:1
    |
142 | #[cfg(web)]
    | ^^^^^^^^^^^

This was referenced Oct 10, 2025
Merged
Closed
@aspcartman aspcartman mentioned this pull request Oct 16, 2025
Merged
4 tasks
@kasper64
Copy link
Copy Markdown

kasper64 commented Oct 19, 2025

Maybe it's stupid question, but is there a workaround for this?
I looked for the possibility to enable feature of dependencies's dependences, but that doesn't seem possible.

@emilk emilk mentioned this pull request Nov 9, 2025
Open
@emilk emilk force-pushed the emilk/default-wgpu branch from 2f8cefc to ef74953 Compare November 11, 2025 17:05
@emilk
Copy link
Copy Markdown
Owner Author

emilk commented Nov 11, 2025

The work-around is as simple as adding an extra dependency on wgpu with default features enabled:

wgpu = { version = "27.0.1", default-features = true }

I'll see if we could/should do that in eframe already somehow to make this easier

@White-Rabbit-Scientific
Copy link
Copy Markdown

White-Rabbit-Scientific commented Nov 17, 2025

Hey there @emilk , frame_template (with rust 1.88 and egui 0.33.0) with wgpu crashes on my M4 Mac (26.0.1). It has been doing this for a while. Glow works fine. Wgpu used to work.

Steps:

  1. Clone eframe_template
  2. Change feature "glow" to "wgpu"
  3. cargo run
  4. Crash.
thread 'main' panicked at /Users/me/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-27.0.1/src/api/instance.rs:65:13:
No wgpu backend feature that is implemented for the target platform was enabled. See `wgpu::Instance::enabled_backend_features()` for more information.

@Fingel
Copy link
Copy Markdown

Fingel commented Mar 20, 2026

For anyone running into this: the changes in this PR are what you need to apply. Alternatively, you can be more selective about the wgpu features per target:

# native:
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
env_logger = "0.11"
wgpu = { version = "27", features = ["vulkan", "metal", "dx12"] }

# web:
[target.'cfg(target_arch = "wasm32")'.dependencies]
wasm-bindgen-futures = "0.4"
web-sys = "0.3.70"              # to access the DOM (to hide the loading text)
wgpu = { version = "27", features = ["webgl"] }

The bummer is that you need to make sure the wgpu version matches the version that eframe depends on, and that's not obvious without using tooling. But not a huge deal.

@emilk emilk mentioned this pull request Mar 26, 2026
Merged
emilk added a commit that referenced this pull request Mar 26, 2026
@emilk
Use default eframe features (wgpu over glow) (#222)
dc6e458 
* Closes #210
@emilk emilk closed this in #222 Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@emilk @kasper64 @White-Rabbit-Scientific @Fingel