Many users are running these Flame Family products on these OS without issue. The error you see seems related to permission. As stated in various discussions on Logik, Full Disk Access is required for Flame and it services. If you use removable storage, you might need to recheck the Full Disk Access if the disk are re-mounted.
Which version of Flame do you run?
If you use Service Monitor application, you can run diagnostics which will show you information about issues.
I thought maybe it was because I’m not home with my NAS and other SSDs plugged in. And he tries unsuccessfully to launch the volumes. But I find it strange because I only work on an SSD that I plugged in.
ok, i found the problem !
I edited the setup text file and disable partitions of the volumes that are not present at the moment (NAS, other SSDs…).
So i Get only the partition of SSD i have right now with me.
I restart Flame and everything is ok.
Maybe it will be nice to implement it on Flame futures update :
Not blocking volumeMGT initilisation at project launch is other partitions (not used) are not plugged.
Happy to hear you are up and running. From what I read, you have a portable workstation / laptop and you have volumes located on a NAS and SSDs that are not available when your are away so Flame / Volume Management cannot see the NAS since it might be the first volume and then you are not able to start.
We will have a look.