You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Bevy 0.10 (unfinished as of writing) includes some very large changes to the scheduling API. These changes should help make #199 and #257 more achievable.
Describe the solution you'd like
Use a recent commit on the main branch of bevy or 0.10 when that comes out.
Allowing system sets to be nested helps when there are a large number of systems that need to be scheduled. Sets of systems (e.g. all the systems needed to update inventories) can be encapsulated together in a sane way without having to create an explicit label for it.
The text was updated successfully, but these errors were encountered:
## Description
Fix#264
Bevy version is pinned to a recent commit on the main branch until 0.10
is released.
## Test Plan
Run examples and tests. Behavior should be the same.
scheduling is a bit tricky so I may have made some subtle mistakes.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Bevy 0.10 (unfinished as of writing) includes some very large changes to the scheduling API. These changes should help make #199 and #257 more achievable.
Describe the solution you'd like
Use a recent commit on the main branch of bevy or 0.10 when that comes out.
Additional context
Allowing system sets to be nested helps when there are a large number of systems that need to be scheduled. Sets of systems (e.g. all the systems needed to update inventories) can be encapsulated together in a sane way without having to create an explicit label for it.
The text was updated successfully, but these errors were encountered: