4 ) us- small, didnt give up (yet)
Make sure that the locations for Project Home and Media Cache are not indexed by Spotlight and ensure that the Protection Mode preference has been disabled and let us know.
i am getting a lot of these error messages still ( also something I have had reported and was promised that the fix is in 2026.2)
MEMORY : Allocated 35389 MB at address 0x3ed79c000 using mmap()
VIDEO: Display refresh rate detected as: 60.00 Hz
Fontconfig error: No writable cache directories
Output log to: ‘/opt/Autodesk/log/slateDiskCacheCleaner.log’.
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
seems to correlate with slow project loading.. here is a video loading a empty project .. its VERY slow for me , like insanely slow.
also funny enough by accident caught another bug where it would claim no database on host, restarting flame and boom suddenly its there again? aha… this is connected to my flame project server
Still havent used 2026 in a single project, but my artist really want to, but everytime I just test it like a little bit it completely does a bunch of weirds stuff:
I hate that button so much. Pisses me off every time I have to go turn it off.
from my experience it seems to be saved to your user settings. I only had to switch it off once and that follows through to future projects as well.
I have had official confirmation from ADSK that they have replicated my specific problem and this has now been actioned as a ‘Change Request’ to the Dev team.
Hoping for a speedy resolve to this current bug as I’m on a longterm project that I can not roll back to 2025 at this point.
@eddiead thanks a lot for providing data for investigation to our Support team! This is the only way we can fix these issues. We are working on a fix and we will keep you updated.
Thank you Stephane.
Make sure to upgrade to Flame Family 2026.2.1 ASAP!
Fix in dot release in 5 days. That’s impressive.
agreed - a clear demonstration that this is a world class outfit
Upgrading and testing today. Impressive turnaround time from the dev team!
Happy to report that 2026.2.1 has fixed the performance lags I’ve been seeing. I’ve been on a job for the last couple of weeks that’s become a monster - 50+ conforms, etc, running on a Mac Studio. I installed 2026.2.1 today and it’s made a HUGE difference. Performance is as I’d expect.
Bravo! Thanks for getting this out so quickly!!
Agree - thank you so much!! Made a huge difference for me as well. Project saves went from 2-3 minutes to about 10 seconds!
I’d be curious to know what it was that was causing the slow saves…
I am trying to start up a new project on flame 2026
Seems like its absolutely not ready to be used with a project server ?
-
Beign greeted with invalid OCIO config errors still, again, even on jsut default aces 2.0
-
first conformed timeline, permanent errors in the log about some volataile files, leading to me not beign able to SAVE timeline resizes
At this point in time it looks like central/collaborative workflows via a project server is not supported anymore? whats the alternative?
Hi Finn,
While we are not yet using 2026+ in Production since a few deal killer critical bugs have only recently been fixed, the errors you are having seem to be extra-ordinary. I’d be happy to talk about Central Server and your infrastructure to see if there is anything acting as a road block.
Looks like macOS / Linux user permissions. Collaborative workflows, being project server, remote access or Burn, requires matching identities and file access on clients and server.
where does it say that in the documentation?
Sorry but it only says needed stuff is hardlink/softlink support etc if i looked in the right places, nothing about matching UIDs, is it just UIDs or GIDs as well?
My macs use 501 as user, they all have the same username do I just add this user and ID to my project server ? would be great if the project server install guide would properly say what it actually needs.
It also says to just use rw,sync as options to export while the project server sets up many more options about root squashing etc
I dont have problems when connecting to the project server itself and that one does not have the UID of my macs either. just one local user and group 10 “wheel”.
I do have a problem when putting project home on any other server, even one that has UIDs and I matched the exported share of the project server. Not sure if its storage backend related or whatever,..
Anyhow got a call with support on dec 22nd to hopefully drill this problem down, ordered a baremetal NAS today as well to build something from scratch with rocky and have more controll than with my qnap.
I really hope flame will move away from this “using files as a database” mantra and is moving the whole project into the postgresDB instead, much easier to deal with and works well over WAN etc.

