Can we break the chain of reference links?

[David Aynardi]

Assume 3 files:

File 2 includes a design layer viewport which references file 1.

File 3 includes a design layer viewport which references file 2.

It appears that when file 3 is opened, in addition to updating the referenced information from file 2 VW also follows the refence links from file 2 back to file 1 and updates this "indirect" information as well. This ensures that file 3 is not cut off from the latest version of the info from file 1 even when file 2 has not been opened or updated.

Is there a way to restrict VW to review only the last generation of reference links without pursuing the chain to increasingly remote drawing files? (When file 3 is opened, read only the direct links from file 2, do not pursue the links from 2 back to 1)

On large projects we experience unacceptabe wait times as the software traces out all the reference links, many of which are turned off and not relevant to the drawing we are trying to open. This could be avoided if we could limit the search to only the last generation of linked files. If we need information from a more remote file, we prefer to manually establish direct links without passing information through intermediate files.

[panta rhei]

I don't think we can, but this is a brilliant wish list item!

Off the top of my head: the ability to be WGRd could be a layer property.

[Jeffrey W Ouellette]

David,

I think the AutoUpdate for WGRs/DLVPs should work.

When you first create a WGR/DLVP the "Select Viewport Source" dialog should prompt you. Toward the bottom, there is an option to "Automatically update out of date reference during file open" leave this unchecked. Also, make sure "Save referenced cache to disk" is checked.

In a current document with WGR/DLVP in place, go to the Organization dialog and edit the "References" tab. Select the reference file and "Edit..."

In the subsequent dialog, the setting should correspond.

[David Aynardi]

Jeff.

I tried the approach you suggest. This prevents automatic updating but does not restrict updating to the last generation of reference files when the link is finally updated manually. You still end up with the big snowball of redundant referenced layers.

Following are two layer lists. First is the layer list immediately after purging unused layers. The first 3 layers are actually in the file. The ones starting nna# are referenced from the top tier of reference files.

A109 Low roof R1.vwx contains 14 layers

///

1:1 1:1 Titlebock

1:96 Bkgnds

1:96 Roof Plan

1:96 Grids

1:96 NNA#19_Grid: Lvls 6-8

1:96 NNA#19_Property

1:96 NNA#19_Grid: Lvl 5

1:96 NNA#21_Lower Roof

1:96 NNA#21#17_Grid: Lvls 6-8

1:96 NNA#21_Area ID

1:96 NNA#21_GRIDS roof

1:96 NNA#21_Penthouses

1:1 NNA#19_1:1 Titlebock

1:96 NNA#19_Grid: Lvls 1-4

And here is the list after manually updating a single refrence file (The link was not updated automaticly because file was set as you suggested).

A109 Low roof R1.vwx contains 54 layers

///

1:1 1:1 Titlebock

1:96 Bkgnds

1:96 Roof Plan

1:96 Grids

1:96 NNA#19_Grid: Lvls 6-8

1:96 NNA#21_Lower Roof

1:96 NNA#21#17_Grid: Lvls 6-8

1:96 NNA#21_Area ID

1:96 NNA#21_GRIDS roof

1:96 NNA#21_Upper Roof

1:96 NNA#21_Grids 6-8

1:96 NNA#21_Penthouses

1:96 NNA#21#16_Lvl 6a, 7a, 8a

1:96 NNA#21#16_Lvl 6, 7, 8

1:96 NNA#21#16_Stairs Lvl 8a

1:96 NNA#21#16_Stairs Lvl 6

1:96 NNA#21#16_Stairs Lvl 7

1:96 NNA#21#16_Stairs Lvl 6a, 7a

1:96 NNA#21#16_Stairs Lvl 8

1:96 NNA#21_Lvl 8

1:96 NNA#21#17_Property

1:96 NNA#21#17_Grid: Lvl 5

1:1 NNA#21#9_1:1 Titlebock

1:96 NNA#21#9_1/8" symbols

1:48 NNA#21#9_1/4" symbols

1:96 NNA#21#16_Lvl 1

1:96 NNA#21#16_Grids 6-8

1:96 NNA#21#16_Lvl 6 area ID

1:96 NNA#21#16_Lvl 6A area ID

1:96 NNA#21#16_Lvl 7 area ID

1:96 NNA#21#16_Lvl 7A area ID

1:96 NNA#21#16_Lvl 8 area ID

1:96 NNA#21#16_Lvl 8A area ID

1:96 NNA#21#16#10_Grid: Lvls 1-4

1:96 NNA#21#16#10_Property

1:96 NNA#21#16#10_Grid: Lvls 6-8

1:96 NNA#21#16#10_Grid: Lvl 5

1:96 NNA#21#16#16_Lvl 1

1:96 NNA#21#16#16_Area ID

1:96 NNA#21#16#16_Grids 1-4

1:96 NNA#21#16#16#10_Grid: Lvls 1-4

1:96 NNA#21#16#16#10_Grid: Lvls 6-8

1:96 NNA#21#16#16#10_Grid: Lvl 5

1:1 NNA#21#16#10_1:1 Titlebock

1:1 NNA#21#16#9_1:1 Titlebock

1:96 NNA#21#16#9_1/8" symbols

1:48 NNA#21#16#9_1/4" symbols

1:1 NNA#21#17_1:1 Titlebock

1:96 NNA#21#17_Grid: Lvls 1-4

1:96 NNA#21#16#16#10_Property

1:1 NNA#21#16#16#9_1:1 Titlebock

1:96 NNA#21#16#16#9_1/8" symbols

1:48 NNA#21#16#16#9_1/4" symbols

1:1 NNA#21#16#16#10_1:1 Titlebock

As you can see, the same layers are listed redundantly, once for each appearance they make in successive referenced files. This is what I'm trying to avoid.

[David Aynardi]

The reason I got interested in this (other than the long load times we have experienced) is that the VW layer/class map utility flashes a warning when run in some of our drawings, telling us that the file contains over 500 layers.

My layer-list script confirmed the "over 500 layers" that the class/layer map objected to. These layers are not actually in the drawing but are the product of the snowball effect discussed above.