Unable to hatch boundary

[Fire_col]

This is annoying me I'm trying to use the concrete hatch within a bounday of 50mmx365mm (2"x14" ish, for you imperialists out there :wink:).

Now all my other hatches have worked on my drawing but this particualr hatch just doesn't want to play ball, and I really can't figure out why.

I've tried turning off associative hatching, I've played with the hatching scale but it keeps coming up with the same message.

The boundary incidently is a closed polyline

 

Any Ideas?

[Dana W]

Is it possible you have another object beneath or very near the boundry you want to use, that is mucking things up?

 

I have, at times, had to resort to tracing the boundry with a polyline, then moving it way off to the side someplace, hatching it, then moving the hatch back into the spot I wanted it in.

 

Sometimes AutoCAD seems unwilling to cooperate with hatching in some parts of my drawings that are fairly dense.

[Fire_col]

Nope it's all by its self.

[Fire_col]

Right got it, aparently it only works properly with a scale of 1 or less. weird considering my other hatches needed scale of 15 to look correct.

I hate CAD sometimes

[Dana W]

Right got it, aparently it only works properly with a scale of 1 or less. weird considering my other hatches needed scale of 15 to look correct.

I hate CAD sometimes

 

Yeah, the concrete was aparently created at actual size. Agregate is itsy bitsy.:wink: What I don't get is why it told you something is wrong. Mine just splops it in there at a huge scale and my hatch consists of the SPACE between the hatch image lines and maybe one bit of gravel.

 

I've had nasty issues trying to use ARSAND too. Heaven forbid the hatch scale is too small. It comes out so dense my graphics card catches fire if I inadvertantly roll the crosshair over it and it goes into perpetual highlight for select.

[Fire_col]

Oh I hate it when it does that! I don't know why CAD told me there was something wrong either, sometimes I wonder if CAD even knows why it does what it does.

[dbroada]

stop moaning. Try and find a copy of release 10 and hatch something.

[KJB]

When complex hatches give me a problem, I copy the area to be hatched to 0,0. Hatch the area and then move the hatch to its correct location. This procedure always resolved my problem with certain hatches.

[LearningQuickly]

The GRAVEL hatch does this to me all the time. Just CHSPACE on your boundary to to bring it into paperspace then hatch it. For some reason the complex hatches are quite glitchy in Model space but work fine in Layout. Once your done, just CHSPACE back to Model space.

[alanjt]

Right got it, aparently it only works properly with a scale of 1 or less. weird considering my other hatches needed scale of 15 to look correct.

I hate CAD sometimes

Strange, it should alert you if there is an issue with the hatch density.

 

stop moaning. Try and find a copy of release 10 and hatch something.

or older versions of MicroStation.

[KJB]

LearningQuickly has the same basic resolution as me. The problem with complex hatches are large coordinates.

[Dana W]

Strange, it should alert you if there is an issue with the hatch density.

 

 

or older versions of MicroStation.

 

It's not always dense the way autocad sees it. It depends on how much area you are hatching, I think.

 

I was creating a Site Vicinity Map for the upper right corner of a survey, so I just copied the outer property boundries to another place in modelspace, and hatched it. I had forgotten to change the hatch to something less dense, so I ended up with 27 acres of ARSAND at 1.00. It was ok as long as I was zoomed in where a unit (1.00') was about 1/10 of the screen or bigger but zoomed out it was just a blob of white. Trying to select it for erasing nearly brought my computer to tears. The highlight effect scrolled in like a curtain.

[alanjt]

It's not always dense the way autocad sees it. It depends on how much area you are hatching, I think.

 

I was creating a Site Vicinity Map for the upper right corner of a survey, so I just copied the outer property boundries to another place in modelspace, and hatched it. I had forgotten to change the hatch to something less dense, so I ended up with 27 acres of ARSAND at 1.00. It was ok as long as I was zoomed in where a unit (1.00') was about 1/10 of the screen or bigger but zoomed out it was just a blob of white. Trying to select it for erasing nearly brought my computer to tears. The highlight effect scrolled in like a curtain.

Ugh, Highlight. While waiting on a new machine at work, I had to just turn it off.