Just a thought here. But are you trying to launch a Project from a higher version of software? For instance, did you run this project in 2026.2 but now trying to launch it in 2026.1?
I havent - im delivering on a couple of other projects at the moment. So will try some things tomorrow when things have calmed down!
so I archived the project - set up a completely new project on a different drive and different cache and the same thing is happening with that one. now it crashes all the time when launching the new project. also support never got back to me!
Could you share the case number?
25196496
Let me check
There is the following error message that is kind of explaining the issue:
[error] 2130669568 CoDirectIO.cpp:500 12/17/25:17:20:54.084 Unable to write 49807360 bytes to ‘/Volumes/Thunder1/Thunder1-Projects/Eco Outdoor/Eco_Outdoors_flame1/media/9/0x000002e400000094.raw’: No space left on device
Time to clean up the storage and make some room.
I realise that. And I did. But why has it killed the whole project. Thats not very robust software is it. Why didnt it just say no space left on the device - or even hitting render will fill your drive etc etc. something a bit more cleve than killing my project
Do you store the project home and the media cache on the same storage?
The error message says that the metadata of the project was probably not written to disk due to space issue. Since you are working with RAW format for your cached media, these frames are large and can fill up a storage quickly. Using a different location for your project home would have triggers a warning when rendering.
I do
This is not a bad practice BUT you are saving small files (i.e. metadata) and large files (cache) to the same storage location and this might not be best for playback performance.
We will provide more error reporting for such case in future updates. For now, be careful to not fill up the storage.
I can split it as I have two thudnerblade X12s - these do go at 6500mbits so they are super fast
For people searching for this error in the future:
PROJECT: Integrity check failed: Unable to extract frameids from libraries.
-Ted
I should also say - im only using cacheing so much still as there isnt a bloody relink function. I would run all my projects with non cached and the rushes and artwork etc etc in folders I create. but with no usable relink I cant trust it will ever work again if I move to a different flame system. I mean look at resolve (or any other NLE) perfect solution for this. I go to the top level of the project and hit relink all files and it relinks them all. easy. you can mess with your folder structure anything you want - and the software just finds the clips.
Yep. Ever since Flame, and, in a way, most of us, commited to an unmanaged media workflow, yes, flame need a bulk relink/consolidate/convert tool for manage projects.
Moving forward, please use detailed topic subjects and in addition to screen grabs, copy and paste error messages so they become searchable and findable for future you and future colleagues.
word.
I get around it with symlinks mostly but there is another hack.
If you write all your media out as openclips , the openclips point to the file - you can change the path inside of the .clip files to whatever you want.
anyone wants a flame-openclip relink utillity? lol.
I really only need to it when moving things across projects, like I just had “car commercial2” use shots from “car commercial1” but they also of course gave us new graded files for the old shots of “car commercial1” so i had to re-run them through the shots setups → boom bam batch changed the paths in the openclips and the batch files with a simple search and replace script so that everything would
be contained in “car commercial2”.