I have a simple LevelSequence that contains a track for a SkeletalMeshActor that animates an object in the scene. When I use an Origin Override, though, it seems to not affect the SkeletalMeshActor. The GatherTask, GatherSubsequenceTask and AssignTask in MovieSceneTransformOriginSystem.cpp do not seem to even iterate on that actor subsequence at all. How can this be made to work?
I do note, though, that if I make the SkeletalMeshActor a child of a StaticMeshActor that’s in a subsequence within that main TransformOrigin-animated LevelSequence then I can still get it to animate relative to the TransformOrigin movement. It’s a bit of an indirect workaround but it does work.
Hey there,
I’ve tested out some of the basics with what you’ve stated here and I wasn’t able to repro, but I have a couple of more questions so I can help you out.
- Which version of 5.5 are you working with? There were some adjustments to Override Instance information and transform origin, but it’s more the opposite problem, where subsequences would get the instance override properly.
- In terms of your setup, are you using an object as your instance override information? If so, is that level object loaded?
- If you drop a breakpoint into Run of FGatherTransformOrigin, are you hitting that breakpoint? (You’ve indicated no, but want to double check) If not, I would double-check that your level sequence actor instance is set up correctly, with bOverrideInstanceDatabeing true if you’re setting this up in code.
If you can, a few screenshots of your setup or a small project file that you can share would be useful to help us pinpoint the source of the issue.
No problem, if you find further information that could point to the issue in the future don’t hesitate to repost on here.
Dustin
I’m on 5.5.4.
I’ve been trying to make an example project on plain unmodified 5.5.4 with minimal assets to reproduce this but it seems to be working in this test project. In our project we certainly do get FGatherTransformOrigin::Run() executing. But there must be something I’m missing in my test project since I can’t replicate the same behaviour.
We do have some modifications in code that could be affecting this a bit but I tried with those changes disabled and still was getting the problem. I’m going to move on to some other work for a bit as my workaround that I mentioned earlier has been working consistently. But I will certainly circle back to this again.
Thanks for your time!