mirror of
https://github.com/bevyengine/bevy
synced 2024-12-21 02:23:08 +00:00
206c7ce219
Huge thanks to @maniwani, @devil-ira, @hymm, @cart, @superdump and @jakobhellermann for the help with this PR. # Objective - Followup #6587. - Minimal integration for the Stageless Scheduling RFC: https://github.com/bevyengine/rfcs/pull/45 ## Solution - [x] Remove old scheduling module - [x] Migrate new methods to no longer use extension methods - [x] Fix compiler errors - [x] Fix benchmarks - [x] Fix examples - [x] Fix docs - [x] Fix tests ## Changelog ### Added - a large number of methods on `App` to work with schedules ergonomically - the `CoreSchedule` enum - `App::add_extract_system` via the `RenderingAppExtension` trait extension method - the private `prepare_view_uniforms` system now has a public system set for scheduling purposes, called `ViewSet::PrepareUniforms` ### Removed - stages, and all code that mentions stages - states have been dramatically simplified, and no longer use a stack - `RunCriteriaLabel` - `AsSystemLabel` trait - `on_hierarchy_reports_enabled` run criteria (now just uses an ad hoc resource checking run condition) - systems in `RenderSet/Stage::Extract` no longer warn when they do not read data from the main world - `RunCriteriaLabel` - `transform_propagate_system_set`: this was a nonstandard pattern that didn't actually provide enough control. The systems are already `pub`: the docs have been updated to ensure that the third-party usage is clear. ### Changed - `System::default_labels` is now `System::default_system_sets`. - `App::add_default_labels` is now `App::add_default_sets` - `CoreStage` and `StartupStage` enums are now `CoreSet` and `StartupSet` - `App::add_system_set` was renamed to `App::add_systems` - The `StartupSchedule` label is now defined as part of the `CoreSchedules` enum - `.label(SystemLabel)` is now referred to as `.in_set(SystemSet)` - `SystemLabel` trait was replaced by `SystemSet` - `SystemTypeIdLabel<T>` was replaced by `SystemSetType<T>` - The `ReportHierarchyIssue` resource now has a public constructor (`new`), and implements `PartialEq` - Fixed time steps now use a schedule (`CoreSchedule::FixedTimeStep`) rather than a run criteria. - Adding rendering extraction systems now panics rather than silently failing if no subapp with the `RenderApp` label is found. - the `calculate_bounds` system, with the `CalculateBounds` label, is now in `CoreSet::Update`, rather than in `CoreSet::PostUpdate` before commands are applied. - `SceneSpawnerSystem` now runs under `CoreSet::Update`, rather than `CoreStage::PreUpdate.at_end()`. - `bevy_pbr::add_clusters` is no longer an exclusive system - the top level `bevy_ecs::schedule` module was replaced with `bevy_ecs::scheduling` - `tick_global_task_pools_on_main_thread` is no longer run as an exclusive system. Instead, it has been replaced by `tick_global_task_pools`, which uses a `NonSend` resource to force running on the main thread. ## Migration Guide - Calls to `.label(MyLabel)` should be replaced with `.in_set(MySet)` - Stages have been removed. Replace these with system sets, and then add command flushes using the `apply_system_buffers` exclusive system where needed. - The `CoreStage`, `StartupStage, `RenderStage` and `AssetStage` enums have been replaced with `CoreSet`, `StartupSet, `RenderSet` and `AssetSet`. The same scheduling guarantees have been preserved. - Systems are no longer added to `CoreSet::Update` by default. Add systems manually if this behavior is needed, although you should consider adding your game logic systems to `CoreSchedule::FixedTimestep` instead for more reliable framerate-independent behavior. - Similarly, startup systems are no longer part of `StartupSet::Startup` by default. In most cases, this won't matter to you. - For example, `add_system_to_stage(CoreStage::PostUpdate, my_system)` should be replaced with - `add_system(my_system.in_set(CoreSet::PostUpdate)` - When testing systems or otherwise running them in a headless fashion, simply construct and run a schedule using `Schedule::new()` and `World::run_schedule` rather than constructing stages - Run criteria have been renamed to run conditions. These can now be combined with each other and with states. - Looping run criteria and state stacks have been removed. Use an exclusive system that runs a schedule if you need this level of control over system control flow. - For app-level control flow over which schedules get run when (such as for rollback networking), create your own schedule and insert it under the `CoreSchedule::Outer` label. - Fixed timesteps are now evaluated in a schedule, rather than controlled via run criteria. The `run_fixed_timestep` system runs this schedule between `CoreSet::First` and `CoreSet::PreUpdate` by default. - Command flush points introduced by `AssetStage` have been removed. If you were relying on these, add them back manually. - Adding extract systems is now typically done directly on the main app. Make sure the `RenderingAppExtension` trait is in scope, then call `app.add_extract_system(my_system)`. - the `calculate_bounds` system, with the `CalculateBounds` label, is now in `CoreSet::Update`, rather than in `CoreSet::PostUpdate` before commands are applied. You may need to order your movement systems to occur before this system in order to avoid system order ambiguities in culling behavior. - the `RenderLabel` `AppLabel` was renamed to `RenderApp` for clarity - `App::add_state` now takes 0 arguments: the starting state is set based on the `Default` impl. - Instead of creating `SystemSet` containers for systems that run in stages, simply use `.on_enter::<State::Variant>()` or its `on_exit` or `on_update` siblings. - `SystemLabel` derives should be replaced with `SystemSet`. You will also need to add the `Debug`, `PartialEq`, `Eq`, and `Hash` traits to satisfy the new trait bounds. - `with_run_criteria` has been renamed to `run_if`. Run criteria have been renamed to run conditions for clarity, and should now simply return a bool. - States have been dramatically simplified: there is no longer a "state stack". To queue a transition to the next state, call `NextState::set` ## TODO - [x] remove dead methods on App and World - [x] add `App::add_system_to_schedule` and `App::add_systems_to_schedule` - [x] avoid adding the default system set at inappropriate times - [x] remove any accidental cycles in the default plugins schedule - [x] migrate benchmarks - [x] expose explicit labels for the built-in command flush points - [x] migrate engine code - [x] remove all mentions of stages from the docs - [x] verify docs for States - [x] fix uses of exclusive systems that use .end / .at_start / .before_commands - [x] migrate RenderStage and AssetStage - [x] migrate examples - [x] ensure that transform propagation is exported in a sufficiently public way (the systems are already pub) - [x] ensure that on_enter schedules are run at least once before the main app - [x] re-enable opt-in to execution order ambiguities - [x] revert change to `update_bounds` to ensure it runs in `PostUpdate` - [x] test all examples - [x] unbreak directional lights - [x] unbreak shadows (see 3d_scene, 3d_shape, lighting, transparaency_3d examples) - [x] game menu example shows loading screen and menu simultaneously - [x] display settings menu is a blank screen - [x] `without_winit` example panics - [x] ensure all tests pass - [x] SubApp doc test fails - [x] runs_spawn_local tasks fails - [x] [Fix panic_when_hierachy_cycle test hanging](https://github.com/alice-i-cecile/bevy/pull/120) ## Points of Difficulty and Controversy **Reviewers, please give feedback on these and look closely** 1. Default sets, from the RFC, have been removed. These added a tremendous amount of implicit complexity and result in hard to debug scheduling errors. They're going to be tackled in the form of "base sets" by @cart in a followup. 2. The outer schedule controls which schedule is run when `App::update` is called. 3. I implemented `Label for `Box<dyn Label>` for our label types. This enables us to store schedule labels in concrete form, and then later run them. I ran into the same set of problems when working with one-shot systems. We've previously investigated this pattern in depth, and it does not appear to lead to extra indirection with nested boxes. 4. `SubApp::update` simply runs the default schedule once. This sucks, but this whole API is incomplete and this was the minimal changeset. 5. `time_system` and `tick_global_task_pools_on_main_thread` no longer use exclusive systems to attempt to force scheduling order 6. Implemetnation strategy for fixed timesteps 7. `AssetStage` was migrated to `AssetSet` without reintroducing command flush points. These did not appear to be used, and it's nice to remove these bottlenecks. 8. Migration of `bevy_render/lib.rs` and pipelined rendering. The logic here is unusually tricky, as we have complex scheduling requirements. ## Future Work (ideally before 0.10) - Rename schedule_v3 module to schedule or scheduling - Add a derive macro to states, and likely a `EnumIter` trait of some form - Figure out what exactly to do with the "systems added should basically work by default" problem - Improve ergonomics for working with fixed timesteps and states - Polish FixedTime API to match Time - Rebase and merge #7415 - Resolve all internal ambiguities (blocked on better tools, especially #7442) - Add "base sets" to replace the removed default sets.
147 lines
6.5 KiB
Rust
147 lines
6.5 KiB
Rust
use async_channel::{Receiver, Sender};
|
|
|
|
use bevy_app::{App, AppLabel, CoreSchedule, Plugin, SubApp};
|
|
use bevy_ecs::{
|
|
schedule_v3::MainThreadExecutor,
|
|
system::Resource,
|
|
world::{Mut, World},
|
|
};
|
|
use bevy_tasks::ComputeTaskPool;
|
|
|
|
use crate::RenderApp;
|
|
|
|
/// A Label for the sub app that runs the parts of pipelined rendering that need to run on the main thread.
|
|
///
|
|
/// The Main schedule of this app can be used to run logic after the render schedule starts, but
|
|
/// before I/O processing. This can be useful for something like frame pacing.
|
|
#[derive(Debug, Clone, Copy, Hash, PartialEq, Eq, AppLabel)]
|
|
pub struct RenderExtractApp;
|
|
|
|
/// Channel to send the render app from the main thread to the rendering thread
|
|
#[derive(Resource)]
|
|
pub struct MainToRenderAppSender(pub Sender<SubApp>);
|
|
|
|
/// Channel to send the render app from the render thread to the main thread
|
|
#[derive(Resource)]
|
|
pub struct RenderToMainAppReceiver(pub Receiver<SubApp>);
|
|
|
|
/// The [`PipelinedRenderingPlugin`] can be added to your application to enable pipelined rendering.
|
|
/// This moves rendering into a different thread, so that the Nth frame's rendering can
|
|
/// be run at the same time as the N + 1 frame's simulation.
|
|
///
|
|
/// ```text
|
|
/// |--------------------|--------------------|--------------------|--------------------|
|
|
/// | simulation thread | frame 1 simulation | frame 2 simulation | frame 3 simulation |
|
|
/// |--------------------|--------------------|--------------------|--------------------|
|
|
/// | rendering thread | | frame 1 rendering | frame 2 rendering |
|
|
/// |--------------------|--------------------|--------------------|--------------------|
|
|
/// ```
|
|
///
|
|
/// The plugin is dependent on the [`crate::RenderApp`] added by [`crate::RenderPlugin`] and so must
|
|
/// be added after that plugin. If it is not added after, the plugin will do nothing.
|
|
///
|
|
/// A single frame of execution looks something like below
|
|
///
|
|
/// ```text
|
|
/// |--------------------------------------------------------------------|
|
|
/// | | RenderExtractApp schedule | winit events | main schedule |
|
|
/// | extract |----------------------------------------------------------|
|
|
/// | | extract commands | rendering schedule |
|
|
/// |--------------------------------------------------------------------|
|
|
/// ```
|
|
///
|
|
/// - `extract` is the step where data is copied from the main world to the render world.
|
|
/// This is run on the main app's thread.
|
|
/// - On the render thread, we first apply the `extract commands`. This is not run during extract, so the
|
|
/// main schedule can start sooner.
|
|
/// - Then the `rendering schedule` is run. See [`RenderSet`](crate::RenderSet) for the standard steps in this process.
|
|
/// - In parallel to the rendering thread the [`RenderExtractApp`] schedule runs. By
|
|
/// default this schedule is empty. But it is useful if you need something to run before I/O processing.
|
|
/// - Next all the `winit events` are processed.
|
|
/// - And finally the `main app schedule` is run.
|
|
/// - Once both the `main app schedule` and the `render schedule` are finished running, `extract` is run again.
|
|
#[derive(Default)]
|
|
pub struct PipelinedRenderingPlugin;
|
|
|
|
impl Plugin for PipelinedRenderingPlugin {
|
|
fn build(&self, app: &mut App) {
|
|
// Don't add RenderExtractApp if RenderApp isn't initialized.
|
|
if app.get_sub_app(RenderApp).is_err() {
|
|
return;
|
|
}
|
|
app.insert_resource(MainThreadExecutor::new());
|
|
|
|
let mut sub_app = App::empty();
|
|
sub_app.add_simple_outer_schedule();
|
|
sub_app.init_schedule(CoreSchedule::Main);
|
|
app.insert_sub_app(RenderExtractApp, SubApp::new(sub_app, update_rendering));
|
|
}
|
|
|
|
// Sets up the render thread and inserts resources into the main app used for controlling the render thread.
|
|
fn setup(&self, app: &mut App) {
|
|
// skip setting up when headless
|
|
if app.get_sub_app(RenderExtractApp).is_err() {
|
|
return;
|
|
}
|
|
|
|
let (app_to_render_sender, app_to_render_receiver) = async_channel::bounded::<SubApp>(1);
|
|
let (render_to_app_sender, render_to_app_receiver) = async_channel::bounded::<SubApp>(1);
|
|
|
|
let mut render_app = app
|
|
.remove_sub_app(RenderApp)
|
|
.expect("Unable to get RenderApp. Another plugin may have removed the RenderApp before PipelinedRenderingPlugin");
|
|
|
|
// clone main thread executor to render world
|
|
let executor = app.world.get_resource::<MainThreadExecutor>().unwrap();
|
|
render_app.app.world.insert_resource(executor.clone());
|
|
|
|
render_to_app_sender.send_blocking(render_app).unwrap();
|
|
|
|
app.insert_resource(MainToRenderAppSender(app_to_render_sender));
|
|
app.insert_resource(RenderToMainAppReceiver(render_to_app_receiver));
|
|
|
|
std::thread::spawn(move || {
|
|
#[cfg(feature = "trace")]
|
|
let _span = bevy_utils::tracing::info_span!("render thread").entered();
|
|
|
|
loop {
|
|
// run a scope here to allow main world to use this thread while it's waiting for the render app
|
|
let mut render_app = ComputeTaskPool::get()
|
|
.scope(|s| {
|
|
s.spawn(async { app_to_render_receiver.recv().await.unwrap() });
|
|
})
|
|
.pop()
|
|
.unwrap();
|
|
|
|
#[cfg(feature = "trace")]
|
|
let _sub_app_span =
|
|
bevy_utils::tracing::info_span!("sub app", name = ?RenderApp).entered();
|
|
render_app.run();
|
|
render_to_app_sender.send_blocking(render_app).unwrap();
|
|
}
|
|
});
|
|
}
|
|
}
|
|
|
|
// This function waits for the rendering world to be received,
|
|
// runs extract, and then sends the rendering world back to the render thread.
|
|
fn update_rendering(app_world: &mut World, _sub_app: &mut App) {
|
|
app_world.resource_scope(|world, main_thread_executor: Mut<MainThreadExecutor>| {
|
|
// we use a scope here to run any main thread tasks that the render world still needs to run
|
|
// while we wait for the render world to be received.
|
|
let mut render_app = ComputeTaskPool::get()
|
|
.scope_with_executor(true, Some(&*main_thread_executor.0), |s| {
|
|
s.spawn(async {
|
|
let receiver = world.get_resource::<RenderToMainAppReceiver>().unwrap();
|
|
receiver.0.recv().await.unwrap()
|
|
});
|
|
})
|
|
.pop()
|
|
.unwrap();
|
|
|
|
render_app.extract(world);
|
|
|
|
let sender = world.resource::<MainToRenderAppSender>();
|
|
sender.0.send_blocking(render_app).unwrap();
|
|
});
|
|
}
|