Page 6 of 6

Re: Found a way to get CubeitMod to work with newest Kisslic

Posted: 27 Apr 2015, 09:21
by jonny.m
And here it is: CubeItMod5B5

Changes since last version:

Fixed a bug on the new Solid Speed reduction.
The speed change between normal Solid Speed and Short Solid Speed can now be adjusted.
Small Loops and Perimeters can be printed at lower Speeds. Only usefull if you have multiple small loops per layer.

I updated the description to show how the new features work, let me know if you have any comments on it. It also includes a "Initial Setup" to guide newbies through the first steps with Kisslicer and CubitMod.

Since CubeItMod becomes more and more complicated with things that might not always be neccessary I decided to work on a simpler, user friendly version which might be enough for most printing jobs. Hope to finish this one soon as well.

Regards,
Tobi

Re: Found a way to get CubeitMod to work with newest Kisslic

Posted: 27 Apr 2015, 13:26
by joestefano
That sounds good, It is getting a bit complex for the average user. I'll give this version a try and get back to you. Thanks for all your hard work!

Re: Found a way to get CubeitMod to work with newest Kisslic

Posted: 27 Apr 2015, 13:42
by joestefano
Tobi, where is the 5B5 exe? it is not in the folder just the .po file

Re: Found a way to get CubeitMod to work with newest Kisslic

Posted: 27 Apr 2015, 14:09
by jonny.m
Hm, maybe your firewall or antivirus software ? Just tested it on two devices and the .exe is there. I attached it here again, renamed as .txt and zipped it with password protection (password: cubeitmod). Hope that works for you?

The folder I posted before contains two subfolders:
Folders.png
Folders.png (2.52 KiB) Viewed 3867 times
And this is the content of the two folders:
1..png
1..png (6.52 KiB) Viewed 3867 times
2..png
2..png (13.21 KiB) Viewed 3867 times
Is anyone else having this problem as well?

Regards,
Tobi

Re: Found a way to get CubeitMod to work with newest Kisslic

Posted: 27 Apr 2015, 14:40
by joestefano
Got it. it was my Norton blocking it, all set