The wipe checkbox is gone on the style tab.
I assume it's now disabled by setting it to zero mm at the mat tab.
I still have problems to understand the Min Jump and Trigger settings:
As almost everybody uses 5D:
The min jump is a threshold to destring: so with more than 2mm travel you get a destring when a travel is >2mm
The trigger pop up tells me that a min travel treshold of for example 4mm is resulting in destring and wipe when a travel is > 4mm.
So when both set to 2mm you get a wipe and destring?
What happens if the min jump is 4 mm and the trigger is 4mm.
And vice versa?
KISSlicer 1.6 Release is here! (UPDATED 2017-09-08)
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta Bug Reports
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta Bug Reports
No bug, compliments 
Earlier the printpath was not very consistent. When printing an Architectural model with a lot of columns the print path was erratic.
With the new seam function (fill) the path is logical for thos small islands.

Earlier the printpath was not very consistent. When printing an Architectural model with a lot of columns the print path was erratic.
With the new seam function (fill) the path is logical for thos small islands.
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta Bug Reports
Regarding the new "Join Loop" box I don't understand the remark that
As with zero, the paths (the middle of the extrusion) are just kissing each other. But with for example 0.4mm pathwidth, than it's resulting in a double amount filament at that overlap. That can't be good I think. The advance feature is only compensating for the delay of response of the extruder regarding the (de)acceleration of the XY movement. That has nothing to do with that seam (overlap) IMO.
Also: are the values of the seam settings in mm or percentage. It seems in mm. The % would be preferable when changing the extrusion width.
(when some dark side feature tweaked).the gap optimal has to be zero
As with zero, the paths (the middle of the extrusion) are just kissing each other. But with for example 0.4mm pathwidth, than it's resulting in a double amount filament at that overlap. That can't be good I think. The advance feature is only compensating for the delay of response of the extruder regarding the (de)acceleration of the XY movement. That has nothing to do with that seam (overlap) IMO.
Also: are the values of the seam settings in mm or percentage. It seems in mm. The % would be preferable when changing the extrusion width.
funBart wrote:I checked the new seam future: Join-Loop. It seems to me a very good idea to have a non hard stop at the seam, but in stead let the path of the loop fluently connect to the perimeter.
No Join Loop: Seam: a part of the outer loop path is combined with the perimeter path
Full: the complete outer loop path is combined with the perimeter path.
I have to check still how it works in real life. That's hard as the effect is also depending to the new "advance" Preload function I don't understand yet..... Where to begin?
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta 1.1 is here!
Question about the support structure: Earlier we had a flow tweak for the interface support. Now it's replaced with the "width" function? So when wanting meager support interface with a 0.4mm nozzle, one can set it to 0.3 or 0.2mm?
Also: is the main support structure based on the extrusion width on the style tab? Or the infill extrusion?
As I think to have seen now, there are a lot of settings that are based on exact values, as the stepover function, the seam settings and support interface.
When changing the nozzle size and within limits the path width one has to change all those unrelated (excact) settings as well.
IMO a setting based on a percentage of path width would be easier for a lot of users.
Also: most users set the path width as the nozzle size. It's changed when there are troubles with thin walls, but otherwise not.
Maybe it would be easier only to have a setting for Nozzle size on the Printer tab, and with expert settings an option to change that nozzle size path for loops and infill. So all on the printer tab.
As a nozzle belongs to a printer most of the time.
All the belonging settings to that nozzle size (or width changed to another pathwidth) are likely best getting that width and apply a percentage. Than you don't have to check all the settings when changing path width or nozzle size.
As the overstep function: now you have to change it when changing to 0.6mm path width from 0.2 to 0.3mm overlap. When able to set it to 50% you haven't have to change the value.
As said earlier: it would be nice if the new overstep function has some clever influence with the support structure.
For example: it would be easy to calculate the min angle to generate support based on the min layer height generated and the min stepover value.
Also: is the main support structure based on the extrusion width on the style tab? Or the infill extrusion?
As I think to have seen now, there are a lot of settings that are based on exact values, as the stepover function, the seam settings and support interface.
When changing the nozzle size and within limits the path width one has to change all those unrelated (excact) settings as well.
IMO a setting based on a percentage of path width would be easier for a lot of users.
Also: most users set the path width as the nozzle size. It's changed when there are troubles with thin walls, but otherwise not.
Maybe it would be easier only to have a setting for Nozzle size on the Printer tab, and with expert settings an option to change that nozzle size path for loops and infill. So all on the printer tab.
As a nozzle belongs to a printer most of the time.
All the belonging settings to that nozzle size (or width changed to another pathwidth) are likely best getting that width and apply a percentage. Than you don't have to check all the settings when changing path width or nozzle size.
As the overstep function: now you have to change it when changing to 0.6mm path width from 0.2 to 0.3mm overlap. When able to set it to 50% you haven't have to change the value.
As said earlier: it would be nice if the new overstep function has some clever influence with the support structure.
For example: it would be easy to calculate the min angle to generate support based on the min layer height generated and the min stepover value.
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
- lonesock
- Posts: 258
- Joined: 09 Nov 2014, 18:41
- Contact:
Re: KISSlicer 1.6 Beta 1.1 is here!
@funBart: I fully agree, many of these would be more useful relative to the extrusion width. I might even be able to *remove* a setting or two! I definitely plan to do this for the upcoming 2.0 release, but I didn't want to break a bunch of existing functionality. Possibly a intermediate workaround would be a checkbox to select if a set of parameters (grouped in a box) were relative to the extrusion width...it's just yet another setting. [8^/
I'm trying to see if there is a good enough solution that I can implement quickly and robustly. If not, it may have to wait for the 2.0 track.
thanks,
Jonathan
I'm trying to see if there is a good enough solution that I can implement quickly and robustly. If not, it may have to wait for the 2.0 track.
thanks,
Jonathan
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta 1.1 is here!
Sure, sure, that good old future feature releasewait for the 2.0 track.

Can I assume that my infamous "Y is the new Z" function will be in that release as well?
https://www.craftbot.nl/2015/07/08/y-is ... direction/
That's a way to complex sequence to be able to print slow slopes smoothly by slicing in Y direction in stead of Z.
Although that function is way more complex when there are different levels of slow slopes.... But than again: you are the first implementing the automatic variable layer height. It's peanuts for you!
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
-
- Posts: 66
- Joined: 07 Nov 2014, 15:23
Re: KISSlicer 1.6 Beta 1.1 is here!
If by "path width" you mean "extrusion width", I disagree. With a nozzle diameter of 0.35, I use extrusion widths between 0.3 and 0.55 depending on layer height, material, resolution requirements, speed requirements, infill vs. loops, etc. I don't want this setting to be hidden somewhere in the printer tab. Sure, which values are reasonable for the extrusion width setting depends on the printer hardware, but this is true for so many other settings as well.funBart wrote: Also: most users set the path width as the nozzle size. It's changed when there are troubles with thin walls, but otherwise not.
Maybe it would be easier only to have a setting for Nozzle size on the Printer tab, and with expert settings an option to change that nozzle size path for loops and infill. So all on the printer tab.
As a nozzle belongs to a printer most of the time.
- funBart
- Posts: 49
- Joined: 07 Nov 2014, 11:40
- Location: Rotterdam, the Netherlands
- Contact:
Re: KISSlicer 1.6 Beta 1.1 is here!
Than you are stupidIf by "path width" you mean "extrusion width", I disagree.

I don't care, as I have 6 slicers tuned to print great with my CraftBots. But 95% of the people -mentally disturbed enough to use a slicer not belonging to their printer- is setting the pathwidth / extrusion width / width poop to their nozzle size.
Only 'know it alls' want to set a different value. Mostly to force thin walls to be seen and sliced ok. But that's only needed with other slicers, as KS is slicing the thin walls ok even when they are smaller than the Extrusion Width, known as Path Poop . Yeah for crowning! And Pooping!
So, why would one set the pathwidth different than the nozzle size with KS? As that value is the most optimal regarding the flow, spit out, poop of a nozzle.
I only use extreme pathwidths, as 2,5mm with a 1mm nozzle when printing Vase mode. But Kisslicer isn't able to print real vase mode.... (spiraling single perimeter). Shame on you KISSlicer! Shame!
That nozzle value belongs to the printer and hasn't to be seen ever again. As changing the path width +/- 33% of the nozzle size isn't needed with KS. But with other slicers it is.
Bart ter Haar
CraftBot PLUS support: https://www.CraftBot.nl
CraftBot PLUS support: https://www.CraftBot.nl
-
- Posts: 16
- Joined: 18 Sep 2015, 15:32
- Contact:
Re: KS slows down on short paths
Peter,pjr wrote: My suggestions:
Printer/Extruder Hardware - set the DrvLen for each extruder. This is the distance between filament drive pulley and nozzle orifice, so even for direct drive systems, there will be at least 60mm.
Material - set the PreloadVE; depending on drive type, the destring may be a little low.
Wizards/Tuning Wizard - When Jonathan has fixed the fault, try printing the test cube with the Preload wizard.
Peter
thanks for the suggestions.
But I don't think it will solve my problem where the blob appeared because it's only due to KS slowing down drastically on the orange paths (on my picture).
Why does KS slows down drastically on these paths ? Shouldn't the perimeter (and loops) speed be always constant ?
Anyway I will follow your suggestions and will try again.
Cheers.
- EddyMI3D
- Posts: 81
- Joined: 03 Oct 2015, 17:12
Re: KISSlicer 1.6 Beta 1.1 is here!
Hi there!
So many new things
But where can I set the parameters for bridging?
It seems to be very slow here I would like to tune it up a bit.
Thanks for help,
Eddy
So many new things

But where can I set the parameters for bridging?
It seems to be very slow here I would like to tune it up a bit.
Thanks for help,
Eddy