KISSlicer 1.5 Beta 2 - in development

[626Pilot]

I found a couple bugs in the Linux 64 build of 1.5 beta 2.16.

First, if you select an object to work with it, and then go to edit something in a number field down below, and you highlight the number and hit Delete, it will delete the object instead! I think it should pass the delete event to the text field instead of the object.

Second, I had some settings like this:
Layer height 0.2
First layer ("bed roughness") 0.3
Fan Z 0.5

Fan turned on for the first layer, which is super bad because it will encourage nasty warping and over-shrinkage on the bottom infill. 0.3 < 0.5, so there is some extra Z coming in there somewhere, maybe from however much it thinks it has to lift for the first layer. I didn't expect it to turn on until it passed the Fan Z elevation.

[lonesock]

OK, I get the first one, and it's on the list.

However, with the second one, if someone wants the fan on below the height where the model starts, then they would have to enter a negative number for the fan's Z threshold, which doesn't seem very intuitive to me. I would prefer to just make it clearer that it is Z height above the bed, not in model-space. Hopefully that would be sufficient?

thanks,
Jonathan

[Isaac_alaska]

very very nice, i really like the vertical stacking option, wont' get used very often but when it does it's a great time-saver!

has there been any more work on vertical separation between part and support?
the current option works okay with layers .15 or thicker, by setting the vertical separation to .14, but with .1mm layers the part and support are still pretty stuck together with .09 separation

is there a way to completely remove an arbitrary layer of support? if so it wouldn't be hard to find the top layer of support and then just tell it to not print that layer, which would work very well for what i'm doing

[626Pilot]

However, with the second one, if someone wants the fan on below the height where the model starts, then they would have to enter a negative number for the fan's Z threshold, which doesn't seem very intuitive to me. I would prefer to just make it clearer that it is Z height above the bed, not in model-space. Hopefully that would be sufficient?

I'm confused. I'm not using a raft, layer 0 just goes straight to the glass. If I say to turn on the fan at 0.5, and the first layer is 0.3 tall, it should not turn on until after the first layer. Or am I missing something?

[lonesock]

@626pilot: The bed roughness value is added to the first layer thickness (since a perfectly flat bed of 0 roughness would not have a 0 mm thick first layer), so in your case the extruder will be right at 0.5 mm for the first layer.

@Isaac_alaska: I will look into that right now.

thanks,
Jonathan

[inventabuild]

Lonesock, what kind of mathematical shape do you try to create w/ the extrusion? I'm wondering how the footprint of the layer changes as the height increases.

[lonesock]

I have a new build up (for Windows, more on the way) in Dropbox: Version 1.5 beta 2.20.

Changes from 2.16:

• Arbitrary Z-gap is now allowed
• Fixed a bug where the wipe and destring following support interface paths where at the wrong height when Z-Gap was used.
• G-code summary at the end now includes per-extruder filament length (and volume) used.
• Optimized object slicing with many small sub-meshes.
• You can now add up to 5 layers of support interface on top of the raft.
• Pressing delete anywhere in the model tab no longer deletes the model.
• Fixed a bug where the animation slider would reset itself every second.
• Fixed bug when Slice-and-Save is checked and we cancel the file selection.
• Every-N-Layers now doesn't drag-value-change.
• Added a squiggle-base to the prime pillar to help it adhere to the bed / raft.

thanks,
Jonathan

[mhackney]

Now Mac 1.5 beta 2.20 too! Cool, thanks.

[626Pilot]

Really glad about the support matrix under prime pillars. Those are so fragile sometimes.

I read earlier that "Rim Speed (Deltas)" isn't implemented yet. When it is implemented, what will it do? I looked up the definition of "rim speed" but it doesn't clarify much.

Do you have the forward/inverse kinematics stuff set up to do features like max carriage velocity and min carriage height? If you want to protect a Delta printer, those would be a good place to start.

[mhackney]

Jonathan, I've run 2.20 on both Mac and Windows 7 64-bit and replaced and printed all of my reel parts. I didn't find any regressions and the parts printed perfectly.