1.5 beta 2.22 top layer bug?

Post Reply
User avatar
voyt
Posts: 27
Joined: 15 Nov 2015, 07:20
Contact:

1.5 beta 2.22 top layer bug?

Post by voyt »

Hello everybody,
I decided to migrate from good old 1.1.0.14 version to current beta, and I get some strange effect while slicing "3D Benchy boat"...
(windows 64bit)

Maybe I'm doing some simple mistake... (on 1.1.0.14 it slices/print perfectly) Any idea, anyone?..
(I've got a PRO version)
KISSLICER-1.5-BETA-2.jpg
Thanks!
euroreprap.eu
User avatar
plexus
Site Admin
Posts: 114
Joined: 02 Sep 2014, 21:39

Re: 1.5 beta 2.22 top layer bug?

Post by plexus »

I just sliced it with 1.5 b2.22 and I do not see the paths you are getting. can you post your main settings and also the STL to ensure that I am using the same settings and model?
User avatar
voyt
Posts: 27
Joined: 15 Nov 2015, 07:20
Contact:

Re: 1.5 beta 2.22 top layer bug?

Post by voyt »

Hello,
Sure - here is the link to the zip. STL and .ini files are enclosed. (only one preset "BIB 015" which is actually used for 0.2mm layer printing)

https://www.dropbox.com/s/0lp1urscrxp12 ... m.zip?dl=0

Later on I found the problem disappears if I print with 0.15mm-height layers. But... I like printing with 0.2..... ;)
euroreprap.eu
User avatar
voyt
Posts: 27
Joined: 15 Nov 2015, 07:20
Contact:

Re: 1.5 beta 2.22 top layer bug?

Post by voyt »

Jonathan,
could you please examine the issue shown on the above images? Id didn't happen on 1.1 releases. It only appears when you slice to 0.2mm layers..
Not a tragedy, but maybe this is something worth taking into consideration when working on v2...
(On beta 3.6 also it's there..)
Thanks
euroreprap.eu
User avatar
lonesock
Posts: 258
Joined: 09 Nov 2014, 18:41
Contact:

Re: 1.5 beta 2.22 top layer bug?

Post by lonesock »

That looks like a numerical precision issue. I can duplicate the problem here as well. I'm guessing the deck is on an exact multiple of 0.2 mm? It works OK if I set the layer thickness to 0.2001 mm, which should give (nearly) identical G-code output. It's a hack, I know. I will look into this for the 2.0 release.

thanks,
Jonathan
Post Reply