-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Detailed models - Searching support spots takes forever, even when supports are disabled. #10940
Comments
Hello, @viesturz , Thank you for report. We can confirm. We will try to fix in some next release. SPE-1811 Have a nice day |
This issue should be fixed and fix will be part of the next release. |
I can verify that this bug is still present in version 2.7.0. Support generation will process even if no supports are requested and they are very slow on detailed models. |
Still not fixed. I created a 200mm cube with 25% gyroid infill and 0.08 mm layers. The slicing too a few seconds but searching for supports takes minutes even though supports are disabled. It seems to be single threaded so consider multithreading it. |
Sorry to add, it looks like Prusaslicer could be running out of memory at this stage. It’s using 10GB whilst calculating overhang perimeters. |
This is not completed. Prusa Slicer 2.7.1 hangs on "Searching Support Spots" if you turn on fuzzy skin at all. My slicing takes an hour now to complete in most cases. If I turn off fuzzy skin, it's quick, like seconds. This is all with Supports turned off, so why is it searching for support spots at all? |
Hello, @Gryfang , Could you share the project file (3MF), where the problem occure, please? Thank you |
Support searching still happens when supports are off, even with "Alert when supports needed" off. @Gryfang: @DanielDC88: Here are the 2 projects I tested this on: |
Sure. Here's a model that I just waited with supports off and support on
build plate only for way over twice the amount of time. I tested fuzzy skin
off, and supports generated almost instantly. With fuzzy skin on, the fuzzy
skin generated quickly, but the supports took way longer than expected.
I was using .05 / .05 on the fuzzy skin settings.
…On Fri, Jan 12, 2024 at 6:06 PM Alice Jacka ***@***.***> wrote:
Support searching still happens when supports are off, even with "Alert
when supports needed" off.
@Gryfang <https://github.com/Gryfang>:
I can't reproduce the hanging problem, and fuzzy skin adds a little time
to perimiter generation but doesn't seem to affect the support generation
stage. I have a pretty beefy computer though, what are you using?
@DanielDC88 <https://github.com/DanielDC88>:
Mine stays at a prety consistent 1GB RAM usage throughout, is that system
usage, or just Prusa Slicer?
Could you share your project file and a screenshot of task manager
Processes page showing the problem?
Here are the 2 projects I tested this on:
Projects.zip
<https://github.com/prusa3d/PrusaSlicer/files/13925742/Projects.zip>
—
Reply to this email directly, view it on GitHub
<#10940 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFAB6A5D76J3EXZ7I45MQK3YOHT2XAVCNFSM6AAAAAAZ3TIJSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI2TCMRWG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This was also using organic supports. But like I said, it almost appeared
to be frozen longer than it should have. I opened up task manager, and it
was using one core. I use a laptop, but it's no slouch. 8c 16th Ryzen 9
5900HX, 32GB RAM, RTX 3070 GPU. Don't know if you are using the GPU for
anything, but even the onboard GPU isn't horrible.
…On Sat, Jan 13, 2024 at 7:34 PM Greg Morse ***@***.***> wrote:
Sure. Here's a model that I just waited with supports off and support on
build plate only for way over twice the amount of time. I tested fuzzy skin
off, and supports generated almost instantly. With fuzzy skin on, the fuzzy
skin generated quickly, but the supports took way longer than expected.
I was using .05 / .05 on the fuzzy skin settings.
On Fri, Jan 12, 2024 at 6:06 PM Alice Jacka ***@***.***>
wrote:
> Support searching still happens when supports are off, even with "Alert
> when supports needed" off.
>
> @Gryfang <https://github.com/Gryfang>:
> I can't reproduce the hanging problem, and fuzzy skin adds a little time
> to perimiter generation but doesn't seem to affect the support generation
> stage. I have a pretty beefy computer though, what are you using?
>
> @DanielDC88 <https://github.com/DanielDC88>:
> Mine stays at a prety consistent 1GB RAM usage throughout, is that system
> usage, or just Prusa Slicer?
> Could you share your project file and a screenshot of task manager
> Processes page showing the problem?
>
> Here are the 2 projects I tested this on:
> Projects.zip
> <https://github.com/prusa3d/PrusaSlicer/files/13925742/Projects.zip>
>
> —
> Reply to this email directly, view it on GitHub
> <#10940 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BFAB6A5D76J3EXZ7I45MQK3YOHT2XAVCNFSM6AAAAAAZ3TIJSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGI2TCMRWG4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
@non-bin Here is the file I used and a video of the slicing process You will see the memory increase from the 1GB you mentioned from the 4m 9s mark onwards. |
Description of the bug
Searching support spots step is very slow on detailed models and seems to be run even when supports are not requested.
Project file & How to reproduce
Open this marlin: https://www.printables.com/model/5480-marlin-multi-material/files
Slice
Checklist of files included above
Version of PrusaSlicer
2.6.0
Operating system
win 11
Printer model
voron 2.4
The text was updated successfully, but these errors were encountered: