Box3D + ECS compatibility?

Summary · qwen2.5:32b

Box3D's state management is incompatible with ECS systems designed for optimal performance through contiguous array storage, potentially causing cache coherency issues. The key solution suggested is to refactor Box3D to align with the ECS paradigm used; simply using pointers would not resolve potential cache misses due to scattered memory allocation.

Excerpt

<!-- SC_OFF --><div class="md"><p>Looking at Box3D's repo, it appears that it's hanging on to state - which by my understanding means that we won't be able to use it with an ECS that's intended to maximize performance by storing state in contiguous arrays (i.e. archetypal ECS) for cache coherency while various systems iterate over state data.</p> <p>Is the only solution to refactor Box3D to operate within the paradigm of whatever ECS that is being utilized? It seems like just changing it to use pointers to where the data actually is would still result in the indirection, and potential cache misses of the pointers themselves being scattered across memory, without controlling their allocation.</p> <p>Any thoughts or ideas? :]</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/deftware"> /u/deftware </a> <br /> <span><a href="https://www.reddit.com/r/gamedev/comments/1upmtml/box3d_ecs_compatibility/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/gamedev/comments/1upmtml/box3d_ecs_compatibility/">[comments]</a></span>