just noting my experiences in 5.5.2
Have always worked with Sequencer thumbnails off, and camera previews turned off as well.
animating cameras works fine.
but the moment I use camera tracking ( specifically with an actor attached to a moving object)
It crashes within a couple of seconds of me tweaking the animation curves)
I have tried also reducing path trajectory cap to 10, but the crash persists.
Is there another work around someone has found to work? or perhaps an eta on the next hotfix patch?.
this is Kinda critical to completing the animation by the upcoming deadline.
And I should mention, Im suprised at how an issue this significant was missed with the latest unreal 5.4.2, Particularly when they are at patch .2
I would be much more forgiving at a first release ( and typically for my team, recommend not moving to the new version till 1-2 hotfixes come out).
however this is a serious error particularly for people using unreal in a professional work environment with deliverables that cant be missed, AND off the back of us now paying for licences and a reduction on support staff in our region…
I appreciate that it is still an amazing tool for animation but please dont go the way of adobe and autodesk in support and poor release quality.
I don’t know if this is going to help everyone but i was also having very frequent crashes whenever i would try and edit a camera animation in my scene which made it literally impossible to work.
Whilst digging down the youtube rabbit hole of UE 5 optimisation, i came across this video which is nothing at all to do with the camera animation crash issue but linked in the description is his “optimised config file” for the project he made using nanite and PCG for level design.
Since i was playing around with PCG and nanite, i decided to copy the settings in my defaultengine.ini file (after taking a backup) and loaded up my level and amazingly i haven’t had a single crash when working on my camera animations since then and was able to start making progress again.
I haven’t A/B tested each line so i don’t know exactly what fixed my issue nor am I an expert in CVARs but all i can say is, its working much better for me since i did that. Your milage my vary but just wanted to throw that out there just in case it helped someone here
I’ve taken the time and compiled from source, thanks to your heads up, hoping I’d get a crash-free user experience with Sequencer. Sadly my project still crashes due to the same access violation. Please take another look, the bug still lurks and is not fixed!
