Question #294519 on Yade changed: https://answers.launchpad.net/yade/+question/294519
Bruno Chareyre posted a new comment: >it is not possible to actually update verletDist during the simulation It is possible of course. The main problem is that the collider is smart: if the grains do not move (as in your exemple) there is no need to detect new collisions. Consequence: the lines after "# Attempting to introduce distant interactions" are not doing anything You can check in the 3D view, the bounds are not modified. The new sizes would be accounted for only after the next colliding step (give a velocity to one body, bounds will change). >As for runEngine(), I confirm adding O.runEngine(O.engines[1]) before O.step() is enough I see. runEngine() skips the check InsertionSortCollider::isActivated(), so you get something even if it would not normally run. In the long run, I think this question of creating distant interactions should be solved without the collider because it has different requirements compared to detecting collisions. Bruno -- You received this question notification because your team yade-users is an answer contact for Yade. _______________________________________________ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
