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

[3.2] PhysicalBone inherited from RigidBody #44150

Closed
wants to merge 1 commit into from

Conversation

dedm0zaj
Copy link

@dedm0zaj dedm0zaj commented Dec 6, 2020

Hello.
I changed the inheritance of the PhysicalBone through the RigidBody. Methods and properties are now available for the PhysicalBone such as add_force, add_torque, linear_velocity, etc.
image
image
image

Bugsquad edit: This closes godotengine/godot-proposals#1951.

For PhysicalBone, it becomes possible to perform all manipulations belonging to RigidBody (add_force, add_torque, linear_velocity, etc)
@dedm0zaj dedm0zaj changed the title PhysicalBone inherited from RigidBody [3.2] PhysicalBone inherited from RigidBody Dec 6, 2020
@Calinou Calinou added this to the 3.2 milestone Dec 6, 2020
@Calinou
Copy link
Member

Calinou commented Dec 6, 2020

Thanks for opening a pull request 🙂

Pull requests (especially ones that break backwards compatibility) should be opened against the master branch instead of 3.2. This is because feature development occurs in the master branch. We can then cherry-pick specific PRs to the 3.2 branch if they don't break backwards compatibility.

@AndreaCatania
Copy link
Contributor

Though, PhysicalBone is not a RigidBody even if they could seems to share some features.
The PhysicalBone has some mechanism that changes its collision model depending on some skeleton parameters; and subsequent RigidBody changes may break how the PhysicalBone works. But most important, under the hood, the physics engine can use a different technology to simulate a more precise and complex joint setup; which is generally used for ragdolls.

It's not yet implemented but implement it after this change would make things more difficult: #28909

I don't think it's desirable change it, even because we already have the methods apply_central_impulse (and similar) on the PhysicalBone; so if anything is missing on the PhysicalBone it's better add it.

@dedm0zaj dedm0zaj requested a review from a team as a code owner March 12, 2021 12:26
Base automatically changed from 3.2 to 3.x March 16, 2021 11:11
@aaronfranke
Copy link
Member

@dedm0zaj Is this still desired? If so, you should perform the above requested change, and remake this PR based on the master branch. Otherwise, this PR will be considered abandoned and closed.

@aaronfranke aaronfranke modified the milestones: 3.2, 3.3 Mar 16, 2021
@akien-mga
Copy link
Member

This would break compat in the API so it can't be made in the 3.x branch, but it can be considered for master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants