hey there Autodesk. I hope you are getting all my crash reports. there has been quite a few. mainly around rendering
From previous issues, Iâve heard that the crash reports include limited data, and in itself I donât think trigger any action, but can be referenced if you report and issue.
If you have a serious problem, you have to open a support case. I wouldnât expect them to look at your crash reports otherwise.
I was having multiple crashes one evening and I got a phone call from @JFb asking if everything was ok . . . Yup, those days did exist.
3 Likes
We do look at every crash reports. Sometimes, they are enough to help us figure out what is wrong, but more often than not it can be specific to a setup or configuration and having someone from support investigate the issue is the best way to have it solved.
1 Like
Im getting tremendous problems with non cache material and renders. Checkerboards appearing all over the place. Crashing and having to force quit. Itâs all over the place. Im trying to deliver a job so not really possible to sit there and think about whats going. Other than it appears to be losing its source material and renders.
Im just trying a fresh project now and starting again,. The other one was a converted project
also I will go away from the desktop - then come back and all the frames have
disappeared
. if you then whizz up and down the clip they will come back. very alarming.
@Jonhollis - does the mac have an option to put external disks to sleep when not in use?
Volume integrity check has been deprecated.
I think the new tool is called integrity check.
Itâs in the docs somewhere.
Maybe here
Iâve been banging away n this stuff since November and havenât seen what youâre seeing.
My workstation is now 16 years old, definitely not bleeding edge like yours.
All I know is none of this happened with 2025-2-2
2026 does not use âframestoresâ as we have known them for the last 30 years.
Now there is a media cache - sort of like a vanilla framestore.
Media cache still has some of the clever adsk functionality but discards some of the legacy inefficiencies.
There will be some bounciness on this flight.
Itâs peculiar that you are having issues with a brand new project though, since this does not drag any baggage.
Iâm curious if there are some energy saving toggles in macOS that may cause your storage to sleep?
Itâs not probable that the fault is with stone and wire necessarily since this is not really in play any longer.
Without rooting around in your system I have no clue.
Maybe support will help you after delivery?
I remember that in the past they would help you to successfully make the deliveryâŚ
Im going back to 2025 - this sucks big time. Itâs totally trashed my project. I was in the type tool and it crashed and now I canât access that project at all
I havenât got time to go through calling support. I need it to be rock solid
1 Like
I think @philm is on the right path.
Quite a few folks have run 2026 without the type of instability youâre describing. That is not to discount your pain at the moment, the pain is real. Itâs quite likely that there is a pecularity in the way your system is setup that is contributing to these crashes. Support will have to find out what that was, as it may also affect others that happen to have the same circumstances.
But for now going back to 2025.2.2 seems the right move. An upgrade to a major release always comes with some uncertainty and some testing is required to make sure your system is stable.
It sucks that this happened, but itâs not out of the ordinary, and doesnât make this release or Flame any worse than others. Working with support on this can consume time, and if this is your only system can be tricky when youâre on deadlines. So hopefully going back to 2025.2.2 will give you back your sanity.
Sorry was very frustrated there. I let it get to me. Nothing set unusual on the Mac. Only thing is itâs the new M3 Ultra.
jh
1 Like
I assume the new M3 Ultra comes with Sequoia? Which is supported by Flame but only recently and with limited mileage I assume. I wonder if thereâs some peculiarity of that OS version that hasnât been totally worked out. I believe it has some new weird security features.
Funnily enough, I just saw a variation on this very problem on another Mac Studio on the other side of the planet.
When 2026 gets installed it overwrites many of the 2025 service preferences.
2026 services are not entirely backwards compatible with 2025.
Since the work required compatibility with flame 2025.2.1 it was necessary to find a solution that permitted this version of the software to run and render.
The solution was to uninstall every version of software, remove some residual 2026 directories and configs, then install the appropriate version of software.
And now that flame is back in businessâŚrearranging pixels for moneyâŚ
Which is good.
The Mac 2026 uninstaller is not so good and leaves residue.
Maybe thatâs a case for an improvement/feature request - but iâm tired - itâs been a long day.
So are you saying it needs a fresh install?
As soon as Iâd written the post we discovered something else, which might point to the NAS hardware or perhaps a potential NAS/network/firewall misconfiguration.
Fortunately logik projekt was already in play so we just changed infrastructure and carried on (transferred NAS data to a local DAS, re-pathed /PROJEKTS and pressed âplayâ) this means that the NAS can be off lined and analyzed.
Itâs hard to know how to fix your problem since I have no insight into your system configuration.
1 Like