KISSlicer 1.5 release candidates 1 and 2

frozen.rabbit
Posts: 132
Joined: 17 Nov 2014, 09:20

Re: KISSlicer 1.5 release candidate 1

Post by frozen.rabbit »

Win64 version also does 0.0055 thing in layer thickness, extrusion width, and infill extrusion width.
calinb
Posts: 25
Joined: 21 Apr 2015, 13:05

Re: KISSlicer 1.5 release candidate 1

Post by calinb »

WooHoo!

I was just signing-on to the forum to try to find out why I'm not getting wipe gcode (I recall something was posted here in the forum) and found this thread. Thank you so much, Jonathan, for bringing Kisslicer development back to life!

Cal
Last edited by calinb on 19 Jun 2016, 15:39, edited 2 times in total.
KISSlicer user since 2012 (PRO since 2013)!
User avatar
pjr
Posts: 692
Joined: 05 May 2015, 10:27
Location: Kamnik, Slovenia

Re: KISSlicer 1.5 release candidate 1

Post by pjr »

frozen.rabbit wrote:Win64 version also does 0.0055 thing in layer thickness, extrusion width, and infill extrusion width.
Also in the Material/Main temperature field; I entered 195 and didn't notice that the temp was set to 1095!! I think it is also the same for first layer temp.

Peter
inventabuild
Posts: 271
Joined: 09 Nov 2014, 23:03

Re: KISSlicer 1.5 release candidate 1

Post by inventabuild »

What version of Windows are you guys running with the erroneous numbers appearing in the fields? I'm running KISSlicer Win64 on Windows 8 and I'm not seeing any erroneous numbers:
KISSlicer Win64 - Windows 8 - No Repeating Numbers On My Computer
KISSlicer Win64 - Windows 8 - No Repeating Numbers On My Computer
Windows 8 - No Repeating Numbers On My Computer.JPG (50.7 KiB) Viewed 3416 times
I was going to upgrade to Windows 10, but might hold off if that creates the issue.
calinb
Posts: 25
Joined: 21 Apr 2015, 13:05

Re: KISSlicer 1.5 release candidate 1

Post by calinb »

Okay...I'm still not getting a wipe with 1.5 rc1 Win64

The "Crown Path," below is actually the jump but there is no wipe. I have also seen Kisslicer code that incorrectly identifies a jump as a loop path. Note that I even set Min_Jump and Trigger to zero to destring on all travels.

G1 X58.42 Y37.36 E6.2102
G1 X58.51 Y37.62 E6.2115
G1 X58.52 Y37.76 E6.2121
;
; 'Destring/Wipe/Jump Path', 0.0 [feed mm/s], 70.0 [head mm/s]
; 'Destring Suck'
G1 E1.2121 F3000
;
; 'Crown Path', 0.2 [feed mm/s], 44.0 [head mm/s]
G1 X48.84 Y36.85 E1.2121 F15000
; 'Destring Prime'
G1 E6.2121 F3000
G1 X49.27 Y36.99 E6.2142 F2640.1
G1 X50.13 Y37.13 E6.2182
G1 X51.28 Y37.25 E6.2235
G1 X52.65 Y37.3 E6.2298
G1 X54.16 Y37.31 E6.2367

from _styles.ini:

quality_percentage=40
layer_thickness_mm=0.12
extrusion_width_mm=0.25
num_loops=3
skin_thickness_mm=0.76
infill_extrusion_width=0.25
infill_density_denominator=0
stacked_layers=2
use_destring=1
use_wipe=1
use_corners=1
loops_insideout=0
infill_st_oct_rnd=1
inset_surface_xy_mm=0
seam_jitter_degrees=0
seam_depth_scaler=0
seam_gap_scaler=0
seam_angle_degrees=360

from _materials.ini:

g_code_matl=3B204D617962652073657420736F6D65206D6174657269616C2D737065636966696320472D636F64653F
fan_Z_mm=0.2
fan_loops_percent=70
fan_inside_percent=70
fan_cool_percent=100
temperature_C=230
keep_warm_C=150
first_layer_C=230
bed_C=0
sec_per_C_per_C=0.00192
flow_min_mm3_per_s=0.1
flow_max_mm3_per_s=4
destring_suck=5
destring_prime=5
destring_min_mm=0
destring_trigger_mm=0
destring_speed_mm_per_s=50
destring_suck_speed_mm_per_s=50
Z_lift_mm=0
min_layer_time_s=5
wipe_mm=5
cost_per_cm3=1.15585
flowrate_tweak=1
fiber_dia_mm=2.83
color=185270272
KISSlicer user since 2012 (PRO since 2013)!
frozen.rabbit
Posts: 132
Joined: 17 Nov 2014, 09:20

