diff --git a/Cargo.toml b/Cargo.toml index 248f7b5f4624b..3cc7d8ff5b435 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -54,8 +54,8 @@ bevy_gilrs = ["bevy_internal/bevy_gilrs"] bevy_gltf = ["bevy_internal/bevy_gltf"] bevy_winit = ["bevy_internal/bevy_winit"] -trace_chrome = ["bevy_internal/trace_chrome"] -trace_tracy = ["bevy_internal/trace_tracy"] +trace_chrome = ["trace", "bevy_internal/trace_chrome"] +trace_tracy = ["trace", "bevy_internal/trace_tracy"] trace = ["bevy_internal/trace"] wgpu_trace = ["bevy_internal/wgpu_trace"] diff --git a/docs/cargo_features.md b/docs/cargo_features.md index 02ca8d88b11fc..70675f281a19e 100644 --- a/docs/cargo_features.md +++ b/docs/cargo_features.md @@ -21,7 +21,7 @@ |-|-| |bevy_dynamic_plugin|Plugin for dynamic loading (using [libloading](https://crates.io/crates/libloading)).| |dynamic|Forces bevy to be dynamically linked, which improves iterative compile times.| -|trace|Enables system tracing (useful in tandem with a feature like trace_chrome).| +|trace|Enables system tracing.| |trace_chrome|Enables [tracing-chrome](https://github.com/thoren-d/tracing-chrome) as bevy_log output. This allows you to visualize system execution.| |trace_tracy|Enables [Tracy](https://github.com/wolfpld/tracy) as bevy_log output. This allows `Tracy` to connect to and capture profiling data as well as visualize system execution in real-time, present statistics about system execution times, and more.| |wgpu_trace|For tracing wgpu.| diff --git a/docs/profiling.md b/docs/profiling.md index 4bb45cb5ed76d..cbe4f72b48df7 100644 --- a/docs/profiling.md +++ b/docs/profiling.md @@ -6,7 +6,7 @@ Bevy has built-in [tracing](https://github.com/tokio-rs/tracing) spans to make i ### Backend: trace_chrome -`cargo run --release --features trace,trace_chrome` +`cargo run --release --features trace_chrome` After running your app a `json` file in the "chrome tracing format" will be produced. You can open this file in your browser using . It will look something like this (make sure you expand `Process 1`):