Action in one Layer affects Action in another Layer. #28530

New Issue

Mario Mey · 2011-09-07T01:13:49+02:00

Mario Mey commented

2011-09-07 01:13:49 +02:00

Category: Animation

%%%Found in Pepper Branch, now in Trunk.

Animations in different layers shouldn't affect actions in different layer. But it happens. How to repeat it: open the file.

Info:
Action "loop": StartFrame: 0, EndFrame: 50, Layer: 0
Action "reset": StartFrame: 0, EndFrame: 5, BlendIn: 5, Layer: 0

There's a action in loop (starts with Z key). When you press X key, an Action in the same layer reset the bones loc-rot-scale.

In this way, everything it's ok. Now... let's play the bug.

Uncomment "own.playAction('layer',....)". It modify the scale or rotation of another bone in another layer (1). It shouldn't affect layer 0... but it affects it. Try it by yourself. It starts resetting, and, 5 frames later, it get back to a previous pose.

The only way to avoid this error is giving "reset" action a EndFrame and BlendIn of 10 or more (in this case). For the visual, it is not so much difference... but it shouldn't work like that.

Cheers. %%%

**Category**: Animation %%%Found in Pepper Branch, now in Trunk. Animations in different layers shouldn't affect actions in different layer. But it happens. How to repeat it: open the file. Info: Action "loop": StartFrame: 0, EndFrame: 50, Layer: 0 Action "reset": StartFrame: 0, EndFrame: 5, BlendIn: 5, Layer: 0 There's a action in loop (starts with Z key). When you press X key, an Action in the same layer reset the bones loc-rot-scale. In this way, everything it's ok. Now... let's play the bug. Uncomment "own.playAction('layer',....)". It modify the scale or rotation of another bone in another layer (1). It shouldn't affect layer 0... but it affects it. Try it by yourself. It starts resetting, and, 5 frames later, it get back to a previous pose. The only way to avoid this error is giving "reset" action a EndFrame and BlendIn of 10 or more (in this case). For the visual, it is not so much difference... but it shouldn't work like that. Cheers. %%%

Mario Mey commented

2011-09-07 01:13:49 +02:00

Changed status to: 'Open'

Mitchell Stokes commented

2011-09-07 01:14:52 +02:00

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

Mitchell Stokes commented

2011-09-07 01:14:52 +02:00

%%%Moving to the Game Engine tracker.%%%

Mario Mey commented

2012-09-25 21:45:34 +02:00

%%%Similar problems:

Case A:

Action "A" in PLAY mode, playing in Layer 0, 30 frames long.
Action "B" in LOOP mode, playing in Layer 1, 60 frames long.

When action "B" is in frame 60 and starts again (loops), action "A" does the same (starts again).

Case B:

Action "B" (object rotation) in LOOP mode is playing in Layer 1.
I want to play action "A" (obcolor, alpha fade out) in PLAY mode, in Layer 0, 30 frames.

What it does: Action "A" continues playing. Action "B" does not fades out, but when it reach frame 30, the objects gets invisible (alpha=0).

How to make action "B" play:
Before playing action "A", I stop action "B" using stopAction(). Then, I play action "A".

What it does: action "B" stops. Action "A" in layer 0 starts to play (it fades out)... but action "B" STARTS AGAIN. The result is not bad for what I want to do... but not what the code says.%%%

%%%Similar problems: Case A: Action "A" in PLAY mode, playing in Layer 0, 30 frames long. Action "B" in LOOP mode, playing in Layer 1, 60 frames long. When action "B" is in frame 60 and starts again (loops), action "A" does the same (starts again). Case B: Action "B" (object rotation) in LOOP mode is playing in Layer 1. I want to play action "A" (obcolor, alpha fade out) in PLAY mode, in Layer 0, 30 frames. What it does: Action "A" continues playing. Action "B" does not fades out, but when it reach frame 30, the objects gets invisible (alpha=0). How to make action "B" play: Before playing action "A", I stop action "B" using stopAction(). Then, I play action "A". What it does: action "B" stops. Action "A" in layer 0 starts to play (it fades out)... but action "B" STARTS AGAIN. The result is not bad for what I want to do... but not what the code says.%%%

Porteries Tristan commented

2015-07-28 11:46:05 +02:00

Added subscriber: @panzergame

Porteries Tristan commented

2015-07-28 11:46:05 +02:00

Send a blend example file please.

Mario Mey commented

2015-07-28 23:50:36 +02:00

Maybe one of my firsts bug reports... I don't find the file.

I'll try to reproduce it, but I cannot say when.

Thanks for take this bug.

Maybe one of my firsts bug reports... I don't find the file. I'll try to reproduce it, but I cannot say when. Thanks for take this bug.

Mario Mey commented

2016-06-09 21:17:54 +02:00

I "discovered" this bug again... now, I have a file. @Moguri says in #gameblender "I could see blendin behaving strangely with layers. =/"

Open the file, press P.

The three objects has same linear movement. When Suzzane starts moving (blendin:30), it does it with acceleration. When ICOshpere starts moving, Suzzane is affected by it, by doing another acceleration.

Torus is not affected because it has blendin:0. Icosphere would be affected if there is another action in other layer playing at the same time.

94-play-layers.blend

I "discovered" this bug again... now, I have a file. @Moguri says in #gameblender "I could see blendin behaving strangely with layers. =/" Open the file, press P. The three objects has same linear movement. When Suzzane starts moving (blendin:30), it does it with acceleration. When ICOshpere starts moving, Suzzane is affected by it, by doing another acceleration. Torus is not affected because it has blendin:0. Icosphere would be affected if there is another action in other layer playing at the same time. [94-play-layers.blend](https://archive.blender.org/developer/F316614/94-play-layers.blend)

Mario Mey commented

2016-06-18 01:44:42 +02:00

I'm uploading a new file.

94b-play-layers.blend

The low-poli icosphere has it's own armature, same as cylinder. This is to show how the real linear movement should be. The icosphere is making the torus movement. At the beginning, the torus is has 30 frames of blendin. Then, the movement is the same. It is Ok.

Look at the Monkey. It has a 30 frames blendin at the beginning, it's ok. When the uvsphere starts moving, the monkey does something strange. And then, when the Cone starts moving, the Monkey gets slow... and then it reachs to the real move (cylinder move).

What (I think) it should do
The Monkey should have the 30 blendin starting acceleration... and it has the same velocity to infinite.

I'm uploading a new file. [94b-play-layers.blend](https://archive.blender.org/developer/F317554/94b-play-layers.blend) The low-poli icosphere has it's own armature, same as cylinder. This is to show how the real linear movement should be. The icosphere is making the torus movement. At the beginning, the torus is has 30 frames of blendin. Then, the movement is the same. It is Ok. Look at the Monkey. It has a 30 frames blendin at the beginning, it's ok. When the uvsphere starts moving, the monkey does something strange. And then, when the Cone starts moving, the Monkey gets slow... and then it reachs to the real move (cylinder move). **What (I think) it should do** The Monkey should have the 30 blendin starting acceleration... and it has the same velocity to infinite.

Mario Mey commented

2016-06-18 02:07:14 +02:00

Also, I tried to use KX_ACTION_BLEND_ADD with intentions of not affecting other layers/bones... with no success.