11b41206eb
This updates the `pipelined-rendering` branch to use the latest `bevy_ecs` from `main`. This accomplishes a couple of goals: 1. prepares for upcoming `custom-shaders` branch changes, which were what drove many of the recent bevy_ecs changes on `main` 2. prepares for the soon-to-happen merge of `pipelined-rendering` into `main`. By including bevy_ecs changes now, we make that merge simpler / easier to review. I split this up into 3 commits: 1. **add upstream bevy_ecs**: please don't bother reviewing this content. it has already received thorough review on `main` and is a literal copy/paste of the relevant folders (the old folders were deleted so the directories are literally exactly the same as `main`). 2. **support manual buffer application in stages**: this is used to enable the Extract step. we've already reviewed this once on the `pipelined-rendering` branch, but its worth looking at one more time in the new context of (1). 3. **support manual archetype updates in QueryState**: same situation as (2).
37 lines
1.2 KiB
Rust
37 lines
1.2 KiB
Rust
use bevy::{
|
|
diagnostic::{Diagnostic, DiagnosticId, Diagnostics, LogDiagnosticsPlugin},
|
|
prelude::*,
|
|
};
|
|
|
|
/// This example illustrates how to create a custom diagnostic
|
|
fn main() {
|
|
App::new()
|
|
.add_plugins(DefaultPlugins)
|
|
// The "print diagnostics" plugin is optional. It just visualizes our diagnostics in the
|
|
// console
|
|
.add_plugin(LogDiagnosticsPlugin::default())
|
|
.add_startup_system(setup_diagnostic_system)
|
|
.add_system(my_system)
|
|
.run();
|
|
}
|
|
|
|
// All diagnostics should have a unique DiagnosticId. for each new diagnostic, generate a new random
|
|
// number
|
|
pub const SYSTEM_ITERATION_COUNT: DiagnosticId =
|
|
DiagnosticId::from_u128(337040787172757619024841343456040760896);
|
|
|
|
fn setup_diagnostic_system(mut diagnostics: ResMut<Diagnostics>) {
|
|
// Diagnostics must be initialized before measurements can be added.
|
|
// In general it's a good idea to set them up in a "startup system".
|
|
diagnostics.add(Diagnostic::new(
|
|
SYSTEM_ITERATION_COUNT,
|
|
"system_iteration_count",
|
|
10,
|
|
));
|
|
}
|
|
|
|
fn my_system(mut diagnostics: ResMut<Diagnostics>) {
|
|
// Add a measurement of 10.0 for our diagnostic each time this system runs
|
|
diagnostics.add_measurement(SYSTEM_ITERATION_COUNT, 10.0);
|
|
}
|