bot

When I mean visualization, I mean layer by layer visualization... with the infill completely laid out to the top... you know the part where cura says "Loading toolpath for visualization" The wait for that, combined with re-slicing, can take quite some time. If it is a bug that's causing this, I'd be surprised.

Take a look at your Holyness the software developer. I'm done. I came here to try and give you guys feedback. Have fun with your little computer program. Edit: Oops... that last comment was snide, wasn't it?

I have the data to back up my assumptions of the developer, now too.

How many times must I explain the problem clearly? It's not hanging... it's not a bug... it's just bad implementation of auto slicing. THAT'S THE PROBLEM. Say you have the terminator model I linked to loaded up, at 0.1mm or less, and you change a setting. How long does it take to go from seeing a visualization, changing a setting, and then seeing the visualization again?

A good reason to implement a feature is to save your users hours of aggravation because your software assumes its users are dumb.

I'm not saying it freezes up. It just takes a long time to slice then re-generate the visualization. This is pointless if I accidentally changed a value... Oh, and at a .1mm layer height, make sure. Sometimes 14.09 will fail to completely slice the model... I presume due to memory limitations. And we're back to comparing 64 bit vs 32 bit... This is an issue if you actually USE the software. I use it. I print constantly, none-stop. I strive to NOT WASTE 10 minutes waiting for a model to re-slice just so I can see the visualization I was trying to inspect...

Load up these models: http://www.thingiverse.com/thing:455609 scale them to 1.6 Slice them, inspect the visualization and then accidentally nudge the model by clicking it or accidentally typing into a text box when you didn't know it had focus... and tell me that isn't a perfect use case for "don't slice unless I tell you to." Don't get me wrong... when I eventually get the slice I want it's fine: http://imgur.com/a/GtFMN

I don't want you to think I don't love Cura for the amazing things it does... and freely. I simply urge you to change your mind. It's a simple option, it can be tucked away if you like.. it can be enabled by modifying an ini file... whatever you need to do to ease your stubborn mind. Clearly a majority of users want the option to disable auto-slicing.

You don't actually use your software for anything other than printing tiny useless junk, eh? When you start dealing with larger, more complex pieces, your "logic" flies out the window. What a ridiculous company. I certainly will be looking into other software options, and I will stop recommending the UM2, as that has been my go-to recommendation when asked by people. I understand what it's like being an "un-nice person", Daid. I am one too. The difference is, I'm right.

Oh and, you know maybe I WAS in the market for a cartesian printer. With an attitude like yours, Daid, I think I'll be steering clear of UM.

I have explained to you multiple times why your logic is flawed. A million pictures of spock won't change my mind that you are wrong here. It's not logical to have it setup this way. Sure, it allows an uneducated user to stumble around and avoid.. pressing one button? Yet they have to set all these complicated settings... hmm. It doesn't add up. You need to get off your high horse and implement the flipping checkbox that says "don't slice yet" or "ready to print." You didn't even understand my point from the first part you quoted in your last post on this thread. If the developer uses the software, they are now the user. It was a joke. I'm starting to question your logic and reasoning skills, now. This explanation of "calculating a bounding box" does not make sense. Is that the process that takes 2-5 minutes or more sometimes? I doubt it.

But why does it have to slice every time you change any parameter, even by accident? At least give us an option to say "ready to slice" with a radio button near the save to SD button.

Software can't be made for the developer... once the developer uses it, he/she becomes a user.

Hmm I've never had this issue with Cura. It does first layers fantastically with or without combing or retraction. Are you guys/girls running heated beds? This sounds just like an adhesion issue, not a slicing issue. Painters tape works pretty well, but I've had the best luck with the purple coloured glue stick.

Are you looking to pick up speed by avoiding the comb? Or are you worried about it affecting the print quality? I quite like the way cura performs combing with the retract while combing plugin enabled (with a relatively high 3mm or greater minimum distance for retract on the plugin). If you're looking to pick up speed by skipping the combing moves, I dunno.

Daid do you use your own software to actually 3D print things? Beause I do, and this is the absolute worst part of using your software. I have a large build platform, but it's not really larger than a UM2, so it's ludicrous the way cura handles large print layouts and large models. Not to mention my computer is not lacking. SSD, i7, 16GB ram, etc... Software isn't made for the developer, it's made for the user.

edit: this post was full of stupid.

A very succinct answer to number one. I shall find another slicer. Thanks. As for the number of polygons for number 2... I don't know. It doesn't require many. Simply multiple pieces on the plate, a circular bed plate, and one piece being half on and half off the grid. It only freezes the first time this happens, it seems, with a set of models on the plate.

There are a few things I don't like about Cura, but many things I love. These issues haven't forced me to go back to any other software, but it's becoming frustrating. 1) There NEEDS to be a "slice now" button, instead of automatically slicing any time an object is place. In fact, the program should ONLY make a new set of gcode when I tell it to, otherwise it is VERY annoying to accidentally bump a model a few mm and have it start slicing again. This is not optional, I don't know why the program works the way it does now, i'ts nonsensical. 2) When an object is moved so that it is partially on the build area and partially off of it, the programs hangs for some time. Just FYI. 3) I know, I know, python is 32 bit... but this needs to change. I'm constantly running into memory limitations, and the 14.11RC7 I also have doesn't always solve that. These and other small issues I'm forgetting add up to a LOT of frustration when using Cura. Besides that, thank you for the wonderful free software!