Rigid-body-tool's constraint in animation doesn't listen to driver properly #36104

New Issue

fr fff · 2013-07-11T16:49:27+02:00

fr fff commented

2013-07-11 16:49:27 +02:00

Relates to: #36088

%%%--- Operating System, Graphics card ---
ubuntu 12.10, graphics unknown

- Blender version with error ---

2.67b (2.67.0 r57123) from blender.org (thank you!)
(it uses rigid body tools, I believe that is available from version 2.66 and upwards only )

- Short description of error ---

A rigid body constraint from the rigid body tools, type motor, has a driver on angular motor enable (use_motor_ang) button. It returns False, then True, then False depending on current frame. It isn't moving on first False which is correct, turns on True which is correct, but doesn't stop on second False.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

In the blend file, I did never add a driver in it, I didn't even play the animation without driver. I guess it can't be in cache this way? To recreate the error:

in the text panel, Press Ctrl-A, then Ctrl C to copy the text
in the python console panel press Ctrl P to paste and execute
in the physics tab of the properties panel, right click the angular motor enable button,
select add driver
in the f-curve/driver panel, click the pinkish Angular motor line
at the Drivers section right to it (scroll down maybe) click the Expr text field
instead of False enter driverFunc()
press enter
click UpdateDependencies button
in 3d view press Alt A to start the animation.

At frame 50 the motor starts to turn, at frame 100 it does NOT stop. In the operating system's console you can see that it is not enabled any more, so it should stop there. When you hover the enable button on the properties panel the enable state can also be seen live. Diplaying enable status is equal to the console, but the motor isn't acting accordingly.

%%%

**Relates to**: #36088 %%%--- Operating System, Graphics card --- ubuntu 12.10, graphics unknown - Blender version with error --- 2.67b (2.67.0 r57123) from blender.org (thank you!) (it uses rigid body tools, I believe that is available from version 2.66 and upwards only ) - Short description of error --- A rigid body constraint from the rigid body tools, type motor, has a driver on angular motor enable (use_motor_ang) button. It returns False, then True, then False depending on current frame. It isn't moving on first False which is correct, turns on True which is correct, but doesn't stop on second False. - Steps for others to reproduce the error (preferably based on attached .blend file) --- In the blend file, I did never add a driver in it, I didn't even play the animation without driver. I guess it can't be in cache this way? To recreate the error: in the text panel, Press Ctrl-A, then Ctrl C to copy the text in the python console panel press Ctrl P to paste and execute in the physics tab of the properties panel, right click the angular motor enable button, select add driver in the f-curve/driver panel, click the pinkish Angular motor line at the Drivers section right to it (scroll down maybe) click the Expr text field instead of False enter driverFunc() press enter click UpdateDependencies button in 3d view press Alt A to start the animation. At frame 50 the motor starts to turn, at frame 100 it does NOT stop. In the operating system's console you can see that it is not enabled any more, so it should stop there. When you hover the enable button on the properties panel the enable state can also be seen live. Diplaying enable status is equal to the console, but the motor isn't acting accordingly. %%%

fr fff commented

2013-07-11 16:49:27 +02:00

Changed status to: 'Open'

fr fff commented

2013-07-11 17:22:18 +02:00

%%%Actually the same driver for the motor's speed field right next to the enable button works like a charm. It actually takes 0 and 1 instead of True and False (automatically). Just found that out.
Cheers all!%%%

%%%Actually the same driver for the motor's speed field right next to the enable button works like a charm. It actually takes 0 and 1 instead of True and False (automatically). Just found that out. Cheers all!%%%

fr fff commented

2013-07-20 11:06:51 +02:00

%%%SORRY IT'S NOT A BUG!
My fault. Disabling the motor just does not stop the rigid body. I increased rotation damping, now the rotation stops slowly!

in blender:
Run the script, Update dependencies (of driver), Alt A
file: rigidbodyconstraint driver enabled motor.blend see Attachmants tab ^
Sorry and happy blending!%%%

%%%SORRY IT'S NOT A BUG! My fault. Disabling the motor just does not stop the rigid body. I increased rotation damping, now the rotation stops slowly! - in blender: - Run the script, Update dependencies (of driver), Alt A file: rigidbodyconstraint driver enabled motor.blend see Attachmants tab ^ Sorry and happy blending!%%%

Sergej Reich commented

2013-07-21 12:29:45 +02:00

%%%Ok that makes sense, thanks for the report anyways, closing.%%%

Sergej Reich commented

2013-07-21 12:29:45 +02:00

Changed status from 'Open' to: 'Archived'

Sergej Reich closed this issue

2013-07-21 12:29:45 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Rigid-body-tool's constraint in animation doesn't listen to driver properly #36104