2022-05-16 13:53:20 +00:00
|
|
|
//! This example illustrates how to create a custom diagnostic.
|
|
|
|
|
2020-05-04 21:14:49 +00:00
|
|
|
use bevy::{
|
2020-12-24 19:28:31 +00:00
|
|
|
diagnostic::{Diagnostic, DiagnosticId, Diagnostics, LogDiagnosticsPlugin},
|
2020-05-04 21:14:49 +00:00
|
|
|
prelude::*,
|
|
|
|
};
|
|
|
|
|
|
|
|
fn main() {
|
2021-07-27 20:21:06 +00:00
|
|
|
App::new()
|
2020-11-03 03:01:17 +00:00
|
|
|
.add_plugins(DefaultPlugins)
|
2022-05-16 13:53:20 +00:00
|
|
|
// The "print diagnostics" plugin is optional.
|
|
|
|
// It just visualizes our diagnostics in the console.
|
2020-12-24 19:28:31 +00:00
|
|
|
.add_plugin(LogDiagnosticsPlugin::default())
|
2023-03-18 01:45:34 +00:00
|
|
|
.add_systems(Startup, setup_diagnostic_system)
|
|
|
|
.add_systems(Update, my_system)
|
2020-05-04 21:14:49 +00:00
|
|
|
.run();
|
|
|
|
}
|
|
|
|
|
2022-05-16 13:53:20 +00:00
|
|
|
// All diagnostics should have a unique DiagnosticId.
|
|
|
|
// For each new diagnostic, generate a new random number.
|
2020-05-04 21:14:49 +00:00
|
|
|
pub const SYSTEM_ITERATION_COUNT: DiagnosticId =
|
|
|
|
DiagnosticId::from_u128(337040787172757619024841343456040760896);
|
|
|
|
|
2020-05-14 00:52:47 +00:00
|
|
|
fn setup_diagnostic_system(mut diagnostics: ResMut<Diagnostics>) {
|
2020-05-04 21:14:49 +00:00
|
|
|
// 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,
|
|
|
|
));
|
|
|
|
}
|
|
|
|
|
2020-05-14 00:52:47 +00:00
|
|
|
fn my_system(mut diagnostics: ResMut<Diagnostics>) {
|
2022-05-16 13:53:20 +00:00
|
|
|
// Add a measurement of 10.0 for our diagnostic each time this system runs.
|
2022-06-20 17:02:25 +00:00
|
|
|
diagnostics.add_measurement(SYSTEM_ITERATION_COUNT, || 10.0);
|
2020-05-04 21:14:49 +00:00
|
|
|
}
|