Boundary command

[SLW210]

20 hours ago, PGia said:

I exploded the polylines into lines. I also reduced the lineweight to 0, but in both cases the result remains the same.
A colleague who still has an old PC with Autodesk Map 5 (= AutoCAD 2002) also confirmed that the same error occurs.
If I’m not mistaken, AutoCAD 2002 is basically the same as AutoCAD 2000, so @SLW210’s statement that the "boundary" command works correctly in that version intrigues me.

 

Yes, 2000i fails when zoomed out as well.

[SLW210]

The only "solution" besides zooming in I could determine, was to copy the polylines in place and use region on them, which seems to be correct in the example drawing.

 

That should be able to be done with a LISP?

Boundary.dwg

[mhupp]

Was reading up on this too. apparently AutoCAD boundary command doesn't have a tolerance setting but BricsCAD does. That is why people opt to use hatching and then you can create the boundary from the hatch. and then delete the hatch. 

 

I'm confused since their isn't a gap/vertex at that location. 

[SLW210]

It's supposed to use the HPGAPTOL as far as I know.

 

This has been an issue for sometime, now that I looked back into from a few years ago, this problem also occurs with Hatch command. I just tried Boundary and Hatch on a closed polyline object at Zoom Extents and got ...

Quote

 

Hatch - Boundary Definition Error

A closed boundary could not be determined.

There might be gaps between the boundary objects, or the boundary objects might be outside of the display area.

Try one or more of the following:

•  Zoom out until all boundaries are visible. Then specify a new pick point.

•  Cancel the command and modify the objects in the boundary to close the gaps.

•  Confirm that the XY plane of the UCS is parallel to the plane of the boundary objects.

•  Specify a larger value for the hatch scale or use the Solid hatch pattern.

•  If precision is not needed, increase the Gap Tolerance setting.

 

 

And despite the first instruction, Zooming In resolved the issue.

 

I normally resolve this with Hatch by using Select Object, maybe Hatch, Select Object, delete the Hatch and keep the Boundary could work for the OP.

 

@lastknownuser's post brought it back to my memory. There is a thread around from a while back on this issue and needing to use Select Object option for Hatch.