mirror of
https://github.com/bevyengine/bevy
synced 2025-02-16 14:08:32 +00:00
add more tracing docs
This commit is contained in:
parent
9e1a1d15ea
commit
7db4821287
1 changed files with 3 additions and 3 deletions
|
@ -12,6 +12,6 @@
|
||||||
When a suspected wgpu error occurs, you should capture a wgpu trace so that Bevy and wgpu devs can debug using the [wgpu player tool](https://github.com/gfx-rs/wgpu/wiki/Debugging-wgpu-Applications#tracing-infrastructure).
|
When a suspected wgpu error occurs, you should capture a wgpu trace so that Bevy and wgpu devs can debug using the [wgpu player tool](https://github.com/gfx-rs/wgpu/wiki/Debugging-wgpu-Applications#tracing-infrastructure).
|
||||||
|
|
||||||
To capture a wgpu trace:
|
To capture a wgpu trace:
|
||||||
1. create a new `wgpu_trace` folder in the root of your cargo workspace
|
1. Create a new `wgpu_trace` folder in the root of your cargo workspace
|
||||||
2. add the "wgpu_trace" feature to the bevy crate. (ex: `cargo run --example features wgpu_trace`)
|
2. Add the "wgpu_trace" feature to the bevy crate. (ex: `cargo run --example features wgpu_trace`)
|
||||||
3. zip up the wgpu_trace folder and attach it to the relevant issue
|
3. Zip up the wgpu_trace folder and attach it to the relevant issue. New wgpu issues should generally be created here https://github.com/gfx-rs/wgpu. Please include the wgpu revision in your bug reports. You can find the revision in the Cargo.lock file in your workspace.
|
||||||
|
|
Loading…
Add table
Reference in a new issue