Hey, answering is easy: 42 [8^)
Wishlist: I love that thread...I just read, not post. I would like to propose the following: as soon as the release is out, I would like to lock that thread, and open a new one with the features that are not in the release. Also, there are a few features that are already on my list (multi-material objects, comb-like thing, brim, etc.), so no point voting for them. [8^)
Regarding the destring & wipe stuff, this is a bit complex, as we all know by now. [8^) KISSlicer separates the path generation, path combining, and the path exporting. The path generation is the core slicing activity, but it does not actually make wipe paths or destring G-code...all it does is place a Wipe / Destring marker where it thinks it's needed.
So, during slicing, KISSlicer examines the end of path A and the beginning of path B. If the travel path from Aend to Bbegin crosses over a perimeter Request_Event = true. Then, if the distance of that jump is < "Min Jump" then Request_Event = false. Then, if that same travel length is >= "Trigger", then Request_Event is set to true again. After this logic is done, if Request_Event is true then KISSlicer adds in a Wipe/Destring marker.
Now, when combining all paths (from multiple objects, or multiple copies of the same path) KISSlcier looks for those Wipe/Destring markers. When it finds one, if will perform a wipe or destring depending on the style settings (there is now one checkbox to enable wipe and another to enable destring so Wipe can be combined with firmware that supports auto destring with M101/3 cues), and the material settings will determine the wipe length. The actual wipe paths are generated at this point.
Finally, on exporting the G-code, actual extruder commands are inserted, including any destring retracts or primes requested. The Wipe paths are then just motion without extrusion. After a wipe path (or destring event, if wipe = 0 or disabled) the Z-lift happens. When we get to the start of the next path, the reverse Z-lift will happen if needed, and the destring prime will happen if a retract just happened.
Not sure if that helps or hinders.
Loops and Solid overlap is a setting since it's solid on solid...so doing too much or too little has consequences. For the sparse Infill overlap I just always set it to 100% since there is space in the sparse infill for any extra material to go, and we need a decent bond.
The extruder min and max flow rates have the last word. You can set the min to 0 if there is no actual limit with your extruder. Some firmware has an absolute minimum speed they can allow, often a starting minimum velocity value set as a function of the machine acceleration. Any speed lower than this will either get set to min, or 0, either of which is bad since the head speed / flow rate ratio is violated. But, if you do have a minimum value or maximum value, KISSlicer assumes you really mean it...the extruder will not do what is asked of it if you go above or below those limits. The min layer time is secondary. I suppose I could switch into some kind of "roam around in free space" mode, but that is not implemented.
thanks,
Jonathan