Simplify3D User Forum

Hello there,
Yesterday a strange problem kills my mind. I try to slice Baby Groot from Thingiverse. After slicing in 0,05mm i try to copy it on my SD-Card but S3D gets crashed. After restart S3D all my process file are gone. Not a big problem. Sliced Baby Groot again and copy it to the SD-Card. But now i get on every print the warning on my Prusa which said

File Incomplete. Continue anyway?

I try to reset S3D but nothing works. After that i reinstall S3D but the problem still exist. Someone have an idea? Slicing with Prusa Control and Cura works fine without an problem. So i think S3D has an problem after the crash.

Can you post the gcode file here that is giving the warning? Maybe that will help see what's wrong.

I'm having a same issue. The gcode that's created for MK3 says it's incomplete when trying to print from SD card. Also, not sure exact problem but same happens when printing from repetier server. Tried few different stl files but same problem if stl file is big object:

stl files that gave incomplete files when sliced:
1) https://www.thingiverse.com/thing:2770388 - failed
2) 240mm width vertical and curved lithophane picture with 3mm width
3) stormtrooper bodies.

Successful stl:
1) Destiny ghost smaller parts (body and lights) https://www.thingiverse.com/thing:527736
2) Chibi Grim Reaper - https://www.thingiverse.com/thing:2360057

Profile used is Josef Prusa's mk3 profile shared on prusa forum: https://shop.prusa3d.com/forum/original ... 12950.html

Also, I noticed that:
1) when you open the problem gcode file, it has a bunch of null at the end of the file.
2) File size is all 65,536KB (see attached picture).

Sounds like you need to upgrade to 4.0.1. I think this was something that was fixed in that version.

Login to your account on the simplify3d website and you can download the latest version

Yes, do the upgrade to 4.0.1 and it should fix issues with files over 64MB.

As was said earlier, log in and download version 4. It will say 4 but the file name should say the correct version.

After I posted, I noticed a 4.0.1 version. Installed the update and I was able to print.

Thanks!

As other users referenced earlier in this thread this issue should be resolved now in the latest 4.1.0 release. Our team successfully tested several factory files from threads mentioning this issue. These large gcode files will now be written with no issues. This was just one of many improvements to the software. All of which are detailed on our Release Notes page.

Thank you for your help reporting this issue!