Changes to viewport layers revert on Xref reload

[aswartzell]

Alright. Here's a tough one. Our sheet files are not retaining changes to referenced layers (i.e. freeze), as if visretain were set to 0, but it's set to 1!

To put a sheet together, we typically make Model Space Views in view files using the Navigator, and then drag from the Navigator to paper space of the sheet file. Before we upgraded to AutoCAD Architecture 2008 (from ADT 2006), this worked fine--I could freeze layers in viewports, they would stay frozen. Now, any changes to referenced layers in the sheet file revert to the Xref's layer table as if visretain were set to 0 (but it's not).

However, if, in the same sheet file, I detach that Xref, attach the same file manually in model space, make a new viewport in paper space, and then change referenced layers, it retains the changes like it's supposed to!

Also, this is only a problem when the project is loaded in the navigator. For instance, if i open a sheet and then navigate to another project, then mess with layers and reload the Xref, the layers behave as I would expect them to.

It seems clear that there's something going on behind the scenes when I put the model space view on the sheet, I just don't know what that is, and I'm hoping that it isn't some crazy bug that's totally out of my control. Any thoughts would be greatly appreciated.

-Andrew

[stelthorst]

From a review of what's new in ACA 2008

Projects - Views drive Sheets! This one is big. if you have ever spent a lot
of time setting up a View file and then dragging to a sheet, and then later
edit the view file's layers, or other display settings only to find that
the sheet did not update, you will like this new project navigator option.
Just turn it on and watch it work. Very nice. And it works exactly as you
expect. if you change a view - boom, the next time the sheet opens it
matches!

There's probably a variable that will turn this off if you like. I'll check when I get to work tomorrow.

Hope this helps,

[aswartzell]

Thank you. I'll be eagerly awaiting your findings!

[stelthorst]

Thank you. I'll be eagerly awaiting your findings!

Hi Andrew,

Check the VPLAYEROVERRIDES system variable. If it's set to 1 change it to 0.

[aswartzell]

VPLAYEROVERRIDES is a read-only variable, but I tried toggling VPLAYEROVERRIDESMODE and that doesn't seem to make a difference. It's a good thought, though. Thanks!

[aswartzell]

Problem solved. There's an option in the Modify Project dialog box. If "Match Sheet View Layers to View" is set to "Yes", layers in viewports created with the Navigator will behave as if VISRETAIN is set to 0. I set it to "No", and my problem disappeared. See the attached screenshot if you're not sure where this is...

[stelthorst]

Thank you for posting the solution. I'm sure you have helped countless other people who have/will run into the same problem.

Sorry I couldn't be more help. Even though I have 2008 loaded on my machine I am trying to finish up a project before I migrate to it.

[dkoch]

Problem solved. There's an option in the Modify Project dialog box. If "Match Sheet View Layers to View" is set to "Yes", layers in viewports created with the Navigator will behave as if VISRETAIN is set to 0. I set it to "No", and my problem disappeared. See the attached screenshot if you're not sure where this is...

This is a new feature added to 2008, based on the often requested ability to have the layer settings in the View file and the Sheet file stay synchronized. In previous versions, the initial layer settings in the Sheet file would match the view file when a view from a View drawing was dropped into a Sheet file. Many people noted that work often goes on long after that point, and many times the layer settings are changed in the View file during that subsequent work. Short of deleting the viewport, etc, in the Sheet file and recreating it, there was no way to automatically keep the layer settings in the View and Sheet files coordinated. [Setting VISRETAIN to 0 in the Sheet file, saving and reopening it would reset the layers back to the way they are in the source Construct or Element file, not the View file.]

If that does not work with your workflow, then turn it off. But you might want to consider whether you want to adjust your workflow to take advantage of this new feature.