forestia/bevy
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix non-functional nondeterministic_system_order example (#10719)

Browse Source 
# Objective

The `nondeterministic_system_order` example doesn't actually detect and
log its deliberate order ambiguities! It should, tho.

## Solution

Update the schedule label, and explain in a comment that you can't turn
it on for the whole `Main` schedule in one go (alas, that would be nice,
but it makes sense that it doesn't work that way).
This commit is contained in:
Nick Fagerlund 2023-11-25 13:13:35 -08:00 committed by GitHub
parent c454b26c38
commit 91b64df96b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
examples/ecs/nondeterministic_system_order.rs
View File

@ -19,8 +19,10 @@ use bevy::{
fn main() { fn main() {
App::new() App::new()
// We can modify the reporting strategy for system execution order ambiguities on a per-schedule basis // We can modify the reporting strategy for system execution order ambiguities on a per-schedule basis.
.edit_schedule(Main, |schedule| { // You must do this for each schedule you want to inspect; child schedules executed within an inspected
// schedule do not inherit this modification.
.edit_schedule(Update, |schedule| {
schedule.set_build_settings(ScheduleBuildSettings { schedule.set_build_settings(ScheduleBuildSettings {
ambiguity_detection: LogLevel::Warn, ambiguity_detection: LogLevel::Warn,
..default() ..default()