hilbert surface gets printed again on top surface

[maruhe]

attached the models I created to test ArcOverhangs

may it's because the thickness of the overhang is quite low I reduced BottomLayers to 3 and after ArcOverhangs and hilbert surface the infill starts (even printing slow) but after the infill it starts again with hilbert surface printing super slow and this destried the prints (I think because the hot nozzle was nearby / touching the overhang-area for long time

I'm printing ABS and the ArcOverhangs work great! just the following layers need to get printed faster is there an option to limit the number of hilbert layers and the number of slow layers?

arc.zip

while testing I also saw some moves in the infill above the hilbert that have been ultra slow and creating little blobs on the outer surface I didn't found that part in the gcode but it felt like a G1 command without feedrate using an old slow feedrate

[billfj4045]

I too did notice the ultra-slow printing on the subsequent layers above the hilbert pattern. Do agree that the heat passed back to the print could be re-softening it... especially with my attempts in PLA. I know there's more slicer settings that need to be adjusted to make this optimal. I just got through my proof of concept the other day and still have a lot of exploring to do.

[nicolai-wachenschwan]

Yes, there are 2 parameters defined to this usecase. You need to adapt the parameters in the "parameter" section of the script according to your needs. Navigate to Special Cooling Settings. There you find specialCoolingZdist, which is the Z distance the special cooling settings are applied and therefore every solid infill within beeing convertet to hilbert. Default is 3mm, but you can lower it to exclude the top surfaces.

PrintSpeed: change "aboveArcsPerimeterPrintSpeed" and "aboveArcsInfillPrintSpeed" to modify the printing speeds according to your needs.

[maruhe]

specialCoolingZdist is a nice hint, before it looked like this in case I will fix something I_ll create a pull request :-)

i still get this ultra-slow line but din't found it yet but I found a missing linebreak also saw missing linebreaks in other files before:

[billfj4045]

I presume that these changes are in the .py script itself and not in Prusa Slicer (I don't know of them). That might be a step out of my league, but will make a copy of the original script and see what I can do to make those adjustments. Fingers crossed! UPDATE: Google is my friend! :-) Let's see if these changes work! ;-)