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!
@Max.Chen Dang, I was on the wrong branch! I compiled “ue5-main” which made UE 5.6.0. The dev branch makes UE 5.3.3 and I can confirm the crashes are fixed!! I’ll put it through extensive testing tomorrow and will let you know if I find any oddities.
Thank you so much for pointing me in the right direction Max!
@Max.Chen OK the dev-5.5 branch certainly works much better, but I still get a crash in my project. This is happening with a second viewport open (so with sequencer, adjusting camera position in one viewport, looking through the camera in the other). Seems to be fine if I only use one viewport.
That’s very frustrating! I was waiting and hoping the latest fix would fix it, but I still can’t animate any camera in a sequencer, especially with metahumans.
The only workaround that seems to be helping, but not always, is disabling the preview camera in Editor Preferences.
This is driving me absolutely nuts - I’ve a huge project to get wrapped up by the end of the week and it’s completely impossible with this crash occurring constantly… following along in absolute desperation that someone figures out a fix
It’s impossible to work, and I need to finish the project by the end of the week. Every 2–10 changes in Sequencer result in a crash.
I understand that UE is primarily a game engine, but you have attracted hundreds of thousands of people who work with Sequencer—motion designers, animators, cinema artists, etc. Thinking that this bug is not a top priority is just delusional.
Same here. I’m- no, my entire team is on a huge project that big as- a major size, and a lot of us are having this issue. Our TA team is also aware of this error and hangning on it but no one made any solution.
This is serious, significant size of money is bleeding!! Wasting time and money hit the schedule and the quality of the game. Have you imagine 200 talented artists wasting their time struggling with an error and the company pay for it? This is stupid.
Ran into this as well in the latest version as of writing (5.5.3), seems to be specifically related to interacting with the camera in sequencer.
I know that attaching a camera to a skeletal mesh will crash Unreal in a few seconds and cause the uniform buffer error. Disabling camera preview and thumbnails does not prevent this.
Had other cases though where interacting with cameras can cause it as well but seems more random.
Edit: This might be due a separate issue of Unreal rapidly taking up RAM when adjusting keyframes in the curve editor and causing an “exception_access_violation” error. Had this since 5.2.
Edit 2: It seems what was ultimately causing it was having the default RHI set to DirectX 12. Setting it to DirectX 11 fixed the majority of the issues (can interact and attach cameras to actors no issue now).
We are running into this same issue in 5.5.3. Absolutely killing us! You can seem to hold it at bay so long as you have the camera hidden and do not try to directly manipulate the camera via the normal selection handles. I.e. Key a parameter and do you adjustments there. Not ideal.
I have also seen the issue where objects pop to an incorrect position and snap into place if you move a frame. This could also all be related to an issue where, using procedurally created control rigs, we get duplicate joint controllers and they continue to replicate with every save. Sequencer is doing something it didn’t do before. Seems to have been this way since at least 5.3. (Popping objects at least.)
I’ve had same issue with crash when working with cameras in 5.5. I think it may be to do with Camera trying to Cull objects. It crashes every time the camera moves past an actor when I have the camera selected in the sequencer, but if I set the bound culling to be off for that actor it hasn’t crashed yet. Be interesting to see if that fixes it for others.
I switchined off the culling on the Skeletal mesh component in Blue Print…
THIS IS KILLING ME!! On 5.5.3 and can confirm that the bug is still there, been trying to fix this for hours now. Tried everything short of removing the preview screen, because I kind-of really like/need that and it makes my life 10x easier.
Assertion failed: UniformBuffer [File:D:\build++UE5\Sync\Engine\Source\Runtime\RHI\Private\RHIContext.cpp] [Line: 58]
Attemped to assign a null uniform buffer to the global uniform buffer bindings.
This is the error I got. Changed the DX11/12, toggled ray tracing, @Max.chen suggestion, Im still getting this crash, either right when I click the camera, or when I try to move the camera around.
This is awesome news, thank you so much for the update. I’ve just downloaded the patch, keeping my fingers crossed. I’ll report back with findings in a few days.
