-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clip SliceFail #17532
Comments
Correct Win11 |
I've noticed that myself. I read an interesting article that might have some bearing on this. It was about the tendency of computer manufacturers to over-clock their processors trying to squeeze out more performance. Since newer machines are more likely to be running Windows 11 the article got me thinking if the problem might have some basis in that over-clocking. It's a subject that I know nothing about, but it was an interesting take on something that might be going on. |
Interesting. Could be related. My machine by default runs a bit above clock speed. That being said, I think this is something Cura/Win11 interaction related. I can slice this part on 5.4.0 but 5.5.0 and 5.6.0 both produce the slicing error. To me, this points to some change in Cura 5.5+ |
Unsure if those are duplicates or not. Not created by me but they seem to all be relatively thin parts facing slicing issues with Win11 on cura 5.5 or 5.6. Could be same issue in cura. |
Processor: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz 3.00 GHz |
We made some improvements to prevent slicing fails in Cura 5.7.0 available to download now. I was able to slice your model successfully in 5.7.0. Could you test if that's the case for you as well? Feel free to reopen the issue if it is not resolved. |
Cura Version
5.6.0
Operating System
Win11
Printer
Ultimaker S7 Pro
Name abnormal settings
Non that I am aware of
Describe model location
Rotated 90 deg to flight
Describe your model
Sliced successfuly in 5.4.0
Add your .zip here ⬇️
Project file
UMS7_Rail Clip V2.zip
The text was updated successfully, but these errors were encountered: