Annotative Wall Hatches Not Displaying in XRefs (ACA 2020)

Annotative Wall Hatches Not Displaying in XRefs (ACA 2020)

chadclary
Contributor Contributor
775 Views
4 Replies
Message 1 of 5

Annotative Wall Hatches Not Displaying in XRefs (ACA 2020)

chadclary
Contributor
Contributor

I have a couple people in the office having an issue with Annotative Wall Hatches not displaying when the walls are in an xref and I'm stumped.  The only way the hatches appear is if they are not annotative, and a regular hatch pattern that is annotative works correctly.

For testing I opened the file that is being linked (2-BR), did a save-as (test) so the display config settings are the same, and then linked in the original version. As-is, no hatch patterns.  If I edit the xref, then modify a wall type and make the hatching not annotative everything displays as intended.  This all worked correctly in 2019 - so I would assume there is some setting that I'm completely overlooking here...

 

Cheers

0 Likes
776 Views
4 Replies
Replies (4)
Message 2 of 5

David_W_Koch
Mentor
Mentor

I get the same results you get.  A setting to make it work in 2020 like it does in 2019 is not coming to mind.  This may be a 2020 bug, but I would be happy for someone else to disprove that theory by letting us both know what the mystery setting that changed in the 2020 template files is.


David Koch
AutoCAD Architecture and Revit User
Blog | LinkedIn
EESignature

Message 3 of 5

chadclary
Contributor
Contributor

weird.  Thanks for confirming 🍻

0 Likes
Message 4 of 5

dbroad
Mentor
Mentor

There are several effective channels for reporting bugs that I have used in the past:

  1. https://www.autodesk.com/company/contact-us/product-feedback
  2. Filing a support case under https://manage.autodesk.com/home/

Good luck.  Be sure to provide some files to test and specific instructions for how to replicate the problem.  I haven't started using 2020 yet because it requires Windows 10.

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 5 of 5

chadclary
Contributor
Contributor

I talked with support - here is their reply:

 


This is a known issue and is being investigated by the development team to determine whether a fix can be provided in a future release or update. 

Currently the only way to avoid this behavior is to make the hatch non-annotative, which I understand you already are aware of looking the description.