Snap time and value was only uccuring for Absolute view mode, but time should always be snapped regardless.
#jira UE-159804
#rb matt.hoffman, mike.zyracki
#preflight 62d6137f164251d065b8e6db
[CL 21163843 by Max Chen in ue5-main branch]
LastDraggedAttributes might not be set if nothing has been dragged.
Seems to be fallout from UE-150118 CL#19971467 but I haven't been able to reproduce it.
#rb mike.zyracki, jurre.debaare
#preflight 62d05daadc4397d3840fc318
#ROBOMERGE-OWNER: david.hibbitts
#ROBOMERGE-AUTHOR: max.chen
#ROBOMERGE-SOURCE: CL 21096464 via CL 21096630 via CL 21096769
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v972-20964824)
[CL 21099995 by max chen in ue5-main branch]
Gather up all the final drag times of the keys. For each time, get all the keys that match that time and keep the key that moved the most.
#jira UE-156008
#rb matt.hoffman, mike.zyracki
#preflight 629f9d3485333f266455db03
[CL 20558041 by Max Chen in ue5-main branch]
#fix ensure that interactive changes in the curve editor for Animation does not trigger recompression or caching of FRichCurve
#misc fix up curve editor drag/spinbox operations to actually use the property change flag(s)
#misc AnimSequence now evaluates float curves directly from model (which allows previewing interactive changes)
#jira UE-150118
#rb Thomas.Sarkanen
#preflight 626a6702464ae4f520e4aa13
#ROBOMERGE-AUTHOR: jurre.debaare
#ROBOMERGE-SOURCE: CL 19957750 in //UE5/Release-5.0/... via CL 19958488
#ROBOMERGE-BOT: UE5 (Release-Engine-Staging -> Main) (v943-19904690)
[CL 19971467 by jurre debaare in ue5-main branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10869241 via CL 10869527 via CL 10869904
#ROBOMERGE-BOT: (v613-10869866)
[CL 10870586 by ryan durand in Main branch]
The curve editor supports three view types by default - an absolute view (default, matches old behavior), a stacked view and a normalized view. Stacked views draw each curve separately (so non-overlapping) and normalized against their own min/max values. The normalized view draws all curves overlapping with each one normalized against its own min/max values.
A tree view has been added to help effectively manage large numbers of curves. Selecting curves in the treeview controls which curves are visible in the view area. The treeview also supports pinning curves. These pinned curves will always be visible regardless of your selection in the tree view.
A transform tool and a retiming tool have been implemented (via a plugin) which is enabled by default. The transform tool allows you to do a marquee selection of keys and then translate and scale the positions of these keys. The retiming tool allows you to create a 1 dimensional lattice to adjust the timing of your keys with a linear falloff between each lattice point. These tools work across multiple views at the same time which is especially useful if you are representing one dimensional data (such as event keys) in a view, as it allows you to adjust this data at the same time as your animation curves. A smoothing filter has been implemented (via a plugin) to allow running highpass and lowpass filters on your keys.
Opening the curve editor in Sequencer/UMG now creates a separate dockable tab which can be resized and docked as desired. A time slider has been added to the Curve Editor which is synchronized to the playback time in Sequencer. This allows you to scrub time in the curve editor without having to find the Sequencer window and adjust time there while looking at your keys and previewing your animation in the viewport at the same time.
Rudimentary support has been added for saving and later restoring a set of curves in your current session. This allows you to do a rudimentary copy/paste of entire curves but can also be useful for saving a curve, making adjustments to it and then deciding you want to go back - simply reapply the saved curve! Each curve added supports an intention name (such as "Location.X" or "FieldOfView"), and these intention names will be used when trying to apply curves. This allows you to reliably take all of the curves of a transform on one object and apply them to another object (and ensure that Location.X gets applied to the new Location.X, etc.) this can be helpful if you have a mixed set of curves buffered (such as a location and a field of view). In the event that no curves match by intention you can store and apply a single curve at a time from any intention to any other intention.
The Curve Asset editors (float, vector and color curve assets) have been changed to use the new editor. They support the same treeviews, filtering and tools that the Sequencer editor does. In addition, the Color Curve asset editor adds an additional view which provides a 1 dimensional gradient editor as an easier way to visualize and edit colors instead of the channels individually.
#rb Max.Chen, Andrew.Rodham
#ROBOMERGE-SOURCE: CL 6631811 via CL 6633746
#ROBOMERGE-BOT: (vundefined-6620334)
[CL 6633863 by matt hoffman in Main branch]
