You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two issues, both point to a (two?) problems in the collider:
There is one issue is one issue, it points to a potential problems in the collider:
Letting DemoCrash sit still for a few second will occasionally show the box stack becoming "active", as if one of the boxes moved slightly or was brushed by another object. As pointed out by @Murat65536 , this is simply caused by being in contact with the centipede.
Choosing ReorderingMethod.REORDERING_METHOD__DONT_REORDER in DxQuickStep line 147 causes DemoCrash to become unstable. It is not clear that this is really a problem, maybe it is just a property of doing ordered collision? I think I read somewhere that randomized collision tends to be more stable...
This could be a good starting point for debugging a problem in DxQuickStep.
The text was updated successfully, but these errors were encountered:
The box stack is becoming active because it is being brushed by the centipede object. If you print out the position of the sphere that is brushing the box stack, you will see that it's position is slightly changing, which is probably causing the the box stack to become "active".
There are two issues, both point to a (two?) problems in the collider:There is one issue is one issue, it points to a potential problems in the collider:
Letting DemoCrash sit still for a few second will occasionally show the box stack becoming "active", as if one of the boxes moved slightly or was brushed by another object.As pointed out by @Murat65536 , this is simply caused by being in contact with the centipede.ReorderingMethod.REORDERING_METHOD__DONT_REORDER
inDxQuickStep
line 147 causes DemoCrash to become unstable. It is not clear that this is really a problem, maybe it is just a property of doing ordered collision? I think I read somewhere that randomized collision tends to be more stable...This could be a good starting point for debugging a problem in DxQuickStep.
The text was updated successfully, but these errors were encountered: