feat: switch to the new Bvh from parry for the broad-phase#853
Merged
feat: switch to the new Bvh from parry for the broad-phase#853
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the hierarchical SAP broad-phase by a broad-phase based on parry’s new BVH structure.
The
QueryPipelineis now and ephemeral object obtained from the broad-phase withbroad_phase.as_query_pipeline(). It no longer needs to be updated separately from the broad-phase.Since there is no longer any need to update a
QueryPipelineseparately from the broad-phase, this offers a substantial performance improvement on scenes with a large number of objects where rebuilding theQueryPipelinefrom scratch would be very expensive.Currently, the new broad-phase does a little bit more work than what it should to overcome the fact that the narrow-phase hasn’t been designed to not receive any collision-end event from the broad-phase yet. This will be subject to future work.
Note that a large part of this PR modified lines are from
cargo fmtwhich apparently changed its way of sortinguseimports.