Cura refuses to slice when print size reaches limits.

[Uncle_Victor 0]

I have the "problem" since I have an UM3.

Even if the size of the print is within the limits Cura does not slice - print too large message.

I found a lousy trick to solve it, but don't understand why.

Yesterday I wanted to print an object with the size of 190x190mm - no slicing...

I installed an other printer (UM2+) and the slicing worked.

Then switched back to UM3 and it worked also.

But from the moment you reload the file you are out of business again.

No limits were pushed, as the gcode file generated that way printed without any problems

[DidierKlein 729]

Could it be because of the brim or skirt?

[Uncle_Victor 0]

I am aware of that.

btw I am happy I can turn off the skirt in 2.3.1 - in previous versions I had to switch to brim to turn it off.

Can I somewhere load the file so you can check it?

[Uncle_Victor 0]

Have to print something that's close to the printer limits again.

This time I use cura 2.5 (tried 2.6.0 but this version is so buggy I had to go back to 2.5)

In the mean time 2.6.1 is out, a few days after the release of 2.6.0 - as an "old" programmer, having a new version within a week of the previous release is a clear sign the previous one is crappy - I will try it soon...

Back to the limits problem.

Nothing has changed in the recent releases of cura - problem is stil there.

Fortunately my old trick of switching to another printer and back still works in 2.5

(did not in 2.6.0)

I have send my stl file to a friend having also an UM3 (bought it within days after I did some printwork for him) who sliced it without any problems with Simlyfy3D

By the way this guy used cura for less then a week and switched then to Simplyfy3D and does not intend ever to go back to cura. 8)

I am still willing to upload a "problem" stl file to support if someone tells me how.

[nallath 1,120]

This time I use cura 2.5 (tried 2.6.0 but this version is so buggy I had to go back to 2.5)

Issues like what? If you don't report them, we can't fix them.

In the mean time 2.6.1 is out, a few days after the release of 2.6.0 - as an "old" programmer, having a new version within a week of the previous release is a clear sign the previous one is crappy - I will try it soon...

Or it's a sign that the new materials needed to be bundled on the right date The 2.6.1 release is not because there were blocking issues.

I am still willing to upload a "problem" stl file to support if someone tells me how.

Upload it to dropbox or any other model sharing service.