kisslicertalk.com

plexus wrote:Just tried 1.6 beta 1.1 on mac. It wont open. the application has the "NO" symbol through it (see screenshot)

Humm. abuharsky does have it running on a MAC. I wonder if it's O/S specific?

Peter

The Mac build was 64-bit only, compiled on a borrowed machine, so I think the latest Mac release? I can do a hybrid 32-/64-bit release on my super old machine this weekend.

Jonathan

I'm using Windows64 and when I calculate a PreloadVE it's noted as 0.0 in the g-code

Pic 1 Shows calculated PreloadVE entered into the Material tab: Here's some lines of g-code output where preload value is noted 0.0. All preload values are noted as 0.0 in the g-code.

G1 E30.3373 F1500
; head speed 15.000000, filament speed 0.449012, preload 0.000000
G1 X123.512 Y188.244 E30.35515 F900

inventabuild wrote:I'm using Windows64 and when I calculate a PreloadVE it's noted as 0.0 in the g-code

G1 E30.3373 F1500
; head speed 15.000000, filament speed 0.449012, preload 0.000000
G1 X123.512 Y188.244 E30.35515 F900

Yeah, there are some GCodes where preload will be calculated as zero, but most should have a value.

Can you please post a screenshot of your Printer/Extruder Hardware tab.

That preload value looks very high to me; I am currently running at about 0.2 for PLA at 205 degrees.

Thanks

Peter

Hi Peter, it looks like you are clearing up a lot of things.

First of all here is a snippet of my Printer/Extruder Hardware tab that was used to create that g-code. Now I see that the DrvLen s/be 750 mm (my bowden tube length) instead of 0 as shown in the pic I was not aware of this setting since I thought the data I entered into the VE Calculator w/ be populated wherever necessary in the software when I clicked to store the VE value. Secondly, the term Drive Length is a little confusing. Intuitively I thought it s/ be the length of the bowden tube (not sure what is s/b for direct drive); however hovering over the Length To Extrude field in the VE Calculator it almost looks like the Drive Length is the Length To Extrude based on the popup note:

inventabuild wrote:Hi Peter, it looks like you are clearing up a lot of things.

First of all here is a snippet of my Printer/Extruder Hardware tab that was used to create that g-code. Now I see that the DrvLen s/be 750 mm (my bowden tube length) instead of 0 as shown in the pic I was not aware of this setting since I thought the data I entered into the VE Calculator w/ be populated wherever necessary in the software when I clicked to store the VE value.

Secondly, the term Drive Length is a little confusing. Intuitively I thought it s/ be the length of the bowden tube (not sure what is s/b for direct drive); however hovering over the Length To Extrude field in the VE Calculator it almost looks like the Drive Length is the Length To Extrude based on the popup note

The drive length in the extruder hardware is the distance from the filament drive pulley to the top of the nozzle orifice.

The Length to Extrude in the calculator is the length of material to extrude to generate a steady flow at the nozzle so that the ooze can be determined.

Peter

KISSlicer isn't getting typical overhangs yet .

I mean overhangs that are 'dripping" Or Ice Pillars. Or Stalactites
Like these:
It's resulting in insufficient support structure:
Reducing the oversample resolution didn't help.

The test stl is here. https://www.thingiverse.com/thing:635497/#files

When slicing with the "perimeter after inner loops" unchecked, (and Join-Loop set to Seam / Full) it's path is as expected: inside out:
-infill
-loops
-perimeter.

When checked it's path is:
-outmost loop
-perimeter'
-other loops
-infill

EDIT: after some brain banging that makes sense maybe? Or not? As a traditional sequence as:
-perimeter
-outmost loop
-other loops
-Infill
Can't be combined with the new seam feature. Maybe only when setting it "off".

Starting with the perimeter is challenging regarding the needed (angle for) support, but OTOH is starting with the perimeter always resulting in more accurate measurements of the print.


BTW: the checkbox is after "num loops" One should expect it before or after the text "perimeter after inner loops"

@ funbart
Already spotted

When slicing with the "perimeter after inner loops" unchecked, (and Join-Loop set to Seam / Full) it's path is as expected: inside out:
-infill
-loops
-perimeter.

IF the "perimeter after inner loops" unchecked, the path expected will be :
-perimeter
-loops (from outside to inside)
-infill

IF the "perimeter after inner loops" checked, but, the path expected is :
-loops (from inside to outside)
-perimeter
-infill

(don't know where to post it)

In Support Tab, we have a "1st Width" setting, but KS make only one interface layer affected by the previous settings :Angle, Width (of which layer?) and stride

Perhaps I don't find how to...

...it could be interesting to have the first layer of Support (considering Ext Map)...or something with a "1st width" with a percent setting of layer to reach the main extrusion (Like "Limit Increase /layer " setting in Printer/Speed Tab)
=> Have a brim option for Support (considering Ext Map) !!!! with same settings for parts

This kind of parameter will be against (to be translate from french...hem...good luck ) "un potentiel éffondrement du support pour des formes de pièce éloignées de la partie principale de la pièce"
(but very useful, I promise)

By the way : great feature!!