Found an interesting bug in Cura today, anyone else seen this?

Found an interesting bug in Cura today, anyone else seen this?

I upgraded to the latest version and tried printing the built-in Ultimaker robot guy using mostly default settings, and controlling the printer via Cura itself, just to use that configuration as a baseline. Overall it went very well!

So to do a more accurate comparison, I loaded up another model in Cura and exported the gcode so I could run it through Octoprint, which is my typical setup.

To my surprise, out comes the Ultimaker bot again :slight_smile:

Looking at Cura, most views display the updated model correctly, but if I look at the “layers” view, I see the robot again. The craziest part is that if I quick Cura and start over, it’s the same thing; I can’t get rid of mr robot dude.

I filed an issue on Github (https://github.com/daid/Cura/issues/595), but I thought I’d check here to see if anyone has any work-arounds.

try setting cura to open your .stl files and then double click the stl and it should be the sole file open in cura. also make sure both the print and cura setting window are closed. to set the stl file open right click the stl select open with… and right click the cura application icon go to properties and copy the path and paste it into the open with window path. set it to always use this and that should fix the problem.

Hmm… when I open the .stl directly this way (right-click -> open on the file) it loads, but the save icon is disabled, and if I try to save the gcode I get an error “Failed to save” at the bottom of the view window.

FWIW this is on Mac OSX 10.9.

Feels like this is related to the “always generating gcode” feature, I wonder if I can turn that off…

Now no matter how I open it, I can’t save anything, and it doesn’t appear to actually be generating gcode anymore. I may try again on Linux, or maybe just go back to Slic3r until the next version comes out.

try an uninstall then reboot then a re-install with a fresh download