Incorrect transform retuned in sequencer events

  1. Create a sequence with a camera.
  2. Create an event on the sequence
  3. Catch the event in the level blueprint and print the transform of the step 1 camera.
  4. The tranform is 0, 0, 0; 0, 0, 0: 1,1,1 always.

Log:

LogBlueprintUserMessages: [“level”] Tick: Translation: X=505.183 Y=0.184 Z=180.127 Rotation: P=0.000000 Y=179.999985 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Event: Translation: X=0.000 Y=0.000 Z=0.000 Rotation: P=0.000000 Y=0.000000 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Tick: Translation: X=504.887 Y=0.184 Z=180.130 Rotation: P=0.000000 Y=179.999985 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Tick: Translation: X=504.887 Y=0.184 Z=180.130 Rotation: P=0.000000 Y=179.999985 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Tick: Translation: X=504.887 Y=0.184 Z=180.130 Rotation: P=0.000000 Y=179.999985 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Event: Translation: X=0.000 Y=0.000 Z=0.000 Rotation: P=0.000000 Y=0.000000 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000

LogBlueprintUserMessages: [“level”] Tick: Translation: X=504.588 Y=0.185 Z=180.132 Rotation: P=0.000000 Y=179.999985 R=0.000000 Scale X=1.000 Y=1.000 Z=1.000


On the other hand the event is triggered 2 times whithout reason.

Hey Daverkex,

Thanks for reporting this, but it appears that this has been fixed in 4.13. There does not appear to be a particular bug report for this, but general fixes appear to have resolved it.

Hey thanks for answering.
What bug is solved, incorrect transform or that the event triggered 2 times or the two?

Hah, I totally missed that last comment about it triggering twice (See Here). So yes, both are resolved in 4.13.