Is 2026 terribly slow because of the new database structure, or is something else going on?

[finnjaeger]

@philm

…e project server.I only know of only a few places that ever tried a project server workflow:one: very small, didn’t work, gave uptwo: you, made it look like swan lake, ran into 2026 troublesthree: big company with lots of engineering and software development (including the guy who may or may not have invented project server) and they use it very very successfully, every day, but never talk about it

4 ) us- small, didnt give up (yet)

[Slabrie]

@davejahns

…ct from scratch. But I’d like advice on what is the best way to use the new database and project structure?I have a single Mac workstation, with a 60TB external drive configured as RAID5.For this single user setup, what is the best practice for where to set the project and setups path? Obviously media will go to the raid - but should projects and setups be set to the boot drive?Thanks for any help!

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.

[finnjaeger]

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:

[feganflamer]

@johnag

very very very long shot and probably not related but I had very slow save times until I flicked the PROTECTION MODE switch in Flame General Prefs. Not sure how it came on but when I turned it off my system was snappy again.

I hate that button so much. Pisses me off every time I have to go turn it off.

[eddiead]

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.

[eddiead]

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.

[Slabrie]

@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.

[eddiead]

Thank you Stephane.

[Slabrie]

Make sure to upgrade to Flame Family 2026.2.1 ASAP!

The Flame Family 2026.2.1 Service Pack is Now Available!

Hello Logik friends! The Flame Family 2026.2.1 service pack has been released and are being rolled out to your Autodesk accounts. This service pack does not contain any new features, but fixes for the issues listed there: Flame Family Fixed Issues (2026.2.1) Enjoy!

[allklier]

Fix in dot release in 5 days. That’s impressive.

[philm]

agreed - a clear demonstration that this is a world class outfit

[eddiead]

Upgrading and testing today. Impressive turnaround time from the dev team!

[andymilkis]

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!!

[davejahns]

Agree - thank you so much!! Made a huge difference for me as well. Project saves went from 2-3 minutes to about 10 seconds!

[kyleobley]

I’d be curious to know what it was that was causing the slow saves…

[philm]

@kyleobley