Player reference sequencer transform bug

General Issues and Bug Reporting
, , ,
1

Summary

Player reference device sequencer transforms are bugged at runtime. The transform appears to be calculated relative to origin rather than device location. Behavior in editor is ok but in session is not

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Character

Steps to Reproduce

  1. create a sequence
  2. add a player reference device to that sequence (must not be at origin)
  3. modify the device transform during the sequence
  4. preview the sequence in viewport and observe the transform
  5. run the sequence at runtime in a session and observe the transform is different at the points where its transform is modified by sequence e.g. if the sequence is meant to move the device 100.0 up, it will instead put the device at 100.0 above the origin

Expected Result

When a player reference deviceā€™s transform is modified by a sequence it should be calculated at runtime with reference to the deviceā€™s location in the world

Observed Result

When a player reference deviceā€™s transform is modified by a sequence it is being calculated at runtime with reference to the origin

Platform(s)

Only tested on pc in editor session, private session and published island

Video

Additional Notes

In the video, the player reference device is situated on top of the wall and the sphere is at the origin.

2

Having same issue. Wish this got more attention. I have a temporary fix of attaching the skeleton to an invisible mesh transform

4

If I am understanding correctly, this also happens with Character devices, and NPC spawners, used in sequencer.

To workaround:

  • Device transforms and rotations in details panel reset to 0,0,0

  • To move/rotate the model of Character devices and NPC spawners, use the transform and rotation inside sequencer. It wonā€™t move the device itself, but the model attached to it.

  • You should move them by hand because something is different between sequencer XYZ/LUF and details panel XYZ/LUF. (As seen by the character doing a 180 and moving what seems to be towards the camera.)

  • Donā€™t try to set the device in the spot you want, then transfer those coordinates over to the sequencer, it will be additive and really skew the XYZ/LUF. The Y(Up) will work generally speaking, but the forwards and sides seem to be flipped from my experience.

Having root motion on your animations helps so you donā€™t have to add keyframes with regards to movement. Key your initial starting location and rotation, let the anim run, then blend from there. LUF keyed at 0,0,0 in sequencer is world origin, so if anyone reading this canā€™t figure out why their characters disappear in game, but are positioned properly in editor, this is why.

1 Like
6

FORT-1123804 has been ā€˜Backloggedā€™. This is an issue that is in a queue to be addressed.

1 Like
7

It seems like on other platforms like nintendo switch the transform is fine? need to test further though. I was messing around with the different ā€œadditiveā€ and ā€œrelativeā€ transform options