Im getting a lot of crashes when deleting a keyframe in the graph editor in action in batch. like one in ten times I do it. it’s been sending you all the logs. 2026.01.
Thanks for the CER reports Jon. We were able to identify that the crash is not related to deletion of keyframes but to events not being properly removed from the Undo buffer when it is full.
As a workaround you may want to try to bump the amount of Undo levels from 50 to 100 in the General Tab of the User Preferences, but I don’t think this will help that much.
1 Like
Thanks Fred. I will try that anyhow
Im now getting the same thing with no host IP and no database. so when it briefly comes back in the project manager and I click on a project to launch it then crashes the machine. one thing I noticed is that it only happens in my country studio not in the London studio. although its the same Mac studio in both situations. this is something ive done with 2025 all the time and never had a problem
these are the two different location networks im on. the second one is the studio where everything works fine. the first one is the one where it doesnt
you might consider using DHCP with a fixed address.
you might try fixing the IP address to 192.168.4.46
you might look at the HostName, LocalHostName and ComputerName since these are not always static on macOS.
try and set all the names to be the same thing - don’t use hyphens, spaces or apostrophes
use
scutil --get HostName
scutil --set HostName
scutil --get LocalHostName
scutil --set LocalHostName
scutil --get ComputerName
scutil --set ComputerName
1 Like
is 2026 more picky then. as everything was working hunky dory until the upgrade
it may be postgresdb?
there is a service that runs with 2026 called DNS-SD but i can’t confirm if this is the root of your trouble.
It’s documented here
hostname was not set - so ive changed that to be the name of the computer. local host name was weird as it had a -2 on the end. so ive changed that to be the same. computer name was good. lets see if that changes anything. thanks Phil M
macOS can play tricks on you.
computer name plus ‘-2’, ‘-3’, etc.
framestore name plus ‘-2’, ‘-3’, etc.
the finder will magically resolve the names but some services like NFS will reject the name changes and silently fail.
perhaps that’s what’s happening to you?
what did support say?
well by the time I got through the autobot with those clever commands - I made a support case. it got rejected as they said the company name was not what was listed on their list. apparently I missed the LTD off the end. and now its back to square one. so I cant be arsed!
its sort of working now. hasn’t crashed and it launched the project. so maybe you’ve fixed it. I hope Autodesk pay you for your tech support
nah - no better - launched flame this time and it didnt even have a list of hosts. then eventually my laptop appeared then after that the main machine. went into the project and boom crashed again. I give up. can you load a 2026 project in flame 2025?
no - things don’t necessarily go backwards that easily, but don’t give up, just keep doing the same thing over and over again…
i’ll ping you.
Use the ServiceMonitor application.
Select the Diagnostics tab.
Select the Full Diagnostic, Run & Save.
Root through the wall of text in a text editor, and see if you can find anything that says error or fail.
I never run a .0 on a new release for these strange bugs that always occur. I always wait for the next iteration of install that usually works on the bugs. For your current issue, if you need to use 2026, I would back up any old projects and make sure you have no old versions of flame still on the machine.
1 Like
Thats a good plan - wish I had done that!
I’m unable to remember agreeing with ‘wait and see’.
Nothing in life is certain.
It’s probable that this year’s “.0” version is a qualitative improvement over last year’s best guess.
YMMV
