-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Backport 4.0 GodotPhysics fixes for 3.6 #6158
Comments
This doesn't need a proposal, just like most backports. It needs someone willing to do the work. |
Not sure about that, I'm pretty sure @Calinou has mentioned opening a proposal for backporting if it isn't currently being backported (and I don't know that it is being done). |
Proposals are never needed for bug ixes, only for new features. |
Sorry, I was thinking it was a proposal. I've re-opened it as a bug issue: godotengine/godot#71961 |
Describe the project you are working on
FPS.
Describe the problem or limitation you are having in your project
Many bugs with GodotPhysics, all of them have been documented.
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Recent updates to 4.0 such as godotengine/godot#71447 and godotengine/godot#70660 would be beneficial to projects close to completion in 3.x, but not using Bullet Physics (Gridmaps, for instance, have collision issues in 3.5 when using bullet that doesn't happen with GodotPhysics).
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
It would be specific backported work to merge the fixes to 4.0 with 3.6.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Definitely not.
Is there a reason why this should be core and not an add-on in the asset library?
It's physics engine fixes.
The text was updated successfully, but these errors were encountered: