Page 5 of 6
Re: Cura 2.1 open beta
Posted: May 20th, 2016, 12:50 pm
by johan
Has anyone here moved to using Cura 2.x.x as their standard slicer or is everyone still using 15.04.x?
Re: Cura 2.1 open beta
Posted: May 20th, 2016, 12:57 pm
by Dim3nsioneer
I'm productive on 2.1. Didn't regret it so far. But I have S3D as backup for the worst case.
Re: Cura 2.1 open beta
Posted: May 20th, 2016, 2:29 pm
by drayson
I´m still on 15.04 for productive work but testing the usability and behavior of 2.1 so far.
But as far as the second nozzle is not supported especially in terms of support material settings (separate temperatures for print/standby, flow, nozzle diameters), it´s not very usable for me...
Re: Cura 2.1 open beta
Posted: May 20th, 2016, 3:23 pm
by LePaul
I've stuck to 15.04
Re: Cura 2.1 open beta
Posted: May 25th, 2016, 4:00 am
by nallath
The undo stuff is broken, but due to wanting to release things, we had to make decisions on what to fix (and what not to). I think we already fixed the undo / redo stack for 2.2
Re: Cura 2.1 open beta
Posted: June 7th, 2016, 2:07 pm
by Amedee
Re: Cura 2.1 open beta
Posted: June 7th, 2016, 2:41 pm
by LePaul
Yeah I got the mass mail announcement in my email this morning.
Re: Cura 2.1 open beta
Posted: June 7th, 2016, 3:04 pm
by Dim3nsioneer
That means the amount of bugs it has right now has to be considered as normal...

Any breaking news since 2.1.1?
Re: Cura 2.1 open beta
Posted: June 7th, 2016, 3:22 pm
by LePaul
I haven't seen many posts on the Ultimaker site about issues....yet

Re: Cura 2.1 open beta
Posted: June 7th, 2016, 3:27 pm
by Izzy
Ok so I've downloaded the new Cura and loaded a simple file to test and check
And in the bottom right corner it says "Preparing to slice..,"
And it's been like that for five minutes
I've rebooted the computer but no joy, so it's back to the previous version untill I can find the problem

Re: Cura 2.1 open beta
Posted: June 7th, 2016, 3:30 pm
by Amedee
Dim3nsioneer wrote:That means the amount of bugs it has right now has to be considered as normal...

I'm afraid we will have so survive quite some bugs... There are still quite some open issues in Github, plus the ones I still have to report
But the engine itself is solid, so that's quite OK.
Dim3nsioneer wrote:Any breaking news since 2.1.1?
No idea, the release notes are for 2.x so it doesn't highlight latest changes...
At least they have included your latest TweakAtZ so it won't crash anymore

Re: Cura 2.1 open beta
Posted: June 7th, 2016, 3:41 pm
by Dim3nsioneer
Amedee wrote:
At least they have included your latest TweakAtZ so it won't crash anymore

Nallath allowed me to write directly to the Postprocessingplugin repository some time ago...

Re: Cura 2.1 open beta
Posted: June 8th, 2016, 3:33 am
by nallath
Izzy wrote:Ok so I've downloaded the new Cura and loaded a simple file to test and check
And in the bottom right corner it says "Preparing to slice..,"
And it's been like that for five minutes
I've rebooted the computer but no joy, so it's back to the previous version untill I can find the problem

Ugh. I swear to god this freaking issue keeps on popping up. It must be our personal Nemisis. Could you send me the logs (see
https://github.com/Ultimaker/Cura#logging-issues for info on which I need)
Re: Cura 2.1 open beta
Posted: June 8th, 2016, 3:45 am
by Amedee
I sliced a lot with Cura 2.1.1 over the past weeks, and I got that from time to time.
Sometimes I could get rid of it by changing some parameter to force a re-slice, sometimes I had to restart Cura...
I haven't installed 2.1.2 yet as I have nothing to print right now

(and upgrading is a bit of a pain as some of my customization are stored in the software tree, so I have to double check and copy them over...)
Re: Cura 2.1 open beta
Posted: June 8th, 2016, 10:09 am
by martin-bienz
...could also be, in my case at least with UMO selected, that you have selected print "one at a time" and the object is to tall, then selecting print all at once solves the issue... (even there is only one object)... strange behaviour (2.1.2). Just guessing, happend to me.