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

Modifier (cylinder) sparse infill speed setting not working. #3849

Closed
SchoGiGIT opened this issue May 16, 2023 · 5 comments
Closed

Modifier (cylinder) sparse infill speed setting not working. #3849

SchoGiGIT opened this issue May 16, 2023 · 5 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@SchoGiGIT
Copy link

What happened?

Created modifier part overlapping with my part. (cyclinder in center of part, look at slower speeds)
Added multiple speed modiferes to this part.
All modifiers seem to work except sparse infill speed (see both standard 180mm/s) even though it is set at 80mm/s

image

image

Project file & How to reproduce

Squad_dome7_cylinder.zip

Version

2.5.59

Operating system

Windows 10

Printer model

Ratrig vCore3-500

@ft276
Copy link

ft276 commented Jan 1, 2024

I am still having this issue unfortunately.

I have a workaround.
If you change the sparse infill line thickness in the modifier, as well as the speed, this corrects the issue.
The thickness can be changed from e.g. 0.5 to 0.51 and it will produce the correct speed. You cannot keep the thickness exactly the same as the default with just the 'modifier' tag on however.

@supermerill supermerill added the bug Something isn't working as intended label Jan 16, 2024
@supermerill
Copy link
Owner

Thanks for the heads-up.

It's kinda an undocumented feature.
The most likely root cause is:
. fill regions are merged to prevent artificial frontier between them, unless a useful setting is changed.
. infill_speed isn't listed as useful setting for creating infill
these speed are available for modifiers to be used with layer range modifier only.
I will make infill_speed/solid_speed/top_speed as settings that will split fill areas, i guess it's the most sane way to do it.

One day, I won't need to split fill & perimeter anymore for speed to be changed... not a easy task though.

@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 Jan 16, 2024
@ft276
Copy link

ft276 commented Jan 16, 2024

Thank you. It's a shame about having to create perimeters between regions like this as it is likely to compromise strength but sounds like not an easy fix. But, this change will stop me from having to set infill speed slow for the entire model, to allow it to be slow for the overhangs.
Much appreciated.
What would be really good is to have the option of more than one height modifier, as given the perimeter limitations I find myself having to use large box modifiers that cover entire layers in order to change speed settings for a section, and that would be much easier with extra height modifiers.
Perhaps I'll make a feature request for that.

Anyway, much appreciated.

@neophyl
Copy link

neophyl commented Jan 16, 2024

You can add multiple height range modifiers already. Admittedly it is not intuitive though. Once you have added an initial height range modifier you can then click on the + button next to it to add others.
image

@supermerill
Copy link
Owner

You have to be on the "Layers" label in the right panel, no the individual one.

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Feb 11, 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 fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

4 participants