Time Warp tracks in subsequences causes cook errors

Hello,

We are encountering issues with have a time warp track inside a subsequence, which causes a cook error regarding being unable to save the outermost sequence due to a illegal reference to a property in an inner property of a subsequence. It seems to be the same as UE-274572, it’s marked as to be resolved in 5.8, I was just wondering if this has been addressed by Epic yet? The only workaround is to have the time warp track in the outermost sequence, which for our workflow is not possible.

From my initial investigations it’s due to the outermost’s sequence’s UMovieSceneCompiledData having a direct reference to the custom time dilation curve in the subsequence, but I’ve not gone further than that.

[Attachment Removed]

Apologies for the massive delay. Yes this issue is UE-274572 and we have been looking at this from various angles. We’re hoping to have this fixed in 5.8 (the 5.8 preview will be out soon but will not have this fixed just yet).

Please follow along here updates to that issue: https://issues.unrealengine.com/issue/UE\-274572

Once I have a fix in hand, I’ll update here with the changelist.

[Attachment Removed]

Hi Max,

Thanks for the update, we’ll wait for the fix to come in.

[Attachment Removed]

Hey William,

Here’s the fix for this that’s been committed to UE5/Main:

https://github.com/EpicGames/UnrealEngine/commit/3d7460616c06b77d7433304872456e6e277298e9

And a follow up fix:

https://github.com/EpicGames/UnrealEngine/commit/31370d869d9d2cb890a03bd72735ddf0a9b0c391

The fix will come out with the 5.8 release.

[Attachment Removed]