dzeibin
commented
5 years ago Ah, this must be the issue we have been seeing also. I couldn't understand why it would happen with some files and not with others.
Open RevitIRL opened 6 years ago
dzeibin
commented
5 years ago Ah, this must be the issue we have been seeing also. I couldn't understand why it would happen with some files and not with others.
Linking in a CAD file that has a layer containing "NPLT" causes the NoPlot routine to fail (it doesn't undo the temporary hide changes - the "Reset No Plot View States" undo entry never gets created) even in views that don't contain the CAD file.
I created a Screencast: https://autode.sk/2J2rNix
This seems like it might be related to the Object Styles issue (that also cropped up in 2018): If a family has a subcategory called "NPLT" (for us it was the Level Head), then "Reset No Plot View States" doesn't happen (like the above). That was an easy fix for us - we just renamed the subcategory in the family and all 2018+ projects (because NPLT in the Level's Type Name provides the needed hiding functionality).
Unfortunately, the only workaround for the "NPLT" cad layer issue is to manually undo the "Temporary Hide for No Plot" entry every time NoPlot is used (which sometimes gets forgotten). Long-term fixes would involve either changing "NPLT" in all cad files (something we'd need to remember to do in the general notes on every project). and which would be a problem when the architect is in cad, or we'd need to change the text string used in Revit to something else (like "NoPLT") - but that would involve changing multiple Type Names and would need to be done in the templates, every existing 2018+ project (and any that later get upgraded), all the typical detail libraries, AND every view that gets copied from older projects instead of the typical library (happens more often than we'd like).
Given that it occurs at a version change, I'm assuming it's an API implementation change that occurred in 2018. I'm hoping there's a way to work around it in the NoPlot code, as even if it's caused by a problem on Autodesk's end, they're not likely to issue a fix for this in 2018.
-Lionel