Skip to content

Conversation

repulsio
Copy link

Hi Isaac! If you think exposing these additional debug drawing functions is useful, please feel to merge. I've tested that it builds successfully and renders correctly in JS. Thank you!

@isaac-mason
Copy link
Owner

Thanks for the PR 🙂

I think the most useful debug draw utilities are the ones that take recast and detour specific structures to render them the same way as the upstream library. I don't know how useful the others would be over e.g. drawing a trimesh with whatever graphics library you are using more directly, e.g. THREE.BufferGeometry instead of debugDrawTriMesh.

The other thing that would be good to check is how much this increases to the bundle size. If this increases the file sizes by a noteworthy amount maybe it's not worth including them in the main builds given many might not use them.

Probably there's a valid consideration for whether all debug utils should be tree-shakable or only be present in a debug build.

@repulsio
Copy link
Author

repulsio commented Jul 8, 2025

Anytime, Isaac, and great points 😄

Please feel free to close or add any of the functions you find helpful!

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