From 7db48212871cf244127f45855d2c1bb6ef94c183 Mon Sep 17 00:00:00 2001 From: Carter Anderson Date: Sun, 16 Aug 2020 01:26:42 -0700 Subject: [PATCH] add more tracing docs --- docs/debugging.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/debugging.md b/docs/debugging.md index f108ae3361..759176623d 100644 --- a/docs/debugging.md +++ b/docs/debugging.md @@ -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). To capture a wgpu trace: -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`) -3. zip up the wgpu_trace folder and attach it to the relevant issue +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`) +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.