Unexpected slicing error.

Jolnear commented 6 days ago

Cura Version

5.7.2

Operating System

Windows 10

Printer

Creality CR-10

Name abnormal settings

Fails with default

Describe model location

I have moved it around, rotated it, etc.

Describe your model

It is watertight. I can slice it weirdly if i shrink it 20%.

Add your .zip here ⬇️

cura.log https://we.tl/t-CfkiAWB3Lv

We are back again with more slicing fails. I upgraded to the newest edition. It will slice if I go 20% smaller. I have tried disabling my antivirus (Windows Defender) and moving it around. Its probably just a me issue but I'm hoping the log fixes something for someone else. It won't print on the standard settings either let alone mine.

GregValiant commented 6 days ago

Thanks for the report. This is a generic error code from your log file. "Backend exited abnormally with return code 3221225477!" MS 3D Builder complained about errors in the model, but the model sliced OK for me as received.

The Cura team will take a look.

Jolnear commented 5 days ago

As a weird update, it will slice with low profile but not standard/dynamic/super built in profiles (or my custom).

I also changed the layer height and that seems to affect the slicing.

GregValiant commented 5 days ago

There might be a tiny error in the model and when the combination of Initial Layer Height and Layer Height is just exactly right the slice hits the error and the crash happens. That's my theory anyway.

If there is a small gap in a model and it falls below some minimum within Cura, then the gap gets ignored. If you scale up the model then the gap gets scaled up as well and can become large enough that the slicer notices, gets confused, and quits. That condition I know happens.

Jolnear commented 19 hours ago

I will say it seems to be more associated with the size/amount of filament. Small models are way more likely to slice. Anything that starts to get bigger seems to struggle. If you guys have a model that you think is good that is larger I could try and slice that if it helps you diagnose any problems and help fix them. I would like to be able to slice without issues haha.

GregValiant commented 16 hours ago

Nobody likes buggy software. I don't, you don't, and the developers don't. I'm retired and this is a hobby for me. I spent a lot of years as a tool designer and as a forensic engineer which is what got me sucked into doing the triage here. I learn a lot doing this. I've sliced 200mb files with no issues whatsoever.

I've been accused at various times of being given "special" releases of Cura, and of having access to some sort of "magic" software that fixes everything. I have noticed that I don't have near as many problems slicing as some people do. Why that is I have no idea. This is a second hand laptop that I got for cheap, and my printer is an Ender 3 Pro that I got for cheap. I don't have multiple monitors, raspberry PI's, Octoprint...nothing fancy at all. Things just work.

Consider that hundreds of thousands of printer owners use Cura. There are currently about 3 bug reports per day coming in and they are often (75-80%) because of bad models or inappropriate user settings. I think that is a pretty good record. Knowing that you are in the 25% minority is no comfort. People just want to print.

Your generic "won't slice" problem could be because Cura didn't quite install correctly, or there is some sort of interference with your Windows installation. The problem came up a lot more with the 5.5 and 5.6 versions of Cura. It's something I've never been able to duplicate but it certainly happened a lot. It does appear to be system specific which makes it really hard to troubleshoot from afar.

All the bug reports are taken seriously but getting to them is a matter of priorities. Resources at UM need to be allocated and a priority list made up. I don't know how many people are on the Cura Team, but it isn't many. Along with Cura there are the Github and UM Forum websites, Thingiverse, firmware for several different printer models, 'How To' articles to write and update, and then there is Cura itself which is arguably the most difficult piece of software. 5.7 was a nice change from the problem-ridden 5.5 and 5.6 versions. We are probably not far from 5.8 and hopefully it will be another step in the right direction.

Jolnear commented 16 hours ago

Sorry yeah not trying to complain just posting things that I notice in the hopes it gets fixed for future and/or if people have anything to try that maybe I haven't. I understand I'm a real fringe case here haha. Tbh idk how I would tell if model is good or not so didn't want to say it was (it say's its watertight but dunno if that means good model) and if someone had a "good model" then wasn't sure if that would help narrow things.

GregValiant commented 14 hours ago

Prusa has some sort of deal with AutoDesk and the NetFabb repair utility is available from within PrusaSlicer. It's pretty good. I use MS 3D Builder for repair. The utility is good and the app itself is very good for altering STL files. It isn't intuitive, but it does work well. One website that I still use is https://formware.co/OnlineStlRepair. It gives a report regarding what it may have found that was wrong with a model. That's nice to post here. The site has a file size limit of about 25mb.

Ultimaker / Cura