I'm working with architectural CAD files that have multiple floor plans stacked on top of each other, which are controlled by layer states. If I LINK the file into Revit, it will automatically apply a VG filter based upon the last saved state of the drawing, (which matches whatever AC Layer State it was saved as). The autocad file has 3-4 layer states per floor, so multiple floor buildings are even worse. Is there a way to automatically create separate VG filters by importing the layer states from AutoCAD? Manually making the VG states for each view would be a huge time constraint.
If I try to unload and reload the dwg file, it will either revert to the previous version, or just display all the lines as "ON".
Is importuning a new COPY of the drawing the only way for AutoCAD to automatically recognize the "saved" layer state (if I save it in a new state each time?)
@sfulnerQ57QF wrote:If I import the file into Revit,
Stop, don't do this. Link it instead. It's not going to help with your question but it will prevent headaches later on.
That was a mistype. I am linking the file (as you noted, it doesn't help with the headache, but reduces additional ones).
@sfulnerQ57QF wrote:
I'm working with architectural CAD files that have multiple floor plans stacked on top of each other, which are controlled by layer states. If I LINK the file into Revit, it will automatically apply a VG filter based upon the last saved state of the drawing, (which matches whatever AC Layer State it was saved as). The autocad file has 3-4 layer states per floor, so multiple floor buildings are even worse. Is there a way to automatically create separate VG filters by importing the layer states from AutoCAD? Manually making the VG states for each view would be a huge time constraint.
If I try to unload and reload the dwg file, it will either revert to the previous version, or just display all the lines as "ON".
Make sure to check the box below when reload.
![]()
Is importuning a new COPY of the drawing the only way for AutoCAD to automatically recognize the "saved" layer state (if I save it in a new state each time?)
@ToanDN That sort of worked, and I feel it's a workaround. Here's what I mean.
The way the architect has chosen to set up the drawings in CAD, they stack everything in model space, then x-reference the model to separate files for each paper space print job.
If I link the secondary file for each floor, with the check box as indicated, it works as designed/intended, deleting all other layers, and I can make a VG viewport for that if desired.
However, if I save the "central" CAD model file in the open view (with it's layer state), the first time I link it shows the saved layers as intended. If I link (The same) model a second time to another floor, even with that box checked, it seems to forget I did that, and links every single layer, with all of them on. Obviously I get the error of "this may create duplicate instances" of the link, but I would still expect it to work as intended. The main reason I want to use the central file than the separate files, is early on, they don't have the separate xreference files made, so I only have the central model available until late in the project.
@sfulnerQ57QF wrote:
@ToanDN That sort of worked, and I feel it's a workaround. Here's what I mean.
The way the architect has chosen to set up the drawings in CAD, they stack everything in model space, then x-reference the model to separate files for each paper space print job.
If I link the secondary file for each floor, with the check box as indicated, it works as designed/intended, deleting all other layers, and I can make a VG viewport for that if desired.
However, if I save the "central" CAD model file in the open view (with it's layer state), the first time I link it shows the saved layers as intended. If I link (The same) model a second time to another floor, even with that box checked, it seems to forget I did that, and links every single layer, with all of them on. Obviously I get the error of "this may create duplicate instances" of the link, but I would still expect it to work as intended. The main reason I want to use the central file than the separate files, is early on, they don't have the separate xreference files made, so I only have the central model available until late in the project.
There is another workaround:
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.