Page 1 of 1

[FIXED] no retraction crashes s3d

Posted: Sun Mar 24, 2019 2:49 pm
by styldesley
Attached a factory file. Generally any object sliced with no retraction crashes s3d (for me). What am I doing wrong? Would like to slice without retraction. Thank you.

Narrowed down the problem

Posted: Mon Mar 25, 2019 1:46 pm
by styldesley
No retraction on right extruder means crashing s3d. No retraction on left extruder and no crashing. Any object , any profile.

Flashforge creator pro 2016 plus

Posted: Mon Mar 25, 2019 2:19 pm
by styldesley
Stock flashforge creator pro profile, with only one change , no retraction on left extruder will also crash s3d. The above factory file is a modified creator pro profile.

Re: no retraction crashes s3d

Posted: Mon Mar 25, 2019 3:19 pm
by horst.w
Works fine for me. No-retraction itself can not be a reason to crash S3D. Version 4.1.1 crashs often without identifiable reason. Close and restart the program and store a factory-file before Prepare to Print. Than it needs only to Open the Factory-file and try again.

The overhang needs support, it seams to flat.

horst.w
GER

Re: no retraction crashes s3d

Posted: Tue Mar 26, 2019 1:31 pm
by S3D-Jake
Try the tips suggested by Alex in this thread: viewtopic.php?f=9&t=11924&start=10#p48068

Re: no retraction crashes s3d

Posted: Sat Apr 06, 2019 9:34 am
by styldesley
4.1.2 fixed crashing with no retraction. No long delay. thank you s3d

Re: no retraction crashes s3d

Posted: Mon Apr 08, 2019 10:15 am
by S3D-Alex
styldesley wrote: Sat Apr 06, 2019 9:34 am 4.1.2 fixed crashing with no retraction. No long delay. thank you s3d
Thank you styldesley! You beat me to it! This issue has been fixed in 4.1.2. A special thank you to everybody that helped by reporting the problem and helping us get to the root cause. Crashes with retraction visualization while retractions are disabled will no longer be a nuisance.

We are always working to improve the efficiency and seamless nature of our product and your help is invaluable. This fix was one of many that occurred with this new version. Please check out our Release Notes page.