ActionActuator resets position when Start-Frame is not set (add to local mode) #38986

New Issue

Monster · 2014-03-06T08:00:00+01:00

Monster commented

2014-03-06 08:00:00 +01:00

System Information
Operating system and graphics card

Blender Version
Broken:2.69.0 r60995 (and 2.68a)
Worked: unknown

Descriptio:n
When playing an action with [Add] and - [x] with untouched Start-Frame (0.00), the position will be reset to the world start position of the action ignoring [Add] and [L].

I attach 3 files:

go.blend - every thing is fine (by setting start frame 1.00 and 0.00 later)
noGo.blend - showing the symptom (by not setting the start frame)
MultiNoGo.blend - showing two objects playing the same action (start frame not set) -> another issue: playing altering the visibility of the objects (I guess it is the same cause)

Step-by-Step:
These are the steps to reproduce the symptom:

start with default scene, look through the camera, frame 1, cube is selected
add a LocRot keyframe

go to frame 11

move the cube <2>

rotate the cube <45>

add a LocRot keyframe

add an AlwaysSensor with True Pulse (to auto-trigger the ActionActuator)

add an ActionActuator with: CubeAction, Play + [Add] + - , end frame 11.00 (do not touch start frame)

connect the AlwaysSensor with the ActionActuator (which creates an AndController)

start the BGE

Observation:
The cube plays the Action once as expected (with motion + turn)
The cube resets to 0,0,0 but keeps the orientation and plays from there

QuickFix:

Setting the start-frame of the ActionActuator to 1.0 permanently fixes the problem for this particular actuator. It can even be set to 1.0. (With undo the issue returns)

**System Information** Operating system and graphics card **Blender Version** Broken:2.69.0 r60995 (and 2.68a) Worked: unknown **Descriptio:n** When playing an action with [Add] and - [x] with untouched Start-Frame (0.00), the position will be reset to the world start position of the action ignoring [Add] and [L]. I attach 3 files: - [go.blend](https://archive.blender.org/developer/F80077/go.blend) - every thing is fine (by setting start frame 1.00 and 0.00 later) - [noGo.blend](https://archive.blender.org/developer/F80078/noGo.blend) - showing the symptom (by not setting the start frame) - [MultiNoGo.blend](https://archive.blender.org/developer/F80079/MultiNoGo.blend) - showing two objects playing the same action (start frame not set) -> another issue: playing altering the visibility of the objects (I guess it is the same cause) **Step-by-Step:** These are the steps to reproduce the symptom: - start with default scene, look through the camera, frame 1, cube is selected - add a LocRot keyframe <i> - go to frame 11 - move the cube <g><z><2> - rotate the cube <r><45> - add a LocRot keyframe <i> - add an AlwaysSensor with True Pulse (to auto-trigger the ActionActuator) - add an ActionActuator with: CubeAction, Play + [Add] + - [x], end frame 11.00 (do not touch start frame) - connect the AlwaysSensor with the ActionActuator (which creates an AndController) - start the BGE <p> **Observation:** The cube plays the Action once as expected (with motion + turn) The cube resets to 0,0,0 but keeps the orientation and plays from there **QuickFix:** - Setting the start-frame of the ActionActuator to 1.0 permanently fixes the problem for this particular actuator. It can even be set to 1.0. (With undo the issue returns)

Monster commented

2014-03-06 08:00:00 +01:00

Changed status to: 'Open'

Monster commented

2014-03-06 08:00:00 +01:00

Added subscriber: @monster

Inês Almeida commented

2014-03-06 10:36:29 +01:00

Added subscriber: @brita

Inês Almeida commented

2014-03-06 10:36:29 +01:00

The files:

go.blend - every thing is fine (by setting start frame 1.00 and 0.00 later)
noGo.blend - showing the symptom (by not setting the start frame)
MultiNoGo.blend - showing two objects playing the same action (start frame not set) -> another issue: playing altering the visibility of the objects (I guess it is the same cause)

(@monster referencing them inside a code block doesn't seem to work)

The files: - [go.blend](https://archive.blender.org/developer/F80077/go.blend) - every thing is fine (by setting start frame 1.00 and 0.00 later) - [noGo.blend](https://archive.blender.org/developer/F80078/noGo.blend) - showing the symptom (by not setting the start frame) - [MultiNoGo.blend](https://archive.blender.org/developer/F80079/MultiNoGo.blend) - showing two objects playing the same action (start frame not set) -> another issue: playing altering the visibility of the objects (I guess it is the same cause) (@monster referencing them inside a code block doesn't seem to work)

Jorge Bernal commented

2015-05-16 01:43:18 +02:00

Added subscriber: @JorgeBernalMartinez