Skip to content

Conversation

@Ralith
Copy link
Contributor

@Ralith Ralith commented Oct 26, 2025

These are practically necessary when working without a PhysicsPipeline.

A larger change could avoid exposing ModifiedObjects, but it seems like it might be useful as well.

Alternatively, BroadPhaseBvh::update could be modified to pull this data from the ColliderSet itself. In that case the public interface could be narrowed to a method on ColliderSet to clear the modified/removed sets, but this would make it impossible for a user to inject their own modified/removed handles. I'm not sure if that's useful.

These are practically necessary when working without a PhysicsPipeline
@sebcrozet
Copy link
Member

Thank you! I don’t love that change, as it increases the risks of user errors, but I don’t have a better alternative yet. Let’s use that until the whole "use BroadPhase independently from PhysicsPipeline" story gets better.

@sebcrozet sebcrozet merged commit a68d0c6 into dimforge:master Nov 2, 2025
8 checks passed
@Ralith Ralith deleted the push-xxrvnmyoysyr branch November 2, 2025 17:44
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