Ok .. well what is it that you are looking for? I am at a loss ... you wanted the hatch pattern fixed .. which I did, but then you edited it to something else ..
Aaaahhh sorry if I upset you.
I do (did) have two problems. Creating the hatch pattern and the crashing of the ACAD when using said pattern.
In my 10 years of using ACAD, I never created a hatch pattern. My first creation was kind like doing emergency brain surgery with a dull chain saw and 15lb sledge. Very messy as you pointed out. You fixed that for me by both fixed the pattern itself and by explaining it to me. I got to thinking and deciding that this pattern will be at all kinds of angles so I deleted the 90 component to make it simpler.
The crashing part is what really was upsetting me and we are against a deadline with a lot of work so we have the engines screaming over here and the Architect wants things shown exactly as they are. So my patience yesterday was at it limits and if I said anything rash. Sorry it was not meant that way.
Lets start from the beginning ...
You must name the hatch file the EXACT name as the name of the hatch pattern defined in the file.
Learn this the hard way yesterday.
You cannot have more than 1 definition of a hatch pattern in a custom hatch.
I don’t, if I understand you correctly. One pattern per file. We cannot have it like the ACAD.PAT file.
(Which kinds of answers a question in the back of my head that we cannot have a single company hatch file up on the server so all my users can pull from.) The custom hatch MUST be in the path specified by the support path, otherwise you will not be able to use it.
It is in the same folder as the installed PAT files.
Now, you cannot rotate certain hatch patterns using the properties dialog if the hatch pattern name is over a certain number of characters long.
So, you should shorten the length of the pattern name if you want to modify it through the properties dialog.
It does look kind of long, now that you mention it.
Thanks again and my apologies.