Cura wishlist

[Dim3nsioneer 557]

You may also export support and model together and import the new model in Cura.

[danilius 118]

I tried 0.4mm walls, but Cura prints them as two lines, unlike the support it generates itself which are much cleaner.

Dim3nsioneer, I'm not sure what you mean, but I created custom supports in Blender, and exported them with my model, but I am after 1-line wide supports that I can create in Blender, which currently is not feasible. Unless, of course, someone has pulled it off!

 

[izzy 33]

1 feature I'd like to see under the advanced maintenance is to be able to move the print head to the front centre making it easier for Atomic Pull cleaning, as well as cleaning the nozzel of muck and changing the nozzel.

[dodgrr 27]

+1 on the printhead centering for atomic pull purposes.. also, I'd like a warning when writing to SD card that there's another file with the same name that previously exists, and I'd like to be given the opportunity to save with a modifier tag ie filename_1. Freaking awesome software BTW, huge thanks for allowing requests to be thrown out here!!

 

[kvones 5]

I would like a button to implement slicing rather than have Cura do a 'real-time' slice everytime I change a parameter. Sometimes I try to change two or three settings, and Cura is already busy re-doing the slice before I have had a chance to put a number in! Then of course everything crashes...

Or is there already a way to stop Cura from doing this that I don't know about?

 

[jweaver 2]

I would like a button to implement slicing rather than have Cura do a 'real-time' slice everytime I change a parameter. Sometimes I try to change two or three settings, and Cura is already busy re-doing the slice before I have had a chance to put a number in! Then of course everything crashes...

 

Or is there already a way to stop Cura from doing this that I don't know about?

 

One of the devs wrote a fix for this in a previous release (i think it was 14), but Daid is dead against this functionality, so it was never added into the product.

So you can have this functionality, but you will need to run an old version.

I just looked back at my old installed versions and this was available in 14.12.1.. You simply had to replace the modified "sceneView.py" and engineResultView.py" files..

 

[nallath 1,120]

So the problem isnt the automatic slicing, but the crashing if it needs to slice something. Could you give us the logs? Changing the auto slicing will only hide the problem, not fix it.

 

[danilius 118]

A nice option would be to be able to specify geometry as being support, that way one could create a solid object that CURA will convert into support. Sometimes CURA generates no support at all even though it is needed, or the supports generated are a poor choice. This is hardly surprising since we cannot expect the programmers to be able to figure out every possible scenario, and it means making custom support much, much easier to remove.

 

[tsagos 8]

May I ask to get cura to do less movement during each layer, and not change its mind midway.

Example: If you have a square, to go from point A to point B to do the infill in one move.

Not from A to D then C and then B.

Less oozing problems. less time printing, fewer defects.

 

[Dim3nsioneer 557]

Yes, less travel moves would be much appreciated. But we have to be aware that this ends up very quickly in solving the travelling salesman problem. Certainly something worth to have a deeper look into for the new Cura.

 

[david-ganon 2]

please do this !!!!!

1. i want to print the walls with no infill and no bottom !!!

i know, there is such option, but it is no good if the print has no support !!!

the infill is not good all the time for this.

let's say i want only 5% infill. only to make the model a bit stronger.

in addition to that, i want support "in the model" were the 5% infill is not going to support the model.

so... please add "inside model support" option !

it will be so great, and save time.

2. let me turn on or off what i want to print

inner wall, outer wall...

thanks

 

[david-ganon 2]

and one more thing !!!!!!

lease make the print area settings better !!!!

my advice.... give me the option to move the print head to the place i want and tell the um2 to make it origin. so it will be the corner of the print area !!! and then i will tel the printer the size of the print area.

just solve that problem please

 

[glorfindel 0]

A couple from me as well...

- set different speed at different layers (like Tweak At Z, but without using M220 as it will cause everything to change speed). I ask this because I would like to print at very different speeds (like one cube at 50 and the figure on it at 5).

- a minimal Z movement up everytime there is free travel. This is to avoid the hotend impacting existing parts while it is traveling (I print parts with lots of homemade supports and it happens frequently that the hotend slams into one of them knocking it down). If the hotend goes up a fraction of mm, moves, and then goes down again this risk is minimized.

Thank you

 

[kvones 5]

One of the devs wrote a fix for this in a previous release (i think it was 14), but Daid is dead against this functionality, so it was never added into the product.

So you can have this functionality, but you will need to run an old version.

I just looked back at my old installed versions and this was available in 14.12.1.. You simply had to replace the modified "sceneView.py" and engineResultView.py" files..

 

14.12.1 is the version I am currently running! I am not sure what you mean by replace though, where would I switch these files out? And why is Daid set against having this?

 

[Dim3nsioneer 557]

A couple from me as well...

- set different speed at different layers (like Tweak At Z, but without using M220 as it will cause everything to change speed). I ask this because I would like to print at very different speeds (like one cube at 50 and the figure on it at 5).

- a minimal Z movement up everytime there is free travel. This is to avoid the hotend impacting existing parts while it is traveling (I print parts with lots of homemade supports and it happens frequently that the hotend slams into one of them knocking it down). If the hotend goes up a fraction of mm, moves, and then goes down again this risk is minimized.

Thank you

 

The current version of TweakAtZ (bundled with Cura 15.02.1) also supports tweaking the print speed only without altering the travel speed.

