KISSlicer 1.5 Beta 2 - in development

[texsc98]

Looks awesome Jonathan! I haven't fully tested by actually running a print yet... But I did slice a part and check out the build cost components.

I have the following observations that all seem to be great:

• Printer/Hardware tab updating "$/hr" updates the build cost.
• Matl tab updating "Warm time" and "$ / cm^3" updates the build cost. "Warm time" also updates print duration.
• Printer/Speed tab updating the fields below updates the build cost and duration
  • X,Y Travel Speed
    Rim Speed (Deltas)
    Z-Speed
    1st Layer Max Speed
    Limit Increase / Layer
    XY Accel [mm/s^2]

And the following that don't behave as I would expect (although I may have the wrong expectations?):

• Style tab "Precision (vs. Speed)" slider doesn't affect build duration or cost.
• Printer/Speed tab none of the the 'Fast' & 'Precise' settings affect build duration or cost

Also have a question... What's the difference between "Rim Speed (Deltas)", and the "X,Y Travel Speed"?

[lonesock]

Thanks, everybody.

The build-time & cost updates seem to be working for me (when changing the speeds and/or the slider) on the Windows builds, was the problem on the Mac build?

Ah, Rim Speed's major difference is that it is not yet implemented! Sorry, that control was supposed to be hidden until the supporting code was in place!

Jonathan

[texsc98]

Thanks, everybody.

The build-time & cost updates seem to be working for me (when changing the speeds and/or the slider) on the Windows builds, was the problem on the Mac build?

Ah, Rim Speed's major difference is that it is not yet implemented! Sorry, that control was supposed to be hidden until the supporting code was in place!

Jonathan

Sorry meant to put that in there, it's the win64 build. Here's a quick video I did showing what/how I tested: https://www.youtube.com/watch?v=-X6ySeouZek

[lonesock]

Calculating the build info can take quite a while for large prints (my favorite slicing test case is the entire mendel packed set STL), so what I tried to do is flag when a setting changes, then 1 second later recalculate the build info. That way, a bunch of changes can all roll into one update, instead of delaying to calculate each individual update.

So for the slider, once you release it, the data should update about 1 second later. Also when the slider is all the way to one side or the other, one of the sets of speed settings will not be used (since the slider interpolates between the 'Precise' settings and the 'Fast' settings), so leaving the slider at 50% might be a better test to check timing updates.

However, all that being said, I think the real culprit is the 1st Layer Max Speed is set to 20 ( which is slower than all your speed settings), and the Limit Increase per Layer setting is 0, meaning your speed limit never increases! So I think basically all paths are stuck at 20 [mm/s]. If you bump that Limit Increase per Layer setting up to 25 or so, hopefully that will resolve the issue.

Jonathan

[texsc98]

Ha that was it, awesome!

Yea I had noticed it had a slight delay between the change and the actual recalc... But didn't realize the limit increase/layer actually needed to be set > 0. I guess I assumed if it was 0 or lower that layer 2 would be "default" speeds. Good to know!

Everything seems to work as expected now with relation to build cost/duration that tweak to my settings, thanks so much!!

[joestefano]

Has CubeitMod caught up to the newest version yet?

[mhackney]

Jonathan, I sliced my entire fly reel model with the new release and verified the improved paths we talked about a few weeks ago. It all sliced and printed nicely. And, I am continuing to love the independent suck/prime speeds.

cheers,
Michael

[kas]

Received a couple fault errors while trying to run KISS 64 and 32 bit.
Right after running the new beta of KISSlicer64.exe I received the dialog box showing the four .ini files needed. My system froze and forced a restart.

Is it possible I'm missing a dependency needed by KISS?

The event viewer showed this:

Code: Select all

Faulting application name: KISSlicer64.exe, version: 0.0.0.0, time stamp: 0x54e40141
Faulting module name: ntdll.dll, version: 6.3.9600.17630, time stamp: 0x54b0e17a
Exception code: 0xc0000005
Fault offset: 0x000000000001f0b2
Faulting process id: 0xe5c
Faulting application start time: 0x01d04bef15f02b03
Faulting application path: C:\Users\Kevin\Desktop\KISSlicer_Win64_1.5beta2.15\KISSlicer64.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 53ebde50-b7e2-11e4-826f-94de80a7c247
Faulting package full name: 
Faulting package-relative application ID:

I tried the 32 bit version and able to catch this report of the error.

Code: Select all

Version=1
EventType=APPCRASH
EventTime=130687886112602224
ReportType=2
Consent=1
UploadTime=130687886113356839
ReportIdentifier=e1d64531-b7e3-11e4-826f-94de80a7c247
IntegratorReportIdentifier=e1d64530-b7e3-11e4-826f-94de80a7c247
WOW64=1
NsAppName=KISSlicer.exe
Response.BucketId=d91ae8c6834b83989559954ab5c170f2
Response.BucketTable=1
Response.LegacyBucketId=73882762387
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=KISSlicer.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=54e40157
Sig[3].Name=Fault Module Name
Sig[3].Value=KISSlicer.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=54e40157
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0011656f
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5861
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=a10f
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=a10ff7d2bb2516fdc753f9c34fc3b069
UI[2]=C:\Users\Kevin\Desktop\KISSlicer_Win64_1.5beta2.15\KISSlicer_Win32_1.5beta2.15\KISSlicer.exe
UI[3]=KISSlicer.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Users\Kevin\Desktop\KISSlicer_Win64_1.5beta2.15\KISSlicer_Win32_1.5beta2.15\KISSlicer.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\COMCTL32.DLL
LoadedModule[6]=C:\Windows\SYSTEM32\COMDLG32.DLL
LoadedModule[7]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[9]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[10]=C:\Windows\SYSTEM32\OPENGL32.DLL
LoadedModule[11]=C:\Windows\SYSTEM32\SHELL32.DLL
LoadedModule[12]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[13]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[14]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[15]=C:\Windows\SYSTEM32\SHLWAPI.dll
LoadedModule[16]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[17]=C:\Windows\SYSTEM32\GLU32.dll
LoadedModule[18]=C:\Windows\SYSTEM32\DDRAW.dll
LoadedModule[19]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\Windows\SYSTEM32\DCIMAN32.dll
LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\Windows\SYSTEM32\SHCORE.DLL
LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[24]=C:\Windows\system32\IMM32.DLL
LoadedModule[25]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[26]=C:\Windows\system32\uxtheme.dll
LoadedModule[27]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[28]=C:\Windows\system32\dwmapi.dll
LoadedModule[29]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[30]=C:\Windows\system32\rsaenh.dll
LoadedModule[31]=C:\Windows\SYSTEM32\bcrypt.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=KISSlicer.exe
AppPath=C:\Users\Kevin\Desktop\KISSlicer_Win64_1.5beta2.15\KISSlicer_Win32_1.5beta2.15\KISSlicer.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5656B4B485F97F9AB99E61F016FCAAED

[kas]

As an update to the post above. I copied the four .ini files that mhackney posted at the SeeMeCNC forums to the directory of both 64 and 32 programs and 2.15 Beta now opens with no issues and no errors.

[lonesock]

OK, thanks. I had another email reporting the same bug, and I think I found it. I will try to post an update tomorrow.

Thanks for your patience!

Jonathan