A Question about Breakables

[nebular]

Hi there!

Been playing a little trying to understand how breakables work and have some questions about the intended use case.

I saw that when breaking the object by slicing its geometry (which sits as a children[0] of the Basic3D container) - then discards the parent Basic3D object and sets the children as the parent.

This has a nuber of implications, as the children is not a Basic3D:

1 - object will be at 0,0,0 - ish (as the children pos & quat are the decal - and the real worldpos & quat were in the discarded quats
2 - collisions are then (broken/unstable) - what happens with the collision shape, volume, etc... ?
3 - several places where this body is indexed will rty to call stuff from the basic3d object causing crashes
4 - also - in the case of instances it will fail right away because there is no mesh as chilren of the (fake) instance Basic3d.

Soooo --- As the functionality looks really cool - i wonder how it should be used ? ?

thanks in advance !!!

[lo-th]

Hi thank's
break only work on basic geometry box sphere ...
break create new convex geometry but i have to solve some issu
_ sometime convex is too tiny and create bug (on three side)
_ i have to find best way to get real impulse force ( différente on each engine )