Cura 2.3.1

[LePaul]

Okay Nallath...I see the posted changes....anything else in the works

Cura 2.3.1 - November 8, 2016

Added the layer height to the profile selection menu.
Fixed a bug where editing material settings has no effect on 3D prints.
Fixed an issue with automatic profile importing from Cura 2.1 on macOS.
Fixed an issue with g-code importing from related machines as a profile.
Fixed an inheritance issue for dual extrusion.
Fixed an issue with “i”symbol updates.
Fixed a freeze that can occur while printing via Wi-Fi.

[nallath]

I think there are a few more bugs fixed, but these are the most notable.

[Amedee]

Rant of the day...

Working on a new project, so I decided to upgrade from 2.3.0 to 2.3.1 before slicing.

Cura didn't want to start, so I started in console mode and saw a python stacktrace apparently due to some customization I did (I have my own machine definition).
So I removed that machine and it went through...

... but the real reason of the crash was actually leftover settings from 2.1.X

On Mac, there was a bug in 2.3.0 that 2.1 settings were not migrated. So when I went to 2.3.0 I rebuilt my profiles, re-set preferences and so on.
But now that bug is fixed and suddenly Cura migrated my old profiles in 2.3.1 as well, so my environment is a complete mess
Not to speak about my 'visibility settings' which are apparently gone again.

This is a real pain for what should be a minor update -- I am about to give up on Cura...

[LePaul]

I feel your pain

If you work with two printers like I do, with different types of material, it's a clusterfuck to loose all your good settings. I wish Cura gave you a simple way to add in your own settings for this filament, etc.

It's a close tie which has me to most annoyed. The Ultimaker 2+ or Cura.

[Izzy]

I haven't used Cura for a month or so now, I feally like S3D now.
I have even set the two macros so that I have a 2 button temperature set for atomic pulls, 1st one set print head to 215'C,2nd one to 95'C. So easy to use.

The only thing is for my test prints, I want the file to use the machines selected material and not define it in S3D, I'm sure one of you guys will tell me what i need to do in the S3D settings to sort this but at the moment I set it to start the print then override the temperature settings on the machine or the USB link.

[LePaul]

Well you know Neotko is the expert!

[nallath]

There was a bug in the 2.3.0 beta that didn't allow you to upgrade settings.

Beta's are always are your own risk (the entire point of a Beta is finding out if there are any issues left that must be fixed)

[Neotko]

I haven't used Cura for a month or so now, I feally like S3D now.
I have even set the two macros so that I have a 2 button temperature set for atomic pulls, 1st one set print head to 215'C,2nd one to 95'C. So easy to use.

The only thing is for my test prints, I want the file to use the machines selected material and not define it in S3D, I'm sure one of you guys will tell me what i need to do in the S3D settings to sort this but at the moment I set it to start the print then override the temperature settings on the machine or the USB link.

So you want S3D to use UltiGcode instead of Reprap... It should be doable I think. It would require some scripting like tinkergnome and I did to make a fake Griffin flavor for um3. Ofc I can't test this since I don't have um2, but your best bet is to download the um3 profile and check how we did insert a fake header, and using that you could replicate the ultigcode header to forget the temperature of s3d and let the machine use the profile.

[Amedee]

FYI for the TweakAtZ addicts...

I scratched my head hours reading the code and looking at the diffs to understand why my favorite plugin^h^h^h^h^h^h post processing script wasn't working anymore -- or at least not consistently.

It turned out that the culprit is CuraEngine which does not print leading zeros anymore. I submitted a pull request to review for TweakAtZ, but you can easily fix that in your local copy...

[MTVDNA]

I tried Cura 2.3.1 today and I must say it has improved a lot. Layer view is really really fast now which is great. Also features like infill layer thickness are very nice, if I recall correctly that wasn't in there before. That can sometimes save lots of printing time.

[MTVDNA]

I tried to run the print as sliced by Cura, but unfortunately the results were not acceptable. For some reason, while printing infill there are a lot of unnecessary retractions, causing blobs and just poor infill. It would literally print 1 line, retract, move over 0.4mm, print another line, retract, etc. I hoped this would be better when the second layer came over it, but unfortunately it was the same. So I went back to S3D for printing it.

I marked the bad infill with red but you need to zoom in to see it.

[nallath]

I think this is fixed for 2.4

[nilrog]

Is it just me...or is Cura annoying to work with?

I started using it a lot more now that my own printer is up and running. And yesterday I was filling the build plate with a bunch of objects, where I loaded only three objects but then duplicated the ones I loaded. And for every object I duplicated, or at least way too often, Cura was twisting and turning the build plate for no apparent reason at all...to the point I was ready to throw it out of my laptop

And I have "ranted" on this before...auto-slicing...it's the worst "feature" of them all

[Neotko]

Is it just me...or is Cura annoying to work with?

I started using it a lot more now that my own printer is up and running. And yesterday I was filling the build plate with a bunch of objects, where I loaded only three objects but then duplicated the ones I loaded. And for every object I duplicated, or at least way too often, Cura was twisting and turning the build plate for no apparent reason at all...to the point I was ready to throw it out of my laptop

And I have "ranted" on this before...auto-slicing...it's the worst "feature" of them all

https://ultimaker.com/en/community/2348 ... k-tutorial

[nilrog]

It's a pity we,as end users, have to go through such hoops when it would be so easy to solve this in the app...