Hi, the code was always working, and still should be, in NewtonIntegrator.pp:208 (and 2 other lines for rotations) I read
if (scene->forces.getMoveRotUsed()) state->pos+=scene->forces.getMove(id);
It was supposed to impose displacement or rotation change directly, and to do it in a way which is thread-safe; changing b.vel may affect other computations going on in that timestep, plus it usually supposes that dt does not change between steps (not always the case). But I see there is only little use for it, and I would have to remember hard what was the reason to introduce it back then. There must have been one :)
Hi, the code was always working, and still should be, in NewtonIntegrato r.pp:208 (and 2 other lines for rotations) I read
if (scene- >forces. getMoveRotUsed( )) state-> pos+=scene- >forces. getMove( id);
It was supposed to impose displacement or rotation change directly, and to do it in a way which is thread-safe; changing b.vel may affect other computations going on in that timestep, plus it usually supposes that dt does not change between steps (not always the case). But I see there is only little use for it, and I would have to remember hard what was the reason to introduce it back then. There must have been one :)
@Jan, do you have NewtonIntegrator in engines?