Page MenuHome

Interpolated text properties do not animate in the viewport
Closed, ResolvedPublic


System Information
Linux 64-bit, AMD Cape Verde card

Blender Version
2.80alpha2 2018-10-30 official binaries

Short description of error
keyframed text properties do not update viewport. One has to go into edit mode and back to refresh.

Exact steps for others to reproduce the error
Create a text object, keyframe character spacing at frame 1.
Move a couple of frames forward, set character spacing to 2, see the viewport update. set keyframe on the spacing property.
Scrub timeline. text does not update based on the interpolated value.
Tab into editing, text updates.

Some properties don't even update the values in the property panel.



Event Timeline

Philipp Oeser (lichtwerk) claimed this task.
Philipp Oeser (lichtwerk) triaged this task as Confirmed, Medium priority.

Can confirm

when changing frames

[SCScene :: View Layer]: Operation is entry point for update: ANIMATION()
[SCScene :: View Layer]: Accumulated recalc bits for CUText: 3
[SCScene :: View Layer]: Accumulated recalc bits for ACTextAction: 2
[SCScene :: View Layer]: BKE_animsys_eval_animdata on CUText (0x7f174eff1b88) at time 4.000000

when switching modes

[SCScene :: View Layer]: Accumulated recalc bits for OBText: 113
[SCScene :: View Layer]: Accumulated recalc bits for CUText: 4294967133
[SCScene :: View Layer]: deg_evaluate_copy_on_write on CUText (0x7f174eff1b88)
[SCScene :: View Layer]: deg_evaluate_copy_on_write on OBText (0x7f1753571208)
[SCScene :: View Layer]: BKE_curve_eval_geometry on CUText (0x7f174eff1b88)
[SCScene :: View Layer]: BKE_object_data_select_update on CUText (0x7f174eff1b88)
[SCScene :: View Layer]: BKE_object_eval_local_transform on OBText (0x7f1753571208)
[SCScene :: View Layer]: BKE_object_eval_uber_data on OBText (0x7f1753571208)
[SCScene :: View Layer]: BKE_object_eval_done on OBText (0x7f1753571208)
[SCScene :: View Layer]: BKE_object_handle_data_update on OBText (0x7f1753571208)

Will try my luck for a bit

Philipp Oeser (lichtwerk) closed this task as Resolved.

Seems like @Sergey Sharybin (sergey) fixed this in rB8e9c16b0cf48.

Will close this (as I am not abled to reproduce this anymore), but feel free to reopen/comment again if issues persist...