Chitubox Slicer is VERY VERY broken [EDIT - it's "network send"]
10 Months+ 1659
[EDIT] - it's the "network send" feature - it corrupts files, see next reply/post from me on this topic for details. Elegoo, seriously, you couldn't figure out how to safely copy files over ethernet?
Randomly the slicer will go completely haywire - take slices out of the model, mirror them, and put them on the opposite side of the build plate. At the same time it generates rectangles that cover the entire build plate. See the image above. The worst part is, it's random, sometimes the slicer generates a valid print like this one
, and sometimes with the exact same settings, it makes slices like in the image.
This ruins prints. It also ruins FEPs and after only a week with my Saturn, it has already damaged my screen. The broken slices with the giant rectangles ripped parts off their supports which where then crushed against the FEP and screen by the parts that were still attached to the build plate.
When the slicer fails like this, it doesn't show in the 3D preview. In order to see broken slices, you have to save the slice file, and then re-import it.
Here is the file that was used to create the broken slice file in the image above: https://drive.google.com/file/d/1Ihm5V-KCZwPV71EnpNS-BWOKd-wMu1Ev/view?usp=sharing
I only recently figured this issue out - but already I can say it's happening a lot - all 3 of my most recent prints with completely different files have this issue.
I can confirm this bug. I tested Network Send on 1.6.5, 126.96.36.199, and 1.7. Sending through a stock comcast modem to an Epax X1-DJ. I eliminated all hardware causes with Epax's excellent customer support (multiple printers, screens, and mainboards). I can recreate the issue by slicing with any of those versions of Chitubox, then Network Send to printer. If you print the file, the preview looks fine on the printer. It didn't hurt my printer other than ageing the screen unnecessarily (unlike the OP), but did create big 'flaps' of resin off the model. I've photographed the print screen during numerous dry prints, as well; it matches what the OP is showing. If you take the USB back to the computer, and open the *.ctb file, you can see the problem layers in the preview. I can work with you on identifying the problem. Let me know what you need.