Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial bevy 0.10 port #4

Merged
merged 25 commits into from
Mar 14, 2023
Merged

Initial bevy 0.10 port #4

merged 25 commits into from
Mar 14, 2023

Conversation

johanhelsing
Copy link
Contributor

@johanhelsing johanhelsing commented Mar 12, 2023

This refactors the high-level xpbd algorithm structure to take advantage of bevy_ecs schedule v3 (i.e. stageless).

The algorithm is split into two schedules, one high-level for running one high-level physics step (i.e. DELTA_TIME) step, and one lower-level for the inner substepping (integrate, solve etc.).

@johanhelsing johanhelsing marked this pull request as ready for review March 12, 2023 12:00
@johanhelsing
Copy link
Contributor Author

Alright, ready for some feedback now. It's mostly about naming (see inline todos)

src/lib.rs Show resolved Hide resolved
src/steps/mod.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
@johanhelsing
Copy link
Contributor Author

XpbdSchedule:
xpbdschedule

Substep schedule:
substepschedule

Looks like there are some ambiguities, from my knowledge they were there from before, I've tried to do a pure refactor as best I could.

@Jondolf
Copy link
Owner

Jondolf commented Mar 12, 2023

I think we can maybe address the ambiguities in another PR, as it doesn't seem to be strictly related to the 0.10 migration or caused by it

@Jondolf Jondolf merged commit e326d7d into Jondolf:main Mar 14, 2023
@Jondolf Jondolf mentioned this pull request Mar 14, 2023
@johanhelsing johanhelsing deleted the bevy-0.10 branch March 14, 2023 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants