XREF DEMO WALLS AND DOORS NOT REPRESENTING ASSIGNED LINETYPES

[jrb63]

I have a base floor plan with a demolition layer with hidden2 line type and color yellow assigned to it. We have wall and door styles with components located on layer 0 and line types and colors set to 'by layer'. In the base plan, everything represents properly with the demo object having the hidden2 line type. see screenshot
xref screen shot.jpg
When I xref the base plan, the wall and doors on the demo layer no longer represent with dashed line type. and the walls are white. See second screenshot. Annotation leaders point to items on demolition layer. Ltscale and psltscale are both set to (1) in both files. Both files are using the same display representations (standard). Visretain is turned on. I detached and reattached xref file to no effect. I recreated the file from scratch. The problem exists in any file I create, and attach, or overlay the xref. Another user can set up a drawing and xref the same file, and it all works fine. What Autocad setting/command am I missing?

[dkoch]

Have you installed all of the updates for both AutoCAD 2018 (2018.1.2) and AutoCAD Architecture 2018 (2018.0.3)? There was an issue with the display of AEC objects in external references:
where components were to be ByBlock or Layer 0/ByLayer so that they should inherit the properties from the parent object's properties, they inherited the properties of the external reference, instead. This was fixed in one of the updates.

[jrb63]

I have our sytem manager looking into that. Thanks for the suggestion. I will get back to you.

[tedg]

Just another thought, assuming this is a base drawing and a sheet with the base xreffed into it:

I know you mentioned visretain is "on" (visretain = 1), but (while in the sheet drawing) have you tried turning visretain "off" (visretain = 0) and RELOADING the xref?
This would reset all layer overrides to how they appear in the saved base drawing.

Then remember to set visretain back "on" (visretain = 1)

Hope that helps

[jrb63]

I installed the update 2018.0.3 and it resolved the issue. Thanks again!