unable to parse print file (0500-4003 152625) since upgrading X1C to 01.08.50.18

[nordurljosahvida]

Bambu Studio Version

2.0.3.54

Where is the application from?

Bambu Lab Official website

OS version

Windows 11

Additional system information

unrelated

Printer

X1C

How to reproduce

Very hard to reproduce (nice start, i know!)

Since updating our first X1C to the new firmware (both the general update to the new interface and also the subsequent update it ran right after) I cannot print to the machine if I include a file in the project that originates on my filesystem. If I add a shape from within bambu or open a 3MF from the in-bambu MW discovery (I'm aware that that downloads the 3MF to downloads folder, but that is not affected), that works.

The exact error is: printing stopped because the printer was unable to parse the file. please resend your print job. error code 0500-4003 152625

I've managed through about 1H of trial and error to narrow down the issue and I've produced two identical 3MFs that perfectly show the error, as one always works and the other always doesn't.
I've ran the risk of upgrading another X1C knowing that would render it offline until this is resolved for science of course, and the results are entirely consistent with the first one.
I've expanded the two 3MFs and as expected the only difference are these metadata lines which do in fact reference the origin of the file on my FS:

Attached is the zip of the two 3MF files.

I cannot understand which logic bambu is using to sometimes include these lines and sometimes not.
It is of course also possible the other lines apart from the path line are causing the issue.
However it is curious that the issue started only after the new firmware upgrade.

I basically cannot use 2 of our 4 business' carbon printers. Please help :)

Thanks!

Actual results

It works

Expected results

It doesn't

Project file & Debug log uploads

fs logo.zip

log_iotc.zip

https://drive.google.com/file/d/1ZfGHNgrjS401AAZu6YeKk7Cvk3VxLYnf/view?usp=sharing

Checklist of files to include

• Log file
• Project file

[nordurljosahvida]

A quick update: (referring to the lines in the winmerge screenshot) simply removing the "path" lines manually doesn't fix the problem.
Removing all metadata key=source_[...] lines works.
For anyone having the same issue:
3MF is basically just a ZIP file.

on Mac: there should be a "show archive contents" where you should be able to modify the files directly. otherwise extract, fix the file, recompress, as in windows steps below.

on Win:

1. rename the problematic .3MF file to .ZIP instead (confirm when warned about the extension change).
2. right-click > extract here
3. open the folder and in the file structure look for the model_settings.config file inside the Metadata subfolder.
4. remove all lines in yellow in the screenshot I posted above (all metadata key=source_[...] lines) for each model
5. close the file
6. select all folder contents (_rels, 3D, Metadata, [Content_Types].xml, and anything else) and right click > compress to ZIP file
7. it's very important that you select the individual root-level items as shown above and not the containing folder (named like the original 3MF file) as that will create an invalid modified 3MF
8. rename the newly created zip to .3MF, ensuring of course to add "edited" in the name also as to not conflict with the original 3MF
9. optionally move the newly created 3MF file up in the containing folder as to return to the same folder level of the original 3MF (you'll likely still be inside the folder created by the original unzip)
10. open the newly created 3MF, do not save for any reason, and send to your printer

on Linux: do something similar

[aneopsy]

I'm having the same issue. I use LAN developer mode.
I suspect that online mode fixes the issue when the file is uploaded to the BBS server, where it may be modified before being sent to the printer.
I have this issue with BBS and Orca. It looks like the issue is related to the original object file because sometimes exporting it with different software and changing the file location fixes the issue.
One quick fix is to export the file as a generic 3MF file in your slicer and then open the new file with your slicer.