ActionActuator do not deactivate on state change #30179

New Issue

Monster · 2012-02-14T11:07:52+01:00

Monster commented

2012-02-14 11:07:52 +01:00

Category: Animation

%%%OS: XP professional
GPU: ATI Mobility Radeon X2300
BGE: 2.61

This is an hard to identify bug. My analyzes might be incorrect. The issue is there.
It is important when using states and ActionActuators for character animation.

State A:

Activates an ActionActuator to play action "A" (play mode) from 1..10
After 60 frames the state changes to state B

State B:

Activates an ActionActuator to play action"B" (play mode) from 1..25
After 60 frames the state changes to state A

I can't find any docs but I think this happens on state change: if there is no connection to any actuator, the actuator gets deactivated.

The ActionActuator seems not to act like this. When the ActionActuator is running on state switch it keeps running even without an controller.
This produces unexpected animations. Together with the issues from Bug 30178 the results are really strange.
%%%

**Category**: Animation %%%OS: XP professional GPU: ATI Mobility Radeon X2300 BGE: 2.61 This is an hard to identify bug. My analyzes might be incorrect. The issue is there. It is important when using states and ActionActuators for character animation. State A: - Activates an ActionActuator to play action "A" (play mode) from 1..10 - After 60 frames the state changes to state B State B: - Activates an ActionActuator to play action"B" (play mode) from 1..25 - After 60 frames the state changes to state A I can't find any docs but I think this happens on state change: if there is no connection to any actuator, the actuator gets deactivated. The ActionActuator seems not to act like this. When the ActionActuator is running on state switch it keeps running even without an controller. This produces unexpected animations. Together with the issues from Bug 30178 the results are really strange. %%%

Monster commented

2012-02-14 11:07:52 +01:00

Changed status to: 'Open'

Brecht Van Lommel commented

2012-02-14 13:07:12 +01:00

%%%Moved from Blender 2.6 Bug Tracker to Game Engine%%%

Raf Colson commented

2014-08-24 18:57:14 +02:00

Added subscriber: @raco

Raf Colson commented

2014-08-24 18:57:14 +02:00

Made a simpler blend file which tests Set State Actuator with Action Actuator. Play 'Scene' and see that it works as it should. Then play 'Scene_Sensors_reused' and see that it doesn't work, while it should.

Monster's original blend file also contains a lot of sensors that are reused. As this second blend file clearly shows that this gives issues, maybe this explains the weird things happening in the first.

Actions_sensors_bug.blend

Made a simpler blend file which tests Set State Actuator with Action Actuator. Play 'Scene' and see that it works as it should. Then play 'Scene_Sensors_reused' and see that it doesn't work, while it should. Monster's original blend file also contains a lot of sensors that are reused. As this second blend file clearly shows that this gives issues, maybe this explains the weird things happening in the first. [Actions_sensors_bug.blend](https://archive.blender.org/developer/F106517/Actions_sensors_bug.blend)

Porteries Tristan commented

2015-07-28 11:27:17 +02:00

Added subscriber: @panzergame