Setting dLoc of motion actuator [0,0,0] via python won't stop object #33585

New Issue

Manuel Bellersen · 2012-12-17T15:30:48+01:00

Manuel Bellersen commented

2012-12-17 15:30:48 +01:00

Category: Logic

%%%An object with character physics-type has a motion actuator which gets set and activated by a python script.
Setting dLoc to anything but [0,0,0] works as expected. Setting it to [0,0,0] should stop the object, if I'm not wrong ( at least it does it in 2.64a).
Sample is attached.%%%

**Category**: Logic %%%An object with character physics-type has a motion actuator which gets set and activated by a python script. Setting dLoc to anything but [0,0,0] works as expected. Setting it to [0,0,0] should stop the object, if I'm not wrong ( at least it does it in 2.64a). Sample is attached.%%%

Manuel Bellersen commented

2012-12-17 15:30:48 +01:00

Changed status to: 'Open'

Manuel Bellersen commented

2012-12-17 15:33:36 +01:00

%%%Sorry. Forgot to say:
→ happens in blender-2.65-linux-glibc211-x86_64
→ same with blender-2.65-r53020-linux-glibc211-x86_64
→ being on Linux 64bit%%%

%%%Sorry. Forgot to say: → happens in blender-2.65-linux-glibc211-x86_64 → same with blender-2.65-r53020-linux-glibc211-x86_64 → being on Linux 64bit%%%

Mitchell Stokes commented

2012-12-18 01:54:16 +01:00

%%%The motion actuator doesn't bother with motion if it's using all 0s. If you want to stop the motion you can deactivate the actuator. However, I could make a special case for the character controller.%%%

Manuel Bellersen commented

2012-12-18 21:48:50 +01:00

%%%Sorry. The provided sample was a bit off. Corrected it.
Now it is working for 2.64a and below but not anymore for 2.65.

Just from the natural point I would say setting dLoc to [0,0,0] to not let the object move anymore would be right.
Especially when I want to use dRot to rotate the object.
If I first move the object by setting dLoc to something and after a while setting dLoc to 0 and rotate via setting dLoc e.g. to [0,0,1] then the object should just rotate and not move anymore. Right?
But now it's still moving.

Maybe I just don't understand the character controller ^^

Btw. Thanks for your work!%%%

%%%Sorry. The provided sample was a bit off. Corrected it. Now it is working for 2.64a and below but not anymore for 2.65. Just from the natural point I would say setting dLoc to [0,0,0] to not let the object move anymore would be right. Especially when I want to use dRot to rotate the object. If I first move the object by setting dLoc to something and after a while setting dLoc to 0 and rotate via setting dLoc e.g. to [0,0,1] then the object should just rotate and not move anymore. Right? But now it's still moving. Maybe I just don't understand the character controller ^^ Btw. Thanks for your work!%%%

Mitchell Stokes commented

2013-01-30 06:58:04 +01:00

%%%As of r54201, there is a new Character Motion option for the Motion Actuator. If you set the dloc to (0, 0, 0) while using this option, it will stop the character from moving if no other motion actuators are also trying to move it.%%%

Mitchell Stokes commented

2013-01-30 06:58:04 +01:00

Changed status from 'Open' to: 'Resolved'

Mitchell Stokes closed this issue

2013-01-30 06:58:04 +01: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

Setting dLoc of motion actuator [0,0,0] via python won't stop object #33585