1.最新版本UE5.6 Sequencer > Expand/Collapse Nodes and Descendants(Shift+V)只能展开,无法折叠,请修复,UE5.5是正常的。(SequencerShift+V.mp4)
2.Keyed(U)功能启用后,在本来具有关键帧的Actor下添加新的轨道关键帧,新轨道会实时更新在过滤结果里,但是没有关键帧的Actor创建关键帧的时候,这个Actor本身不会出现在过滤结果,这似乎有点矛盾,请修复成实时刷新。(KeyedUpdate.mp4)
1.In the latest UE5.6 Sequencer, Expand/Collapse Nodes and Descendants (Shift+V) can only expand nodes but fails to collapse them. Please fix as UE5.5 functions normally. (SequencerShift+V.mp4)
2.When Keyed (U) is enabled:
Adding new track keyframes to an existing Actor with keyframes updates filter results in real-time.
However, when a keyframe is created for a new Actor without any keyframes, the Actor itself does not appear in filter results.
This behavior appears contradictory. Please implement real-time refresh consistency. (KeyedUpdate.mp4)
Hello [mention removed]
Thank you for reaching out and bringing those issues to our attention.
I was able to replicate both.
I’ll make issue reports and share the links once I have them.
As a side note, I would like to let you know that the general recommendation is to report one issue per case.
I know it can be a bit of extra work, but it helps the dev team’s understanding of each case if it revolves around a single issue, especially when discussions get very long; it can become confusing if it branches.
It’s also important for the service metrics: multiple issues in one case negatively affect the perceived efficiency of the EPS service.
Thank you for your understanding.
All the best,
[mention removed]
Thanks for the reminder—I’ll take care of it next time.
Hello [mention removed]
Thank you again for reporting these issues.
I’ve made two JIRA reports to be added to the Unreal issue tracker website (https://issues.unrealengine.com).
Please note that Epic ultimately determines whether the issue will be made publicly accessible, and the process can take a few days; therefore, the tracking link may not be immediately accessible.
Once available, you will be able to track the resolution of the Expand/Collapse Nodes and Descendants (Shift+V) issue at Unreal Engine Issues and Bug Tracker (UE\-300120) and the resolution of the Keyed (U) issue at Unreal Engine Issues and Bug Tracker (UE\-300304\).
I’ll close the case, but feel free to reply if you have anything else to add.
All the best,
[mention removed]