Hatch bug?

[jgrande26]

Is anyone else running 2018 experiencing problems with the Hatch command? If I try to create a new hatch, CAD crashes after I pick the first point. If I try to edit a hatch, CAD crashes as soon as I select the hatch pattern. My coworker is also experiencing the same thing. We both get a fatal error message and CAD shuts down completely.

[Tom Beauford]

I've had the same issue.
Don't know if it's related, but I've had other selecting issues as well: https://forums.autodesk.com/t5/autocad-civil-3d-forum/civil-3d-crash-when-snaping-3d-polyline/m-p/7546934

[jpcadconsulting347236]

I am having that issue. AutoCAD Architecture 2018

For me its the Properties Palette.

If the palette is open and I select a hatch. Fatal Error. If the palette is closed, everything is fine.
If I select the hatch (with palette closed) and issue the LIST command, Fatal Error.

Autodesk knows about it... I think:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/AutoCAD-freezes-when-hatch-object-selected.html

If I find anything, I'll post.

[jpcadconsulting347236]

OK I resolved this issue at my client's office today. When I reset the profile to the autocad defaults (all local paths) it worked fine. As soon as I loaded our profile (with server based paths) it started happening again, like clockwork.

So, I started with the default profile and added out paths one by one. Then I added each line of our acad.lsp and then acaddoc.lsp, one by one, with a restart and test after each addition.

When I added the lines that load our named page setups on file open, it started happening.


; IMPORTS NAMED PAGE SETUPS

(setvar "EXPERT" 5)
(command "._-PSETUPIN" "Z:/AutoCAD 2018/Drawings/Pagesetups.dwg" "*")
(command "._-PSETUPIN" "Z:/AutoCAD 2018/Drawings/Metric Pagesetups.dwg" "*")
(setvar "expert" 0)

So, it had to be something about either the drawings the page setups are stored in, or the page setups themselves... right?

Well AUDIT and RECOVER turned up nothing - the drawings reported clean
If I imported the page setups manually, I could hatch all day with the properties palette open.
And in fact those files are simply copies of the ones in our 2016 folder, and they work perfectly in 2016.

Maddening.

Anyway what worked for me was to create 2 new drawing files from acad.dwt, manually import the page setups from the "bad" files, and then save over "Pagesetusp.dwg" and "METRIC Pagesetusp.dwg" respectively.

Who knows what the real issue was but the problem is gone... office wide... just like that.

It's such a unique, oddball resolution, I can't imagine it's the same issue for you. But maybe it's something to go on.

Good luck.

[Tom Beauford]

To clean page setups from any existing drawings that have the bug try:
; https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/purge-all-page-setup-names/m-p/830018#M55676
(defun DelPageSetup ( Name / Cfgs) ; by Jason Piercey - Autodesk Discussion Forum Moderator
(setq Cfgs
(vla-get-plotconfigurations
(vla-get-activedocument
(vlax-get-acad-object)
)
)
)

(cond
((vl-string-search "*" Name)
(vlax-for x Cfgs
(if (wcmatch (vla-get-name x) Name)
(vla-delete x)
)
)
)

(T
(vl-catch-all-apply
'(lambda () (vla-delete (vla-item Cfgs Name)))
)
)
)
(princ)
)

;; (DelPageSetup "*") to run or
;; (or DelPageSetup (load "DelPageSetup.lsp"))(DelPageSetup "*") to load if needed then run
I use Lee Mac's Steal from Drawing (http://www.lee-mac.com/steal.html) lisp to import a list of Page Setups, this macro imports the two we use for 11"×17" plotting:
(or C:Steal (load "StealV1-8.lsp"))(Steal (strcat (vl-filename-directory (getenv "QnewTemplate")) (chr 92) "AutoCAD Template" (chr 92) "Templates.dwt") (list (list "Page Setups" (list "11×17" "11×17 PDF")))) .regen
Worth a try if the problem returns. In my top 5 list of routines I've ever downloaded (out of hundreds) as it can be used to bring in several times more than Design Center and does a much better job on things like Layouts.

[jpcadconsulting347236]

Lee Mac is the cat's pajama's. Don't know where I be without his help. ;-)

[jpcadconsulting347236]

I have found that (at least in my case) this issue was with the Civil3D object enabler (and not the tool palette as stated before - although that did exacerbate the issue).

If I uninstall the Civil3D OE hatching works fine, reinstall, issue returns.

Easy test and well worth trying.