"Object Too Large" Error (V 2.9.3 Bug?)
I have a couple models that I printed successfully several times in July of 2022. According to GitHub, I was probably using Version 2.4.2 back then. I need to print more, and loaded the old .stl files just fine. However, when I slice them in 2.9.3, I get an "OBJECT TOO LARGE" error. It's not clear if it is running out of processing space (unlikely), or if it's suddenly decided my printed bed has shrunk.
My printer is a MakerGear M2E, which has a bed 200 mm by 250 mm. The model is only ~ 206 mm by 94 wide. Even with a skirt & supports outside the model, there plenty of room on the printer bed. It's not a very complex model:
I searched the forum, and there is no mention of this error message in any topic titles. I just dug on GitHub, and apparently this IS a bug, and has been around since at least 2.9.1: https://github.com/prusa3d/PrusaSlicer/issues/14585
The "Fix" is to turn off "sequential printing". I only have the one model, so I don't need that. If I turn that off, it's perfectly happy...
I figured I'd post this on the forum in cases someone else runs into this.
RE: "Object Too Large" Error (V 2.9.3 Bug?)
This is not a bug in the software but in the user who activated "sequential printing" for this part. 🙂
Just think what would happen if you had another part like this on the bed: the first part would probably interfere with the movement of the print head on the second instance.
RE: "Object Too Large" Error (V 2.9.3 Bug?)
If you only have one object, it shouldn't care, and previous versions were fine. I didn't "activate" sequential printing, I left it alone because it shouldn't matter. I don't have time to meticulously go through the hundreds of options for every print job turning off features that aren't required for the specific model at hand. For example, when I load a standard profile I've used on other jobs, I don't bother to turn off supports on models that don't need them. Same with bridging settings. Sorry if I'm a bit testy, but this "bug" cost me well over an hour of wasted time last night...
Fortunately, I found the fix before I'd wasted several MORE hours reverting back to Version 2.4.2.