bot

Also, it seems that plugins periodically, randomly, and intermittently get disabled for no reason, even though they are shown as enabled and configured. As an example, Retract while combing (the older version) failed to be implemented on the print I'm doing now, even though it's clearly enabled in the gui.

Okay, but if you look closely, the slicer is missing lines. They are filled in on some layers, but don't appear on others. There is definitely enough room to have a .35mm line there. Trust me, these gaps do not get filled. I have an accurately built machine. Using less perimeters is a work-around I did use, but sometimes I need so many perimeters. So how about fixing this bug?

Hi. Sometimes I get gaps in my slicing, as follows. They do translate to gaps in the print surface. http://imgur.com/a/F8LF9

Yeah, good thing I'm able to solve the problem now by disabling the auto-slicing!

Well, I have 16GB of physical memory here, so if anything the python process would run out of places to allocate memory... (is that the right way of putting it?)

You know what it might be (a wild guess here), I'm running an SSD, and cura is running off the SSD. and I have my appdata and other folders moved to another hard drive (kinda hacky). I wonder if that might have anything to do with it...

Oh... yeah. I forgot, sorry. I was expecting to see the button right away. This is FREAKING AMAZING! You just saved me so much frustration. Perhaps I will stick with Cura. Thank you, PM_Dude.

Interesting, daid. Are you running a PC? Windows 7? Do you have MS Security Essentials enabled? I wonder why my machine has trouble killing the process... And PM_Dude, copying that file over does nothing for me...

Rc2 certainly seems MUCH better, at least in that one scenario I showed on the video. I do like helping you squash these bugs, but I'd still think I'd like to have a manual slice OPTION. Another bug, but it's kinda user error, is when I switch to the layer view pre-emptively, before the thing is ready, I get a frozen screen, rather than being able to switch back to the normal view. Perhaps just greying out the layer view button until it's ready would work.

Should I try rc3? I'm gonna install rc2 and wait on your "go-ahead" for trying rc3.

Did you see my video?

Somebody tried this with 14.12 and the issue is still there. There seems to be a retract every "layer" change."

I will download it and try it out! Thank you. What changes did you make? (dumb it down for me, please! )

Well, the issue isn't the g-code viewer itself. I can handle it taking a while to load. I just hate accidentally having it load again. But there does seem to be an intermittent issue where it takes a LONG time to do some things before even getting to the g code preivew... I'll try to pin point some more specific details to recreate the scenario, but things are going smoothly for now (I think it relates to the number of triangles in a model).

Hahaha yeah... I'm still wary about it. But you know as they say, if I'm a paying customer then I really have a reason to complain.

Oh nice I didn't know you could just copy and paste a new install. If I wasn't in the middle of the biggest and most nerve-racking print job yet, I'd mess around with it. Thanks for the advice though. And also on that note, I'm kind of an idiot... I didn't realize there was a current release newer than 14.09. Oooops. I bet it'll fix most of the slowdown hassles... was 14.09 the release with the "SD bug" you talk about?

Yzorg, I think I'm in the same boat. I'm going to be getting a licence for S3D and using Cura for the times that S3d will fail me (because nothing is perfect, right?). And yes, Nallath, at least I realize someone was kind enough to code a stop button (or however you'd like to call it). Here is the link for others not aware: http://umforum.ultimaker.com/index.php?/topic/8574-cura-autoslicing-poll/?p=81528 Thanks again to everyone and sorry again for my confrontational attitude. It's almost like I knew what was coming and had to put up a hard front... or I'm just an "un-nice person."

Thanks. And to be honest, I'm busy printing, I simply do not even have the time to interrupt these activities to modify the program. I really appreciate the effort though. And I appreciate the encouragement and sentiments. I COULD figure it out, you're right, but taking on the actual printing right now is presenting enough of a "challenge." I wasn't expecting clients to be coming in so quickly...

I must admit my original post could have used a different tone. I apologize. :mrgreen: It was very early in the morning and I had not slept. Bad combo for ranting on the internet I guess. I'm excited for Pink Unicorn. Would I still need to run a linux partition to get 64 bit?

Thanks. Was that so hard? I haven't tried it out yet, and I'm sure I'll get lost in the process and have to ask my brother for help. But thank you. I wouldn't have been able to do that in less time or effort than this "arguing."

I've also been having trouble with Cura failing to finish writing the Gcode completely. It's hard to pin point the exact circumstances it's happening under, though.

I do love open source. I simply don't have the time or skills to modify the program to suit my needs. My skills and time are devoted to 3D printing... this software should enable that, not hinder it. What colour is the pill UM ships with their printers?

We can only guess that if the representatives of UM believe that all of Cura users are dumb, and most UM purchasers use Cura, it must follow that UM representatives believe most UM users are dumb? That's logic for you.

MSURunner is correct. I essentially want the ability to lock down the build plate. I also don't want the process to begin again if I tweak a setting accidentally. Also, sometimes I like to tweak a lot of settings really quickly, and the starting and restarting of the process (we won't call it slicing anymore we'll call it "the process") bogs that down a tiny bit. Though, the only reason I have to slice things five times is because the software forces me to. I am a very experienced user, I know how something should look when sliced. I've also learned NEVER to print something without making sure it sliced how you wanted it first. I seldom get a failed print. I LOVE CURA! I just hate working with it sometimes. Part of it is that I want to have the exact G-code of the print I have going up on the screen, but also with the ability to modify the settings if a consequent print is needed. Saving the gcode to a file doesn't allow me to tweak the settings and the load profile from gcode function doesn't seem to work (could be plugins causing interference?). So... what it comes down to is that I want to maximize efficiency while working with Cura. Right now, I'm constantly being set back 2, 5, 10, 20 minutes and more because the software is constantly processing things when I don't want it to. Can I be any more clear? I honestly want to try and help you make this software even better than how amazing it already is.