AutoCAD hatch pattern sometimes becomes non-associative when using Match Properties

[jordanlatta]

I prefer to use associative hatch patterns when possible when drawing building elevations, so that if window locations, etc. move in the future then the hatch automatically stretches and I don't have to redraw all the hatches.

However, I'm running into a problem where using the matchproperties command, it makes the target hatch non-associative. Is the source hatch corrupt or something?

This is an intermittent problem that mostly happens with source hatches that I made a few months ago.

If I make a brand new hatch and then use it as a source, it's more likely to work.

Sometimes saving the file and opening it again makes the problem go away, but only with small files.

I'm using AutoCAD 2023.

[pendean]

@jordanlatta Thank you for the DWG file and videos: I am unable to replicate the issue as shown in your video in AutoCAD 2023.1.2 in WIn10Pro here no matter how many variations I try. I even closed and restarted R2023 twice to see if I can jumpstart the problem, also tried it in MODEL space and inside a viewport in a layout.

How "intermittent" is this?

[jordanlatta]

Thanks for looking into this.

I only started noticing it more often working in one specific file (attached).

I was able to replicate the problem in those videos by copying the problematic objects into a separate file (the one i attached in the initial post) but here is the original file.

It seems like it was fixed once i saved the file and re-opened it.

So when you opened the file it was probably fixed by then as well.

I'll try copying everything into a brand new file and see if that fixes it, but for now here is the problematic file.

[jordanlatta · Accepted solution]

Ok, so I tried copy-pasting everything into a clean file, but it breaks the associativity of ALL hatches in the file when I do that.... No bueno.

But I tried making a new associative hatch with the exact same properties as the problematic source hatch, and then save the file and reopen it. After that, it seems that all the problematic hatches of that particular type are fixed somehow. I guess I'll use this as my solution for now.

However, please note: this problem can still be replicated in the file attached to Message 3 of this thread.

[pendean]

@jordanlatta Message3's DWG is nothing like your earlier block and has so many things going on, I don't have the time to dissect and very inconsistent with your earlier statements

FWIW COPY/PASTE is rarely a good idea: you found the better approach.

[jordanlatta]

Agreed, that file is very busy... hence why I tried to dumb it down in the initial post, but it appears that doing that made it so that the problem could not be replicated.

The relevant area of _MGP_ELEV.dwg is in view upon first opening the file, and I think the problem could be replicated by another user by following the MTEXT directions provided in the file (if anyone else encounters this in the future and wants to troubleshoot).

 

Anyway, its' probably not worth putting any more effort into this, but I super appreciate your time!

Thanks

-JL