.pwsz M7 Pro, saves but Anycubic detects corruption

[Blacky95129]

System

UVtools v6.0.3 X64
Operative system: Microsoft Windows 10.0.19045 X64
Processor: AMD Ryzen 5 3600XT 6-Core Processor
Processor cores: 12
Memory RAM: 8.95 / 31.93 GB
Runtime: win-x64
Framework: .NET 10.0.5
AvaloniaUI: 11.3.13
OpenCV: 4.12.0

Path:       C:\Program Files\UVtools\
Executable: C:\Program Files\UVtools\UVtools.exe
Loaded file: flox + extra_02h57m_133ml_copy1.pwsz [Version: 0] [Class: AnycubicZipFile]

Printer and Slicer

• Printer: M7 Pro Anycubic
• Slicer: Anycubic Photon Workshop 4.1.4

Description of the bug

Hi, I wanted to let you know that I've recently been correcting files with UVTool and saving them correctly, but when I try to open them with Photon Workshop, it gives me a corrupt or no model error. I reopened the file with UVTool and everything is fine. I tried again with an old file for the M7 Pro that I'd corrected with UVTool and then opened after saving with Photon Workshop (which worked normally and happened recently), but it still gives me the same problem without changing any settings.

How to reproduce

.

Files

No response

[github-actions]

This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌

[sn4k3]

Can you revert to v6.0.1 and try out? I did reviews to format to implement missing keys and a new file that was introduced with new machines. Other than that structure did not change.

[CorpseGrinderBD]

Confirming i also am running into the same issue after updating to 6.0.3.
Printer M7 Max - Anycubic Photon Workshop 4.1.4

Version 6.0.2 UVTools has error during file load up.

[CorpseGrinderBD]

Version 6.0.1 UVTools working.

[sn4k3]

@CorpseGrinderBD Ok, can you now use latest UVtools to save file, then open file as zip, remove the calc_layer_volumes.data file from zip, rename back to original extension and try to open in Slicer?
That file adddition was the biggest change in the format.