Re: KISSlicer 1.5 release candidate 1

Post by frozen.rabbit »

WinXP 64 bit here
User avatar
lonesock
Posts: 258
Joined: 09 Nov 2014, 18:41
Contact:

Re: KISSlicer 1.5 release candidate 1

Post by lonesock »

OK, I finally fixed the random number issue. (If a value was outside the allowed range it was being forced to the limit. For example, if you wanted to write 0.4, but only got the "0." in place before the code checked the limits, it would say "0 is too small, set it to 0.005". I had code to not overwrite the value if it was currently the user's focus, BUT there is a quirk of FLTK that I didn't know...input number widgets like I am using actually have a hidden text widget inside them, and *that* actually had the focus, so my test was failing. I know, Too Much Information. [8^)

I also found a bug that would infrequently crash KISSlicer randomly, and fixed that.

Regarding the lack of wipe after a retract and the jump being misidentified: It's weird that there would be no wipe after a retract, I will look into that. The jump being misidentified is my fault. I specify the next path type before moving to the start, so the travel move itself is always (I think) grouped with the path, instead of being up where the destring event is. I should probably have the text there read something like "Begin Destring/Wipe/Lift(if enabled)". Thanks for letting me know about the wipe issue.

I will try to get a RC 2 out today. I have actually been busy adding in features for the *next* release while waiting on feedback for this one, so I had to kill the bugs in 2 different branches, so sorry for the delay.

Thanks for your patience and help, everybody! RC 2 coming up!

Jonathan
User avatar
lonesock
Posts: 258
Joined: 09 Nov 2014, 18:41
Contact:

Re: KISSlicer 1.5 release candidate 1

Post by lonesock »

OK, I just posted version 1.5 Release Candidate 2. (Windows and Linux already, Mac hopefully by tomorrow.)

Changes:
  • Fixed a few controls where the text could not be translated
  • Fixed a bug where a control would be clamped to a limit while the user was editing the value
  • Fixed an infrequent crash (happened most frequently after reloading a model, deleting a model, or trying to open a new model)
Hopefully there are no more show-stopper bugs, then I can release 1.5 and start posting updates for the new features going into the 2.0 version.

Thanks, everyone!
Jonathan
User avatar
lonesock
Posts: 258
Joined: 09 Nov 2014, 18:41
Contact:

Re: KISSlicer 1.5 release candidates 1 and 2

Post by lonesock »

The Mac build should be up there now as well!

thanks,
Jonathan
calinb
Posts: 25
Joined: 21 Apr 2015, 13:05

Re: KISSlicer 1.5 release candidate 1

Post by calinb »

lonesock wrote: Regarding the lack of wipe after a retract and the jump being misidentified: It's weird that there would be no wipe after a retract, I will look into that. The jump being misidentified is my fault. I specify the next path type before moving to the start, so the travel move itself is always (I think) grouped with the path, instead of being up where the destring event is. I should probably have the text there read something like "Begin Destring/Wipe/Lift(if enabled)". Thanks for letting me know about the wipe issue.

I will try to get a RC 2 out today. I have actually been busy adding in features for the *next* release while waiting on feedback for this one, so I had to kill the bugs in 2 different branches, so sorry for the delay.

Thanks for your patience and help, everybody! RC 2 coming up!

Jonathan
No problem Jonathan! I'm just so pleased that you have time to work on Kisslicer again. I'll look for RC2 and check it out ASAP. I tried some other settings that should result in a wipe, but haven't seen it happen and thought I'd ask you and the others here about it before I randomly try many combinations of settings that might identify a bug.

I do see a wipe in Slic3r gcode. However, Slic3r does not provide as much destring control as Kisslicer. I can see the wipe when printing with the Slic3r code too.
KISSlicer user since 2012 (PRO since 2013)!
Post Reply