Great until this moment 2:30 You should STOP and and explain how algorithm deal with such scenario when division linne cuts trough object XLeft and XRight, YBottom and YTop, this will only work if X and Y position of cutting line is NOT between most distant XY position of objects, same goes with XYZ. We get the minimum and maximum of XYZ position of our objects. And we divide scene, half, until any of X,Y,Z is between MIN and MAX of any of our two objects. That require for example to have such property defined, calculated once all vertices transformations are applied. To create virtual BOX for any object.
Hmm, yes, I have overlooked the explanation. When an object intersect two regions, it will be inserted in both, contributing to the subdivision of both sub regions.
![Coding rigid body physics for voxels [Voxel Devlog #20]](http://i.ytimg.com/vi/byP6cA71Cgw/mqdefault.jpg)
good explanation and great visualisation
Very simple ans straightforward explanation, thank you!
simple but good！
you mightve just saved me
Great until this moment 2:30 You should STOP and and explain how algorithm deal with such scenario when division linne cuts trough object XLeft and XRight, YBottom and YTop, this will only work if X and Y position of cutting line is NOT between most distant XY position of objects, same goes with XYZ. We get the minimum and maximum of XYZ position of our objects. And we divide scene, half, until any of X,Y,Z is between MIN and MAX of any of our two objects. That require for example to have such property defined, calculated once all vertices transformations are applied. To create virtual BOX for any object.
Hmm, yes, I have overlooked the explanation. When an object intersect two regions, it will be inserted in both, contributing to the subdivision of both sub regions.
Please balance your audio man jesus christ.
could you like, speak up...