Action Actuator - Flipper Mode Frame Glitches #46122

New Issue

Tobias Lijsen · 2015-09-15T19:29:14+02:00

Tobias Lijsen commented

2015-09-15 19:29:14 +02:00

System Information
win7 64bit

Blender Version
Broken:
2.75 buildbot from 15.9.2015
2.75a official
2.74 official

Worked:
no exact clue - it worked definitly in 2.49b
there have been some Bugreport for this exact topic in Blender 2.71 too - these where solved back then

Short description of error
Frame Glitches in Action Actuator - Flipper Mode
Start and End-Frame sometimes stops 1 frame too early at start - or to late at end

Exact steps for others to reproduce the error

open blend
press P
press right CTRL key several times
see the right "flipper" object stopping at wrong frame sometimes

****BAD WORKAROUND
on the left "flipper" object (use left CTRL key) i do a bad workaround in the Action-Actuator
i set the Start-Frame -1 (to frame 0 istead of 1)
and the End-Frame +1 (to frame 9 instead of 8)
this will fix the glitch but will introduce a not precise animation / reaction

****NOTES
this occurs independent of "animation framerate" setting - wich is set to 60 in this case

thank you and have a good day, Tobi

[flipper_ani_bug.blend](https://archive.blender.org/developer/F233457/flipper_ani_bug.blend) **System Information** win7 64bit **Blender Version** Broken: 2.75 buildbot from 15.9.2015 2.75a official 2.74 official Worked: no exact clue - it worked definitly in 2.49b there have been some Bugreport for this exact topic in Blender 2.71 too - these where solved back then **Short description of error** Frame Glitches in Action Actuator - Flipper Mode Start and End-Frame sometimes stops 1 frame too early at start - or to late at end **Exact steps for others to reproduce the error** - open blend - press P - press right CTRL key several times - see the right "flipper" object stopping at wrong frame sometimes ****BAD WORKAROUND on the left "flipper" object (use left CTRL key) i do a bad workaround in the Action-Actuator i set the Start-Frame -1 (to frame 0 istead of 1) and the End-Frame +1 (to frame 9 instead of 8) this will fix the glitch but will introduce a not precise animation / reaction ****NOTES this occurs independent of "animation framerate" setting - wich is set to 60 in this case thank you and have a good day, Tobi

Tobias Lijsen commented

2015-09-15 19:29:14 +02:00

Changed status to: 'Open'

Tobias Lijsen commented

2015-09-15 19:29:14 +02:00

Added subscriber: @blenderhilfe

Aaron Carlisle self-assigned this 2015-09-15 20:15:57 +02:00

Aaron Carlisle changed title from ~~BGE - Action Actuator - Flipper Mode Frame Glitches~~ to Action Actuator - Flipper Mode Frame Glitches

2015-09-15 20:16:21 +02:00

Aaron Carlisle removed their assignment 2015-09-15 20:16:30 +02:00

Aaron Carlisle commented

2015-09-15 20:16:30 +02:00

Added subscriber: @Blendify

Sergey Sharybin commented

2015-09-22 06:28:43 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-09-22 06:29:30 +02:00

Added subscribers: @hg1, @dfelinto, @Moguri, @brita, @dr.sybren, @panzergame

Sybren A. Stüvel commented

2015-10-01 17:09:36 +02:00

I did some digging, and it worked fine in 2.70a, but was broken in 2.71. It may have something to do with the patch for #41168. If the action is fully played, and then the trigger removed (in this case, you release the RCTRL key), it should play back to the first frame. However, it doesn't update the object, even though BL_Action::Update(float curtime) and BL_Action::UpdateIPOs(float curtime) are called with the correct curtime.

I did some digging, and it worked fine in 2.70a, but was broken in 2.71. It may have something to do with the patch for #41168. If the action is fully played, and then the trigger removed (in this case, you release the RCTRL key), it should play back to the first frame. However, it doesn't update the object, even though `BL_Action::Update(float curtime)` and `BL_Action::UpdateIPOs(float curtime)` are called with the correct `curtime`.

Porteries Tristan commented

2015-10-28 16:22:05 +01:00

@blenderhilfe: The glitch is fixed in 728d1ec504.
@dr.sybren: I confirm for the flipper action not backed, but it's not the subject of this task. We should change it for this bug or close it ?

@blenderhilfe: The glitch is fixed in 728d1ec504. @dr.sybren: I confirm for the flipper action not backed, but it's not the subject of this task. We should change it for this bug or close it ?

Jorge Bernal commented

2015-11-10 06:21:37 +01:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2015-11-10 06:21:37 +01:00

Hi @panzergame,

See #46728 seems related to this issue.

Hi @panzergame, See #46728 seems related to this issue.

Sybren A. Stüvel commented

2015-11-24 08:57:56 +01:00

In #46122#343951, @panzergame wrote:
@dr.sybren: I confirm for the flipper action not backed, but it's not the subject of this task. We should change it for this bug or close it ?

I don't know what you mean with "the flipper action not backed", but I think things should just work. If you can, just fix the bug you found :)

> In #46122#343951, @panzergame wrote: > @dr.sybren: I confirm for the flipper action not backed, but it's not the subject of this task. We should change it for this bug or close it ? I don't know what you mean with "the flipper action not backed", but I think things should just work. If you can, just fix the bug you found :)

Jacob Merrill commented

2016-08-15 20:41:27 +02:00

Added subscriber: @JacobMerrill-1