- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
AutoCAD 2022: “Separate Hatches” tool fails,
AutoCAD 2022: “Separate Hatches” tool fails,
In the screenshot below (attached video), the entire drawing is selected (ctrl + A) and then the hatches are filtered with the “quick select” tool that selects all the hatches then the “separate hatches” is clicked with no response and never grayed out
What could be the issue here?
The dwg is attached
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
What is it you are trying to do? I think you misunderstand what that feature does. It is used when creating hatches not for modifying hatches.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
you also have hatches on top (or underneath) other hatches, and this tool isn't going to fix those either.
BTW, isn't this your 3rd-4th-5th hatches-only post in the last month? I'm curious honestly, not much else.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Sure. The “separate hatches” option is used mainly for already existing hatches as per the screenshot below. It gets the hatches separate and then it is grayed out.
In the dwg I attached in the first post, it fails to do so
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Sorry, but the ‘separate hatches’ is not failing. Your uploaded image indicates 46 hatch entities and that means you have separate entities.
On the other hand, if the Properties Palette showed only ‘1’ hatch with just one center grip, then yes, you could separate it into 46 hatches using the Separate Hatches tool.
If the hatch is behaving as a single entity and not as 46 individual entities, then I suspect another issue is present.
Chicagolooper
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
These distant hatches are selected as hatches as per the screenshot below. How come they are “hatches” but don’t respect the rules of hatches when it comes to “separate hatches”?
How these distant hatches can be identified in a much more complex drawings?
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
@JamaL9722060 wrote:
These distant hatches are selected as hatches as per the screenshot below. How come they are “hatches” but don’t respect the rules of hatches when it comes to “separate hatches”?
>> If you select all, then deselect the main group, you'll see that there is one hatch and one line. Both are somehow DAMAGED. Neither of these objects is selectable by regular window selection soo... Some properties are good (as a number of boundaries, which you can clearly see that there are 3 boundaries, 3 rectangles, therefore the SEPARATE option is available. But, if you run the command itself, it does not do anything - the hatch is damaged.
How these distant hatches can be identified in a much more complex drawings?
>> I have identified it visually. Looked and saw that hatch is basically just a boundary, no real area is hatched. There isn't ONE PARTICULAR METHOD on how to identify broken hatches. Hatch could be damaged in a hundred different ways. Some properties could be good, some other bad. I guess this ability to find the issue only comes with experience.
Lastly, better to try to prevent these issues. Hatching by a picked-point in large civil files isn't reliable enough, boundaries are ofter wrongly identified, which could lead to similar issues. And since it's not easily recognizable, it could cause errors when you count the bill of materials. Better create boundaries manually using polylines. And always double-check that boundaries.
Good luck.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
I’m really sorry guys but this is how I receive the drawings that I’m supposed to convert to GIS. It will be shocking to have features in GIS that have no equivalency in AutoCAD. The more the drawing is complex, the more the visual identification is not efficient.
I observed that the hatches that are candidate to have potential issues are those with “none sperate” hatches. They get fixed with the “separate hatches” command that is assumed to get grayed out. In this particular case, the “separate hatches” command is not grayed out. Why?
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
(defun c:HatchesWithLoops ( / s e i)
(if (setq s (ssget "_A" (list '(0 . "HATCH") (cons 410 (getvar 'ctab)))))
(repeat (setq i (sslength s))
(setq e (ssname s (setq i (1- i))))
(if (= 1 (getpropertyvalue e "NumberOfLoops"))
(ssdel e s))))
(if (> (sslength s) 0) (sssetfirst nil s))
(if s (princ (strcat "\nNumber of hatches with multiple loops: " (itoa (sslength s)))))
(princ)
)
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Thank you for the help.
The lisp file is able to identify the hatches with loops.
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
This is another case where the “separate hatches” option fails
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
"HatchesWithLoops" and "HatchsWithMultipleAreas" are different things!
So the Lisp works and doesn't fail, but it isn't exactely what you asked for.
It is just a helper for you - It is "better than nothing" and helps (you) a lot.
1. Most important: You uploaded the wrong file or your screenshot is not from this file state.
2. Because of my explaination, the Tool should select one hatch _(with only one area, but with more than one loop)
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Sure CADffm.
What I meant here is that the built in “sperate hatches” command fails and never grayed out.
The lisp file does identify the none sperate hatch but unfortunately the “sperate hatches” command fails to get grayed out
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
How do you expect to put out a quality product with such bad .dwgs? You could actually be compounding the errors that are in the files that you are receiving.
You should be putting your efforts into getting quality content from the source.
Rob
Drafting is a breeze and Revit doesn't always work the way you think it should.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
The issue in the last dwg I attached has nothing to do with the quality.
It appears that AutoCAD, by design, fails to get the “sperate hatch” command grayed out as the hatch has a hole (donut hatch). The “sperate hatch” command never grayed out in this case!
What do you think?
Jamal Numan
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Yes,
the native commands working the same way as the Lispfunction:
They checking the number of Loops and not the number of hatch-areas
1 Loop: Separate-option not offered
2 or more Loops: Separate-option offering
In a End-User forum: End of the story
Sebastian