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
Jump to bottom

Cancel slicing takes too long #6253

Closed
zakutin opened this issue Mar 22, 2021 · 6 comments
Closed

Cancel slicing takes too long #6253

zakutin opened this issue Mar 22, 2021 · 6 comments

Comments

@zakutin
Copy link

zakutin commented Mar 22, 2021 •
edited

Version

2.3.0+win64

Operating system type + version

Microsoft Windows 10 Pro (Version 10.0.19042 Build 19042)

3D printer brand / version + firmware version (if known)

N/A

Behavior

  • Describe the problem
    Cancel the slicing takes too long, when slicing with 10um resolution.
  • Steps needed to reproduce the problem
    During the slicing click Cancel.
  • Expected Results
    Cancel the slicing shall happen instantly, completely dismissing all background processes without any delay. Cancel is cancel. No wait. Cancel was working instantly in version 2.1.1.
  • Actual Results
    Cancel process lasts 1-2 minutes, depending on part size.

Is this a new feature request?
No.
@bubnikv
Copy link
Collaborator

bubnikv commented Mar 22, 2021 via email

@zakutin
Copy link
Author

I'm using SLA inherited settings, 0.01 mm slicing resolution and supports.

I recorded two videos for info:

Model files, STL and 3mf:
model.zip

@bubnikv
Copy link
Collaborator

@tamasmeszaros would you please look at it? It looks as if the "Rasterizing layers" step could not be canceled in PrusaSlicer 2.3.0.

@zakutin
Copy link
Author

zakutin commented Jun 2, 2021 •
edited

It looks like the issue still persists in Version 2.3.1+win64. It indeed happens on "rasterizing layers" step. Please see the videos below.
Big part:

big_part.mp4

Small parts:

small_parts.mp4

Models:
models.zip

@bubnikv
Copy link
Collaborator

bubnikv commented Jun 2, 2021 via email

@zakutin
Copy link
Author

zakutin commented Jun 2, 2021 •
edited

This is exactly the same issue number :) I just commented under the closed issue. Thanks, good to know this will be fixed in 2.4!

@bubnikv bubnikv mentioned this issue Aug 6, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bubnikv @rtyr @zakutin