Yesterday I was printing a large print from Bambu Studio. Today (while working remote) I cannot open any 3mf or stl file. All files result in two error messages:
“The file does not contain any geometry data”
and
“Loading of a model file failed” (only when opening 3mf)
I have tested with loads of 3mf and stl files but I am unable to open any file.
I have searched this forum but cannot find any solution.
Bambu Studio version is 1.9.3.50
I don’t know what has changed since yesterday except I’m not at home right now. Studio version was already updated weeks ago.
Any suggestions would be greatly appreciated.
1 Like
I am experiencing the same problem with one 55MB 3MF file, and have never experienced this problem before, since the purchase of my 1st X1C approximately 18 months ago. On 9-7-2024 I had printed from the subject 3MF file, then tried loading the file the next day to print from it again, and it spawned the subject error. Also, in my case, Studio is not having a problem loading other 3MF files.
Notably, where it generally would take Studio maybe 3-4 seconds to load / process the 55MB file to then display it in the viewport, it now spawns "The file does not contain any geometry data” error a moment after I invoke the file load. This implies that Studio does not recognize the file for whatever reason, either after reading the file header, or in the initial lines of code it encounters following the File Header.
On a side note, the "The file does not contain any geometry data” error is a misnomer, because it does not actually check if there is geometry code, it is simply spotting some kind of file read problem (“corrupt,” as from an SSD write error, may be too strong), and the problem is that Studio does not recognize the file. This is provable simply by taking a non 3MF file, changing its extension to 3MF, and then trying to load the file, and Studio will immediately spawn the same error. It would be more accurate if the error read, “File type not recognized,” or, “File type not recognized, or file is corrupt.”
On a side note, and to mitigate any users posting a reply that having a file back-up scheme engaged would have alleviated the problem, such is not correct. I actually have both Google Drive and Windows Cloud backup engaged on the local drive, but backup software merely duplicates files, INCLUDING any offending code (corruption) 
. The only way to mitigate the potential for this problem is through the use of backup versioning, either via manually saving copies with different names, or utilizing automated backup versioning software. It would be a valuable feature if Studio (and Orca) included a setting for Auto Versioning Backups.