Sequencer thumbnails \ Sequencer 缩略图

Development Pipeline & Plugins
, ,
1

Hi，我注意到Sequencer保存逻辑的一个变化：

UE5.6在Sequencer内使用Ctrl+S保存的时候，会自动更新缩略图，以往的版本仅仅是点Sequencer的UI保存图标才会更新缩略图（Ctrl+S不会导致更新缩略图），这个功能实际体验并不好，因为当前的视口内容未必是实际相机，也未必有内容，所以捕获出来的总是奇奇怪怪的结果。手动捕获缩略图是很稳定的，但问题是会被这种机制覆盖，也会导致经常被别人覆盖缩略图（并非别人想更新缩略图，只是无意间）。

而选中资源按Ctrl+S或者右键保存，则不会触发缩略图更新。

建议优化成这样：

没设定手动捕获缩略图的时候，可以遵循这个机制。

一旦用户手动捕获过缩略图，Sequencer不再继续更新缩略图。

一旦用户清除了缩略图，Sequencer继续遵循这个机制。

Hi, I’ve observed a change in Sequencer’s saving behavior:

In UE5.6, pressing Ctrl+S within Sequencer now auto-updates thumbnails, whereas previous versions only updated thumbnails when clicking Sequencer’s UI save button (Ctrl+S didn’t trigger updates). This new implementation creates poor UX because viewport content might not match the actual camera or contain any assets at all, often capturing irrelevant content. While manually captured thumbnails are reliable, they get overwritten by this mechanism—even when collaborators save unintentionally (without intending to update thumbnails).

Note: Saving selected assets via Ctrl+S/right-click won’t trigger thumbnail updates.

Suggested optimization:

Follow default behavior if no manually captured thumbnail exists

Disable auto-updates once a manual thumbnail is captured

Resume auto-updates if user clears existing thumbnails

2

Hey there,

Thanks for raising this, we did a code modification to handle this, here’s a link to the github with the change. https://github.com/EpicGames/UnrealEngine/commit/ce1af30761743e7ab3a3d8757ec9edd17ab55d42

You could modify the code here to get more desired behaviour if you like.

I chatted to the dev team about your suggestion and they are open to changing this in the future. For now we’ve logged a bug if you’d like to follow that. https://issues.unrealengine.com/issue/UE-296721 (it could take a couple of days for it to show).

Thanks,

Dustin

3

Our programmers suggest this modification: Add a null check for GetSequencer(). If it returns null, call Super::SaveAsset_Execute(). This ensures code robustness by providing a safeguard; otherwise, unexpected behavior may occur when null. Whether to implement this change is at your discretion – this is merely a suggestion.

4

Thanks for that, I’ll pass it along.