-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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 #71961
Comments
Note that it may be better to wait a little until physics work stabilizes in 4.0, so we can backport completed work once rather than having to backport fixes several times. |
I absolutely agree, while I'd love the fixes now, I think it would be best to plan for 3.6 having solid physics that can support games being finished with 3.x. |
Have there been enough improvements in 4.0 and 4.1 to warrant a backport to 3.6 yet? 4.2 is just around the corner and physics seem a lot more solid than they were in 3.5. |
4.2? 4.1 hasn't even been released, it's not even in feature freeze yet |
I honestly don't know why I thought it had been already, I think I was getting confused with 4.1 being around the corner (still interested if it'll be backported now as 4.0 is nearly done with). |
.
While it true i think it could be better to wait more, as i think that there could be more fixes incoming when w4 hires the physics engineer they plan, so then they can merge the 4.x changes without doing it more often. |
Godot version
4.0 beta 14
System information
Windows 10
Issue description
Recent updates to 4.0 such as #71447 and #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). I'm reopening this here as I previously incorrectly opened it as a proposal: godotengine/godot-proposals#6158
Steps to reproduce
Most of the bugs are listed here: #45333 (comment)
Minimal reproduction project
N/A
The text was updated successfully, but these errors were encountered: