Coordinate outside allowed range

[guestisp]

Version

6df17e1

Operating system type + version

Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco

Behavior

Trying to slice the following (only the dog, not the box):
https://www.thingiverse.com/thing:220609
we get:

ASSERT INFO:
Slic3r has encountered an error
Coordinate outside allowed range

the same model is sliced properly with the upstream slic3r, i've printed it multiple times.

[uniacke1]

I'm observing this too, local build of sources on linux.

[uniacke1]

This problem is caused by the "Rectilinear (filled)" solid infill pattern. Changing it, or altering the "anchor solid infill" percentages to (e.g.) 1mm/1mm makes the bug go away.

[supermerill]

can't reproduce with the last version.
If you can, please link me the project file (.3mf)

[uniacke1]

Sure, here you go.

FilamentPM-silver.3mf.gz

[supermerill]

Seems like I have fixed this in my dev build.

[uniacke1]

Superb, I'll pull and recompile to give it a sniff test. Thanks!

[uniacke1]

This does indeed appear to have been fixed!

[VanessaE]

This is not fixed, or perhaps I should say it has resurfaced. I'm at commit a4699e7, newly built just before this comment. Try this project:

Benchy_Bernie_1.5x.3mf.zip

The model slices fine at 100% (normal) size, but scale it up some and it throws "Coordinate outside allowed range" as per this issue's title, after spending some time slicing.

Setting the anchors to 0/0 to disable them did not help, however, setting the solid infill to "rectilinear" (not "filled") per your suggestion does work.

[jhoblitt]

I'm seeing this as well and I can't seem to escape it by changing the infill type(s).

[jhoblitt]

The only way I can resolve the error is by scaling the part down to 25% scale. Anything much larger then that fails. This is really odd as previous versions of the part were slicing OK (STLs generated by f360). I have tried running an STL repair and reimporting the part from a OBJ with no change in behavior. This is happening with 2.3.55.2.

[jhoblitt]

@supermerill This is still happening with the nightly build from ~24 days ago. PrusaSlicer 2.3.0 is able to slice the files. I started trying older versions and it works with SS 2.3.55.0 but fails with the same error under 2.3.55.1.

[tecnopolis-ve]

With superslicer 2.3.55.5 does ocurr the same.

I've figured out how to "alleviate" this issue by changing Anchor solid infill by X mm from rectilinear (filled) to rectilinear.

I've tried with a 3dbenchy (normal size does work, scaling over 200% fails)

I think that this issue must be reopened.

[TimbreDesign]

I have also now experienced this with 2.3.55.

I have been oddly able to get rid of the error by flipping the print over (thus requiring support) and lowering the layer height.

Changing the fill or scaling the print down did not solve for this.

Here are the files (.obj, with it working, and one with the errors present):
filament_tube_fix_bolt_Print_1_ERROR.zip

[supermerill]

can't reproduce in 2.3.56.1

[Majestry]

I can reproduce this issue on 2 separate models.
Version 2.3.56.6, MacOs BigSur 11.4 (M1 CPU)
Bed size is set to 235x235x250, model size is 85x134x100. The object was positioned automatically, I didn't moved it on the bed.
If i set infill to 0 - model is sliced, otherwise i got error Coordinate outside allowed range
Github do not allow me to download the m3f file (return the 422 with size is not provided, which is weird), so here is the direct link to 3mf file: https://drive.google.com/file/d/18GI9keV177xMhC34SFBrUKOABO-hvkMV/view?usp=sharing

[supermerill]

@Majestry
I loaded your .3mf and it slices perfectly on a fresh 2.3.56.6
can you take a screenshot of what's going on after you load & slice it?

[Majestry]

@supermerill sure, here is the link to screen record when error occures. https://www.youtube.com/watch?v=WMaPeugcHRo
Also, here i loaded the same model and set infill to 0 - and it was sliced without error. https://youtu.be/oSMP38DvXp8

UPDATE: when recorded the screen, i didn't capture the status bar - the error appeared when it slicing was in state "Preparing infill". And in attached file - how the layers view looks like after the error appeared

[jurisv]

Does this also fix the same issue in MacOS ?

[Belstrekkie]

Both version 2.3.57.4 and 2.3.57.5 are giving me the coordinate outside allowed range in the Windows version, whereas I haven't had any issues in 2.3.57.3 and earlier. In the image the sliced object is version .3 and the error .4. The position and settings are exactly the same.

[alfrix]

i have also found this bug in windows 2.3.57.4 and 2.3.57.5, but not on 2.3.57.3 (same as Belstrekkie)

adding a cube and moving it past 250 mm produces the error

Aspecto-Caja.zip

[Maximilian-Staab]

I'm getting the same error on 2.3.57.5, but only if "brim" is enabled:

[Maximilian-Staab]

The nightly build fixed the issue for me, thanks!

[Dreistein75]

Sorry, not good with GitHub. I have the newest SuperSlicer (MacOS on ARM) and the following STL from PrusaPrinters gives the Error with the "Coordinate outside allowed range". So guess this is still not fixed entirely.

white-christmas.stl.zip

[supermerill]

@Dreistein75
can't reproduce with your stl.
Please post your project file.

[Dreistein75]

@supermerill
I just re-tried and the error is still there. I saved the project as 3mf and I will attach it here. It is SuperSlicer 2.3.57.7 for ARM MacOS

SuperSlicerProblem.3mf.zip

[INeDiA]

@supermerill I just re-tried and the error is still there. I saved the project as 3mf and I will attach it here. It is SuperSlicer 2.3.57.7 for ARM MacOS

SuperSlicerProblem.3mf.zip

same here; switched back to the regular release (no ARM) and it works without any issue

[supermerill]

I think something is creating Nan somewhere when compiled with arm. Next to impossible to fix without a mac mini on hand. Problem is, they are still kind of expensive.

[yonkiman]

I'm also getting a"Coordinate outside allowed range" error when I try to move the object towards the upper right of the build plate. If I pull it in closer to the center it slices fine. I've attached the project file
Coordinate outside allowed range SS 2.3.57.5, Windows 10.zip
.

[supermerill]

@yonkiman on the 2.3.57.5 yes, but it doesn't happen on the latest release (tested on 2.3.57.8)

[yonkiman]

Apologies - should have made sure I was on the latest version!

[elcojacobs]

I have this issue with the latest nightly with this stl.
4028-jet-fan-intake.zip

It shows correctly in sliced preview, but cannot generate gcode.

[supermerill]

@elcojacobs no problem for me.
your project?

[elcojacobs]

This is very strange, I cannot reproduce the error now. It happened on multiple models, even after restart of the appimage.
If it ever happens again, I'll get you a 3mf.

[elcojacobs]

Ah, got it!

I saved my filament profile with 2.4.58.2, which disabled wipe inside at start/end.

Re-enabled them to reproduce the error. There is also a bug that it shows the wrong header for wipe inside at end:

susi_error.zip

Here is a 3mf with the error.

[supermerill]

can slice and gcode it with latest nightly

[elcojacobs]

Seems fixed in yesterdays nightly. Could you reproduce it in the 'better fixes' nightly?
The bug with 2 times the same checkbox label is still there.