Skip to content
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

Crashes Depending on Part Orientation #4428

Open
muckmed opened this issue Sep 27, 2024 · 4 comments
Open

Crashes Depending on Part Orientation #4428

muckmed opened this issue Sep 27, 2024 · 4 comments
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build

Comments

@muckmed
Copy link

muckmed commented Sep 27, 2024

Version

Occurs on 2.5.60.0 & 2.5.59.9, I assume other versions as well.

Operating system type + version

Windows 10 Home Version 22H2 64 bit

Behavior

Attempting to slice the attached file in certain orientations results in a crash. Occasionally, SuperSlicer will display the message shown in the photo below.

image

My temporary workarounds:

A. Orientate the part vertically before slicing. No longer crashes, but printing isn't feasible.

B. Import part -> Right click part -> Add part -> Box. Once the box is added the part will slice successfully in any orientation. HOWEVER, if the height of the added box is less than the height of the "Blower Fan Shroud" part, it will crash. The box must be at minimum 1 layer larger. In this case, on a .2mm layer height & default orientation, the Blower Fan Shroud part is 12mm tall after slicing. A box 12.2mm or taller will allow the part to be sliced. Box does not need to intersect the part.

Project File (.3MF) where problem occurs

Blower Fan Shroud.zip

@JohnEdwa
Copy link

I've found a few models as well that crash or fail to slice on 2.5.60.0 depending on orientation, maybe they can help nail down the issue. Trying to slice the calicat in the normal orientation throws that error and shortly afterwards force-closes the program, while trying to slice it standing on its head throws the same error, but without a crash, until you try again.

The last processing step before it freezes is always "Computing seam visibility areas: object 1/1.", and crash_log.txt is not generated.

SS_2.5.60.0_orientation_crash.zip

@starsolaris
Copy link

Another example
SH72_extension.zip

@supermerill
Copy link
Owner

I'll try to find a little time to work on the 2.5, to have a more stable stable release.

@supermerill supermerill added the bug Something isn't working as intended label Oct 1, 2024
@ExploiTR
Copy link

ExploiTR commented Oct 4, 2024

Same issue - crashing at compute seam visibility.

@supermerill supermerill added this to the Todo with 2.7 merge milestone Oct 12, 2024
@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Oct 13, 2024
supermerill added a commit that referenced this issue Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build
Projects
None yet
Development

No branches or pull requests

5 participants