Looks like you followed all the main suggested fixes already.
One that may be worth following up on is this
Maybe your temporary install 2024.2.2 left some gifts behind?
Other two things:
Start Flame from the terminal so you get the extra output (unless you tried this already), and in the service_monitor run the various diagnostics and look at the log file from the last crash for additional clues.
And for the proverbial dummy check - make sure you disk isn’t full by chance.
my suspicion is that there was a background cache happening in 2024 that never finished.
oh wait.
you must have used 2024 something something to update the project db on that workstation
oh
and since this is pre 2025 it’s probably still dependent on /opt/Autodesk/project/project.db
If the project database was modified by a newer version, and now you’re trying to read it from an older version you’re kind of done.
you could try updating all of these legacy systems to 2024.
you could try wiping flame 3 and reinstalling flame 2023 but that may leave you with no recourse to get access to flame 3’s projects.
you may have archived everything so it’s an easy fix.
uninstall flame software on flame 3.
remove /opt/Autodesk/project
install flame 2023 something something.
restore from archives.
if you choose to upgrade to 2025 you’ll probably need to upgrade your OS
@MagicMtn - what does your engineering team say?
You are talking with them 
Sorry @MagicMtn not to belittle your problem 
I am my engineering team…
I believe updating the 2023 systems to 2024 may be the ultimate solution but i am waiting for a few projects to finish archiving before taking that step.
I opened a ticket with autodesk and was able to schedule a call with them for the am incase I cant resolve it this evening.
version 2024.2.2 was installed on f3 only to open a newer project we weren’t able o access from a freelancer. my understanding is thats the only time we used it but It sounds like the problem we have now is possibly related to this update.
@MagicMtn - it sounds like you’re doing all the right steps.
Removing a 2024 project from a 2023 environment is problematic.
However, once you’e completed the 2023 archives you might consider installing 2024 and updating your 2023 projects.
updating to 2025 will include an OS upgrade to at least macOS 13 (again problematic since it’s not supported by apple) and macOS 15 is about to drop.
You may be at that reluctant moment where you need to upgrade everything, all at once.
Archive everything and check the archives.
Then consider getting on the today train and updating everything.
Happy to report Autodesk fixed the issue in about 15 minutes this morning.
The person I spoke to had already read this entire thread.
I told him the suspicion of 2024 version writing to the 2023 database may not be entirely accurate description of what happened. He believes the more likely case was that flame 3 was accessing a project on flame 1 during an unexpected restart. This locked the database of flame 1 giving us the errors we see in the original post.
The lock was found in the directory /opt/Autodesk/Projects
once the lock was removed and a VIC was run we were able to open the projects successfully with no database errors.
Support said they would write an article about this type of issue since nothing exists on there site about it. When available, I will repost here.
This info may however only be relevant in versions 2024 and previous as my understanding is the file structure changes a bit in 2025.
Thanks for all the help and suggestions getting this resolved.
@MagicMtn - hurrah!
oh wait, now you have to get back to work.
boo!
Thanks for the follow-up. As a longtime member of this forum, and those previous, I can say that my ass has been bailed out by follow-ups a number of times.
It was nice to speak to you today Jonathan, and glad we were able to narrow down the cause swiftly.
I will write a new article today about this, and share the link here once done.
Mark - Autodesk in London, UK 
Here we are:
Let me know if you spot any issues and I’ll fix them!
The Dude abides!
Are you truing to kill Flame? if so, macos would be pkill flame and linux should be something a kin to kill $(pidof flame).