Allow for 32 max collisions in test_body_motion
#89517
Merged
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.
The
max_collisions
parameter inPhysicsServer3D.body_test_motion
, and by proxyPhysicsBody3D.test_move
andPhysicsBody3D.move_and_collide
, is meant to be capped by the size of the fixed-sizecollisions
array inPhysicsServer3D::MotionResult
that's set to the size ofPhysicsServer3D::MotionResult::MAX_COLLISIONS
, which is currently 32.This is currently being bounds-checked with the
ERR_FAIL_INDEX_V
macro when using Godot Physics, which incorrectly leads to an error when passing amax_collisions
of 32, as themax_collisions
parameter is treated as an index rather than a count.This PR addresses this by switching to
ERR_FAIL_COND_V
instead.