Slicing not working

[alexanderswo 1]

When I start Cura (14.07) and slice a model for the first time it works fine. When I change a parameter or move/multiply the model, the slicing does not start again.

- is there a way to restart slicing? (so far only restarting cura helps)

 

[gr5 1,235]

Is this a Mac? There used to be issues like this on the Mac. This sounds extremely annoying and I haven't heard anyone else have this problem in a while but you can clear the platform, get all the settings perfect and then load the model at the last minute if you want to slice only once.

But you shouldn't have to do this. Some things that have messed up cura slicing in the past:

anti-virus software

things plugged into USB

SD cards or similar removable drives.

millions of triangles to slice. Or billions.

Does it do this on all models or just a particular model? Try a simple cube.

 

[alexanderswo 1]

Sorry, haven't been printing for a while. - No, its not a mac. I haven't had those problems in earlier versions. Right now the problem is that I can't rotate the model any more. Cura is starting to slice instantly after loading the model. After rotating, the model is still not beeing rescliced and the old toolpath is shown in layers view.

- nothing except the printer is connected

- its a very simple model, also with other models the same thing happens

- the virus software is called "Managed Antivirus" and I can't simply deactivate it at work

 

[Daid 289]

Cura generates an output.txt in c:program files (x86)Cura_14.07 what does that say? Might be an error in there that can help in finding the cause of this issue.

 

[alexanderswo 1]

Well, I found that file but i'am not qulified to make any conclusions. How can I upload it or what part would you be interested in to see?

 

[Daid 289]

Just copy the contents here, it's magic for most, but makes perfect sense to me :-)

 

[alexanderswo 1]

The file has several thousand lines, thought that wouldn't be helpful. -Anyway, I found that the last line said this:

ValueError: invalid literal for float(): 2,86

so I intuitivley checked the value put in for filament diameter and saw it was a comma instead of a point, changed it and it worked fine again.

-For me the problem is solved, but programming wise it might be good to put in more fool-safety :-)

Thanks for your support!