Remove mesh bone_aabbs as they are not used anywhere and calculating them is a pain #70091
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 #56458 once and for all
Tested with MRPs from: #56458, #69516, and #64416 (comment)
The
bone_aabbs
array was added in 449df8f and was only used in one place. That one place was removed in #44649 and since thenbone_aabbs
has never been used. We do however, usesurface[i].bone_aabbs
.There is no point in merging together the various
bone_aabbs
as the bone indices don't necessarily correlate with each other at all. At best this resulted in a fairly chaotic array ofAABB
s.I will need to discuss with @reduz, but my guess behind the original intention of this code was that it should expand the
mesh->aabb
to cover all the individual bone AABBS. If that is the case, then we will be better off doing that during the original calculation of thebone_aabbs
in the RenderingServer