benjamins94

There, finally remembered to record: https://youtu.be/-A9OF2HBZJU As I have stated before: it does not matter, any variable cura.log

I think we have a misunderstanding 1.) Cura tells me "unable to slice" 2.) I move the model, and ctrl+Z to move it back to where it was, and click "slice" button again 3.) Cura slices without the error Or 1.) Cura tells me "unable to slice" 2.) I pick a random variable, let's say "wall line count", i change it from 3 to 2 and back to 3 again, and click the "slice" button again 3.) Cura slices without the error The slice button becomes greyed out, so I change the variable (again, ANY of them, doesn't matter) or move the model so it becomes clickable again I wish I could tell you which error got missed, but the only thing I get is "unable to slice" I uploaded the .log files a few minutes after it happened Will do a screen record next time...

/w Are you insulting yourself by quoting yourself and writing /w? I already said it doesn't matter, it's just so it lets me click the "slice" button again I do not understand, does changing a variable and undoing the change move the model to a suitable location to print? Anyway, my main point (check the thread title) was that the "unable to slice" error might be a little to vague and it could show some useful information instead, maybe the cause of the error?

Happened for the first time since upgrading to 4.12 cura.log cura.log.1.log

Any variable, just so it lets me (or itself?) try again Moving a model and then undoing it by ctrl+Z also does the trick Also, /w?

Will the error get more detailed if I post those? /s Will do when it pops up next time

Has anyone on the developing team ever thought that the "Unable to slice" error might be a little too vague? Pretty often I get that error, change one variable so it allows me to slice again, then change the variable back to what it was in the first place, and the error is gone Might that be the reason? "unable to slice" for no reason whatsoever, so that's why there's no more info in it? Edit: Video of the issue: https://youtu.be/-A9OF2HBZJU