Real-Time Physics Simulation Forum 2021-06-08T16:45:36+00:00 https://pybullet.org/Bullet/phpBB3/app.php/feed/topic/13218 2021-06-08T16:45:36+00:00 2021-06-08T16:45:36+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=43444#p43444 <![CDATA[Re: Wake up object issue]]> MotionState.getWorldTransform() always return the unchanging position. Dynamic bodies that touch the conveyor will pick up the non-zero velocity at all contact points and will slide along. As long as the conveyor's speed is larger than m_linearSleepingThreshold then neither dynamic bodies or the conveyor will be deactivated. If you stop the conveyor and things do go to sleep then when you wake the conveyor it should wake any touching dynamic objects.

In other words: maybe you don't need to override customMaterialCallback. Depends on if you're doing other fancy stuff therein.

Statistics: Posted by drleviathan — Tue Jun 08, 2021 4:45 pm

]]> 2021-06-08T10:06:50+00:00 2021-06-08T10:06:50+00:00 https://pybullet.org/Bullet/phpBB3/viewtopic.php?p=43443#p43443 <![CDATA[Wake up object issue]]> I am trying to avoid using DISABLE_DEACTIVATION flag and trying to find a more efficient way to handle objects that go to sleep being on top of another object. The object bellow is able to apply lateral friction using a customMaterialCallback (to simulate a conveyor) but when it stops, after a bit, the object above goes to sleep, as expected. Then, I cannot wake it up, even if I change the motion speed or try to activate the object state, because the customMaterialCallback is not executed anymore.
Any clever idea on how to awake this objects somehow else?

Statistics: Posted by maiklof — Tue Jun 08, 2021 10:06 am

]]>