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

Incorrect support speed , seems to stuck at some low speed. #439

Closed
kursatu opened this issue Sep 1, 2020 · 9 comments
Closed

Incorrect support speed , seems to stuck at some low speed. #439

kursatu opened this issue Sep 1, 2020 · 9 comments
Labels
bug Something isn't working as intended

Comments

@kursatu
Copy link

kursatu commented Sep 1, 2020

Version

Version of SupserSlicer used goes here
I've built with the latest commit on 8/27/2020
Use About->About SuperSlicer for release versions
2.2.53
For -dev versions, use git describe --tag or get the hash value for the version you downloaded or git rev-parse HEAD

Operating system type + version

What OS are you using, and state any version #s
Windows 10
In case of 3D rendering issues, please attach the content of menu Help -> System Info dialog

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

Custom CoreXY printer, Vking derivative
Marlin bugfix2, latest commit,
What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s

Behavior

  • Describe the problem
    Slice the object in the attached 3mf file.
    Observe that the support speed it something completely different than anything in the settings.
    I couldn't find where this speed comes from. It looks like a defect.

  • Steps needed to reproduce the problem

    • If this is a command-line slicing issue, include the options used
  • Expected Results

  • Actual Results

    • Screenshots from SuperSlicer preview are preferred

Is this a new feature request?

Project File (.3MF) where problem occurs

Upload a SuperSlicer Project File (.3MF) (Plater -> Export plate as 3MF for Slic3r PE 1.41.2 and older, File -> Save / Save Project for SuperSlicer, Slic3r PE 1.42.0-alpha and newer)
Defect6
Defect6_1
Defect6.zip

@neophyl
Copy link

neophyl commented Sep 1, 2020

Your speeds are being limited by the cooling over ride under filament settings. If you reduce your layer time goal or the Max speed reduction it increases the support speed.

Although I do think there is still a bug around that anyway, as I increased the min print speed to 50mm/s and the support was still printed at 20mm/s. It took either reducing the layer time goal to be ridiculously short or changing the max speed reduction % to get it faster. It should only go as low as the min print speed but that didnt seem to work for the support when set to 50mm/s.

@kursatu
Copy link
Author

kursatu commented Sep 1, 2020

It seems like there is another related defect. If I switch supports (both interface and itself) to another extruder
it does not slowdown for cooling.
I usually print with just the support interface using extruder 4 but not both the support and interface.
For the original defect, the support is printed using the same tool as the model itself, so it should
not slowdown to the cooling override speed.
The rest of the layer does not do that.
This is a high impact defect. It makes the supports unusable.
Defect6_3
Defect6_4
Defect6_5

@supermerill
Copy link
Owner

Found the issue, it's because the support are on their own layer, and the algorithm consider that layer as a layer of the object, hence reducing the speed...

have to find a way to merge these support layer with the object's ones.

@supermerill supermerill added bug Something isn't working as intended and removed problem labels Sep 2, 2020
@kursatu
Copy link
Author

kursatu commented Sep 2, 2020

Thanks for looking into this. I am guessing it is not always fun to
fix such defects, may be a regression.
I've tried to check if this happens with Prusa slicer but it did not even open the .3mf file.
I am guessing they can't be used between Prusa Slicer and SuperSicer.

@neophyl
Copy link

neophyl commented Sep 2, 2020

Did you get a serialise error ? When trying to open in Prusa Slicer

@supermerill
Copy link
Owner

I corrected some errors that can happen when loading config with unknown keys, but i can't do anything to put these corrections into prusaslicer.
Maybe i'll do an "export to prusaslicer" a day I'm bored.

@supermerill
Copy link
Owner

the support-layer time will be added to the object-layer (if unsynch) in the 2.3.55 release.

@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 Nov 4, 2020
supermerill added a commit that referenced this issue Nov 4, 2020
and don't slowdown support layers if unsynchronized
and add half of time diff with previous layer to prevent spikes
@kursatu
Copy link
Author

kursatu commented Nov 6, 2020

I've got the latest code which includes the commit above, 2adea5b
The slowdown is still there. Is it supposed to be fixed by that commit?
Defect439_1

@supermerill supermerill removed the fixed for the next version That means that you should be able to test it in the latest nightly build label Nov 6, 2020
@kursatu
Copy link
Author

kursatu commented Nov 15, 2020

Seems to be fixed with the latest sources on GItHub.

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
Projects
None yet
Development

No branches or pull requests

3 participants