Fix get_contact_count
sometimes being incorrect in _process
#88019
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.
Fixes #88018.
This replaces the usage of
body_get_direct_state
inRigidBody*D.get_contact_count
with a cached value that's populated as part ofRigidBody*D._sync_body_state
, similar to other states in the physics bodies, which prevents_process
from accessing a yet-to-be-synced future contact count.This also fixes the inability to use
get_contact_count
from_process
when using thephysics/*d/run_on_separate_thread
project setting.