Slicing Failed

[DKiefer770]

Application Version

5.2.1

Platform

Windows 11

Printer

Anycubic MegaX

Reproduction steps

Attempted to slice.

Actual results

Slicing proceeds all the way to end the sometimes, but then resets. Now I am getting "Slicing Failed" dialog box.

Expected results

Slicing should complete normally.

Checklist of files to include

• Log file
• Project file

Additional information & file uploads

AI3MX_Stubby Cubical 6.zip

[GregValiant]

Thanks for the report.
I can't get it to slice with Tree Supports turned on. It did slice in 5.2.1 with normal supports and Cura says the print will take 17 days. I have to question your decision to go with a 0.10 layer height on a model this large.

This is one of those odd models that don't show errors but the on-line STL repair utility I used did make some changes.
-> Vertex count changed from 7683 to 3968 (-3715)
-> Triangle count changed from 14506 to 8032 (-6474)
I think that's because there are 241 separate meshes in the model.

4.13.1 took 18 minutes to slice the merged model with tree supports and then promptly crashed. It reported a 15 day 8 hour print.

All in all I'd say this model is not suitable for FDM printing. The outside looks to be simple but Internally it is extremely complicated and supports are a real problem. I don't see any way to get the supports out unless they are PVA.

This image is from 5.2.1 with normal supports and after merging all the separate meshes using MS 3D Builder. When I used one of my high speed profiles this would still take over 100 hours to print.

[DKiefer770]

Thanks for response. I thought I was pushing the envelope here. I really don’t want to remove the supports. This is a lamp design that I print in clear PLA, PETG, ABS, etc. where I want to show some interesting internal structures. In other designs I have (that do not have the internal structures, but just the outer shell), I use Gradual Support Infill Steps (see attached) but I wanted something more consistent. I will try modifying my design (these are randomly/parametrically generated in OpenSCAD) to gut out more of the inside. Clearly the slicer is confused as to what is inside/outside, and what needs supports. This is probably related to my other Issue: 5.2.1 hangs when opening dialogs (Issue #13653). I only see the hangs after I attempt a slicing operation. You can close both these issues if you like. Thanks for your help! David Kiefer ***@***.******@***.***> sine pendulositate nulla significatio From: GregValiant ***@***.***> Sent: Friday, October 28, 2022 7:43 AM To: Ultimaker/Cura ***@***.***> Cc: David E. Kiefer ***@***.***>; Author ***@***.***> Subject: Re: [Ultimaker/Cura] Slicing Failed (Issue #13674) Thanks for the report. I can't get it to slice with Tree Supports turned on. It did slice in 5.2.1 with normal supports and Cura says the print will take 17 days. I have to question your decision to go with a 0.10 layer height on a model this large. This is one of those odd models that don't show errors but the on-line STL repair utility I used did make some changes. -> Vertex count changed from 7683 to 3968 (-3715) -> Triangle count changed from 14506 to 8032 (-6474) I think that's because there are 241 separate meshes in the model. 4.13.1 took 18 minutes to slice the merged model with tree supports and then promptly crashed. It reported a 15 day 8 hour print. All in all I'd say this model is not suitable for FDM printing. The outside looks to be simple but Internally it is extremely complicated and supports are a real problem. I don't see any way to get the supports out unless they are PVA. This image is from 5.2.1 with normal supports and after merging all the separate meshes using MS 3D Builder. When I used one of my high speed profiles this would still take over 100 hours to print. [image]<https://user-images.githubusercontent.com/64202104/198574052-d8782066-93bf-4a81-84c9-a1a82b375504.png> — Reply to this email directly, view it on GitHub<#13674 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALRVHZQLA72TMOQ4QDYEO5DWFO35VANCNFSM6AAAAAARQHP7OA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[GregValiant]

I'll go ahead an close this then. It was an interesting exercise.