The lifting and lowering feature is called zhop and can be found in the expert settings of Cura.

[jweaver 2]

14.12.1 is the version I am currently running! I am not sure what you mean by replace though, where would I switch these files out? And why is Daid set against having this?

 

Probably not worth starting this disucssion. It got quite heated last time and once one of the team wrote a fix, but Daid has strong feeling about this and it never evolved into the current versions,

Here are the details

http://umforum.ultimaker.com/index.php?/topic/8574-cura-autoslicing-poll/

I am sure if you put a post in thwt thread asking this, someone will might update the "fix" so its compatible with v15

[glorfindel 0]

The current version of TweakAtZ (bundled with Cura 15.02.1) also supports tweaking the print speed only without altering the travel speed.

The lifting and lowering feature is called zhop and can be found in the expert settings of Cura.

 

I did not know about zhop, thank you very much you saved my life!

As for TweakAtZ I tried setting print speed only, but it didnt work, printing speed did not really change (I set it to 10% but the change was barely noticeable)

Thank you again

 

[Dim3nsioneer 557]

If you send me the gcode file to dim3nsioneer@gmx.ch I'll have a look at it. Any other information about your TweakAtZ settings might help as well.

[kvones 5]

Wow, thank you for that - I didn't know it was such a big issue!! Tbh though, I don't really get the extreme resistance to what is an optional feature. Just giving someone a choice does not mean they disagree with your design decision - my laptop is somewhat of a robust pensioner, creaky but perfectly capable most of the time. However, the real-time slicing is clearly too much for it, so for me, it would be great to have a button to control it. And yes, I could use another program of course, but I have just got such great results with Cura that I wouldn't want to. Will stick with it for that reason, but sad this feature will likely not see the light of day. :-|

 

[jweaver 2]

Wow, thank you for that - I didn't know it was such a big issue!! Tbh though, I don't really get the extreme resistance to what is an optional feature. Just giving someone a choice does not mean they disagree with your design decision - my laptop is somewhat of a robust pensioner, creaky but perfectly capable most of the time. However, the real-time slicing is clearly too much for it, so for me, it would be great to have a button to control it. And yes, I could use another program of course, but I have just got such great results with Cura that I wouldn't want to. Will stick with it for that reason, but sad this feature will likely not see the light of day. :-|

 

As you are running 14.12.1, just get the 2 files from the thread I posted above and you can have the functionality you want....

 

[nallath 1,120]

Most of us are against the function of not automatic slicing, because people make the (wrong) assumption that because it's automatic that this is the thing that causes the problem.

Like I said; Making it not automatic hides certain symptoms, it doesn't fix them. I personally don't believe in hiding symptomps, i believe in fixing them. Making the slicing automatic shows the symptomps, which get reported (usually with people writing capslock messages or calling us stupid ), which can then be fixed.

This discussion has been going on for months already and every single time someone said it was the automatic slicing that caused the problem, it turned out to be something else. I think its a bit more of a boy who cried wolf.

 

[3dcase 37]

1 workaround;

Being one of the people asking (politely :-P) for a slicing button for, I guess, 2 years.

When waiting takes me to long, move the print outside the printarea (turns grey) do your rotating, scaling or settings, and move it back on the printbed.

1 Wish;

I would like to have a random infill, like there was in the 11... and 12.... versions.

I know the square infill will be stronger, but printing models, lamps or decoration things, most of the time the infill is visible.

So Please, give us the option again.....

 

[nallath 1,120]

Waiting? You don't have to wait for the slicer to finish. The fact that your UI freezes has nothing to do with the automatic slicing. The engine is started as a seperate process with the lowest priority. If any process requires resources (GUI, other running programs) they get it before the slicer gets it.

So, like I said, you are attacking something that exposes a symptom of a problem, not something that actually a problem.

 

[3dcase 37]

Waiting? You don't have to wait for the slicer to finish. The fact that your UI freezes has nothing to do with the automatic slicing. The engine is started as a seperate process with the lowest priority. If any process requires resources (GUI, other running programs) they get it before the slicer gets it.

So, like I said, you are attacking something that exposes a symptom of a problem, not something that actually a problem.

 

Well, I guess that is what "average" users/customers/patients can do. Try to deal with a symptom, work around it, take a painkiller and hope for a expert, a programmer in geldermalsen or a doctor to find and hopefully cure the problem.

But as the topic says, its a wishlist, nobody is demanding something...

But perhaps one day someone concludes its less effort to spend an hour on implementing a manual slice option, than explaining their point of view and that its somebody else's problem.

 

[nallath 1,120]

If you hide the symptom, we don't know about it. I would be a very bad 'doctor' if i'd help my 'patients' hide the real problems. To push the anology a bit further; We won't give you painkillers for a headace, because every time someone asked for the painkillers, it turned out that it was something else that was causing the headace.

A patient should, in my opinion, never ask for a specfic solution. They should notify the specialist of the problem, provide the data of the case and wait for a solution. In this case, people have been asking for a specific solution that doesn't solve the problem, it hides it. (Imagine going to a doctor claiming that you need a specific type of anibiotics because you big toe hurts. It's unlikely that you will get it )

We've had quite a few error logs & data from users who had the same problem and we've been able to fix it for them. So users can do more, they can give us the data we need to fix it.