Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.1k stars 2.06k forks source link

Slicing Bug, Cura is asking to be reported here #13483

Closed nissaba closed 8 months ago

nissaba commented 1 year ago

Application Version

5.1.0

Platform

Mac OS 12.6

Printer

Anycubic I3 Mega S

Reproduction steps

use plugin to auto-orientation optimal speed then slice

Actual results

got an erre asking to report this bug.

Expected results

to get the object sliced

Checklist of files to include

Additional information & file uploads

AI3M_Drone_parts.3mf.zip cura.log.zip

GregValiant commented 1 year ago

Thanks for the report. Cura 5.1 has a bug on Windows installations but this might be the first report of it happening on a Mac computer. The bug seems to have been fixed in 5.2 for Windows. If you Group the models and then move and rotate the group on the build plate you may very well get it to slice. Someone from the Cura team will take a look at this. I rotated the group 90° and it sliced. image

nissaba commented 1 year ago

Thanks for the report. Cura 5.1 has a bug on Windows installations but this might be the first report of it happening on a Mac computer. The bug seems to have been fixed in 5.2 for Windows. If you Group the models and then move and rotate the group on the build plate you may very well get it to slice. Someone from the Cura team will take a look at this. I rotated the group 90° and it sliced. image

Yes I did move the parts after opening the issue, and it did slice. My guess is that the item where place in a way that it can't arrive to a solution. I normally let Cura place the items on the place using r-click arrange all models. For this I used the extensions to get the optimum orientation then got it to auto rearrange the items, that failed then I moved things a bit and this worked.

jellespijker commented 8 months ago

Thank you for your report. It seems that your uploaded project file slices correct on our latest unreleased 5.7.0-alpha.0+3abb5 which indicates that the issue you're experiencing seems to be fixed for the upcoming 5.7.0 release. I'm closing this issue as fixed for the 5.7.0 release

image