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

Crash on slicing stl but slicing repaired stl is working #8760

Closed
1 of 2 tasks
tcjtomas opened this issue Aug 25, 2022 · 5 comments
Closed
1 of 2 tasks

Crash on slicing stl but slicing repaired stl is working #8760

tcjtomas opened this issue Aug 25, 2022 · 5 comments

Comments

@tcjtomas
Copy link

Description of the bug

When loading a simple stl and slicing it fails.

Repair stl, load the saved obj file and slicing it works.

Project file & How to reproduce

Load stl and slice causes silent crash

Load stl repair it

Save obj file

Slice is successful
Adapter.zip
l

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

Version 2.5.0-rc1+linux-x64-GTK3

Operating system

Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-150300.59.90-default OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 7,7 GiB

Printer model

Prusa i3 mk2 reprap

@kubispe1
Copy link
Collaborator

Hello, thanks for you issue report. I think, your model is somehow broken (but just little bit).
But it doesn't apologize the crash of PS. I tried problematic .stl on WIN 10 and that worked.
image
So, please can I ask you to try this steps for us?:

  1. Try it in 2.5.0-rc1 with Classic perimeter generator (Print settings/ Layers and perimeters / Perimeter generator)
  2. Also try it in 2.5.0 alpha3 with Arachne engine.
    This would help us to detect or filter some cases.

hejllukas added a commit that referenced this issue Aug 30, 2022
This was caused by mistakenly swapping the key and the value in a vertex map.
@hejllukas
Copy link
Collaborator

Hi, we fixed the artifacts shown on this model when Arachne was used with the commit 614cd70 in master_250.
But we weren't able to reproduce the crash that you mentioned. Could you please try this attached build and report back if it is still crashing or not?
PrusaSlicer-2.5.0-rc1+17-linux-x64-GTK3-g614cd70-202208301031.AppImage
PrusaSlicer-2.5.0-rc1+17-linux-x64-GTK3-g614cd70-202208301031.tar.bz2
If it will still crash with this build, could you please upload 3MF exported before the crash?

@tcjtomas
Copy link
Author

tcjtomas commented Aug 30, 2022 via email

@tcjtomas
Copy link
Author

Hi Team,

It slices with PrusaSlicer-2.5.0-rc1+17. No issues. And futher more the artifacts are not showing.

Well done :)
This issue can be closed.

BR
Tomas Jensen

@hejllukas
Copy link
Collaborator

Thank you for testing it and reporting back. So I'm closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants