1 Like
Have you using the stock 2026 release OR the latest 2026.2.1 which addresses saving speed issues?
2026.2.1. Creating a new workspace that only contains my working edits and as few batch groups as possible seems to reset the clock, but it’s an unsustainable way to do things in the long run.
Thanks for confirming you are on the latest version. Have you opened a support ticker for this issue?
Also, did you validate that the Protection Mode preference (User / General / Autosave) is not enabled?
1 Like
I’ve reported back to support and protection mode is no enabled.
1 Like
Just want to add to the chorus singing about how slow everything project related is in Flame 2026.x.x.
My least favourite is a 10 minute wait for an archive to close. The Autodesk AI help bot said it was NFS / SMB related. But I switched to NFS and it’s still takes 10mins once a nightly archive is complete to close the archive.
And yeah just creating an empty library causes a long wait. Which seems mental, like what is it even doing, making absolutely sure it made that empty library exactly right?
When I’m working in Nuke I find myself constantly re-saving because I don’t think it could have saved that fast. Sorry that comparison probably gets tiring.
I’ll probably switch back to 2025 for the next project after a couple of recent runs at it.
Edit: On 2026.2.1 and have the protection thingie off
2 Likes
Same here. Running 2026.2.1 on mac. Everything is terribly slow and auto save takes 10min. Tried all the things but nothing helped. Going back to 2025 for my next project.
1 Like
1 Like
Please make sure to open a ticket with our Support team so they can investigate the issue.
1 Like
Please make sure to open a ticket with our Support team so they can investigate the issue.
1 Like
Upgrade to 2026.2.1 with new features that will blow your mind like… waiting 30 seconds to copy a sequence. And how about the other user fave, waiting 30 seconds to paste that sequence after copying. How about the long requested, 5 minute autosave after a 5 minute random pause that has no reason to have happened. Or how about a random 3 minute pause on startup while waiting for the edit desk to initialize? This update has stuff for all the Mac heads and Linux geeks in your artist pool to whine, bitch moan and groan over.
Upgrade today. You’ll be glad you did.
1 Like
Turns out Flame 2025.2 was the penultimate version, and now our only installed version.
I’ve been on every beta program for about a decade. I have decided to self withdraw from the program as I’ve lost hope for a stable progressive future.
3 Likes
It’s frustrating. Always has been and probably will be. A lot of problems have been righted because of your investigations. I hope you join back up tomorrow.
The issue is what path does that lead down. Nuke Studio? Resolve. Sigh.
I’ll literally post an archive and give Lucid access to support. Just fix it.
1 Like
The issues have persisted for me as well. New projects are some what better, but still slow.
@cnoellert the first one to integrate Weavy
2 Likes
Withdrawing is understandable, but also not a solution. We don’t need to shrink the pool further into a mining town situation.
While I have generally defended ADSK in the sense that the move Postgres and unmanaged media is the right path going forward, what I’m not seeing is a sense of ownership and urgency to fix it.
In tech, we would call this a house on fire situation. This issue is complex and persists. So asking individual users to call support and file tickets, or ask people if they have tried the latest version, when clearly some very experienced users are highlighting that this issue is far from resolved, is not getting anywhere fast enough.
While we may not see this out in the open, as it’s a sensitive manner, but that is the type of situation where you put one of your senior engineers on a plane, fly out and fix it for real. That shows a bias for action and urgency, along with a willingness to take it serious.
In a prior career I used to be the factory escalation engineer for HP Enterprise Storage, including LTO robots. And if shit went sideways on a Friday morning, I’d be on a plane by Friday afternoon to Bentonville and work at the Walmart data center to get to the bottom of it.
I think this is this type of situation. No more support tickets and other procedures. Just take it serious and fix it. The house is indeed on fire. Don’t let it burn down entirely. It would be a sad day.
3 Likes
Looking at the Support tickets backlog, I do not see tickets related to the current issue.
@cnoellert your current ticket is for the "Could not resolve //guest’s address” issue and not the speed issue you see.
Please get to our Support team so they can investigate the problem so the development team can provide solution.