Sequencer​​ Pasting Anomalies and Crashes \ Sequencer 粘贴异常和崩溃

Sequencer​​ Pasting Anomalies and Crashes \ Sequencer 粘贴异常和崩溃

1.新建Sequencer,将Crash.txt里的内容粘贴进去,你会发现Actor是灰色的异常状态,对象不可见,此时在Sequencer 中选中它,Copy,就会崩溃

2.重复第一步,但是不要Copy,而是右键转换成可替换Actor,然后再转换成可生成Actor,此时一切正常,对象可见

1.Create a new Sequencer and paste the contents from Crash.txt into it. You will observe that Actors appear grayed out with an error state, rendering the objects invisible. If you attempt to copy these Actors within Sequencer, it will trigger a crash.

2.Repeat step 1, but instead of copying, right-click and convert the Actor to a replaceable actor, then further convert it to a spawnable actor. At this stage, the system functions normally, and the object becomes visible.

重现步骤

Hello [mention removed]​

Thank you for reaching out and reporting this issue.

I was able to reproduce it.

I’ll make an issue report and share the link once I have it.

All the best,

[mention removed]​

Hello [mention removed]​

While testing, I noticed that you are referencing an Object that is not present in the project:

LogProperty: Warning: ObjectProperty /Script/Sequencer.MovieSceneCopyableBinding:SpawnableObjectTemplates.SpawnableObjectTemplates: unresolved reference to ‘"/Script/Engine.Actor’/Game/Levels/Release/SystemLevel/HeroChoose/LS_Hero_HouYi_k.LS_Hero_HouYi_k:MovieScene_0.Actor_12’"’

This creates an InvalidBoundObject, and that’s why copying it crashes the engine.

While technically this is a user error, crashing the engine when copying an object that the Editor knows is in an invalid state is an oversight.

IMHO, this should be better handled by the engine, and for that, I’ve made a JIRA report.

It shall 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 at https://issues.unrealengine.com/issue/UE-300322

I’ll close the case, but feel free to reply if you have anything else to add.

All the best,

[mention removed]​