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

Migrate to Bevy 0.15 #68

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Migrate to Bevy 0.15 #68

merged 1 commit into from
Dec 12, 2024

Conversation

voximity
Copy link
Contributor

@voximity voximity commented Dec 12, 2024

This is a migration to Bevy 0.15. It is simply composed of all necessary changes to make bevy-tnua build with Bevy 0.15, bevy_rapier 0.28, and the tentative Avian 0.2.

There are some problems that currently exist, some likely block this PR:

  • Avian has not published the version supporting 0.15 (I think version 0.2.0 is in progress?)
  • No consideration/work done to convert Bundle pattern to required components
  • Rapier now supports multiple physics "worlds," since RapierConfiguration/RapierContext are now components instead of resources. bevy-tnua may require implementation changes to support this feature properly
  • The character does not properly float/move/respond in all Avian demos

As per #45, I did not make any assumptions about how to adjust the API for the new Bevy version - I provide this as a starting point, and to anyone who depends on tnua and wants to migrate their project to 0.15.

@idanarye
Copy link
Owner

Thanks! I'll take it from here (can't promise to publish today, but I'll try to do it during the weekend)

@idanarye idanarye merged commit 9cf0707 into idanarye:main Dec 12, 2024
6 of 8 checks passed
@idanarye
Copy link
Owner

I looked into the why the floating problem in the Avian demos, and it looks like some of the components were changed. Specifically:

  • Something was changed with the layers. Instead of having all the layers, objects created without layers only have the default layer (i.e. the one generated by Default::default())
  • Mass and AngularInteria are not automatically added - I have to look in ComputedMass and ComputedAngularInteria instead.

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