0 layer XREF override

[AIR_123]

Hi Guys,

Could you please advise on following issue.

If I apply XREF overrides for all the layers it affects all the layers except 0 layer of XREF while printing. Why is that? Any setting to fix it? Thx

[jggerth · Accepted solution]

Layer 0 and DEFPOINTS are 'magic' layers, and should not be used fro drawing anything on, especially in a file that will be used as an XREF.  The fix for your issue, is to fix the Xref file and move anything on layer 0 to a proper named layer.

XREF|0 is not a possible layer, there can be only one (layer 0 that is...)

[AIR_123]

Ok. Thx. Indeed good words 😉 How to explain that to everyone using ACAD, to not leave stuff on layer 0 ;)?

Original XREF is not mine, but 3rd party, so have to deal with it some how...

[Anonymous]

Blocks with entities on layer 0 will match the layer parameters of layer on which they are inserted.  Layer 0 should be used ONLY for the creation of blocks which one desires to acquire the properties of the layer on which the block is inserted and NOTHING else.  NOTHING else should be on layer 0.

Similarly, layer DEFPOINTS, which was originally designed to hold the DEFining POINTS for associative dimensions and was designed not to plot.  Once people discovered that useful feature they began drawing on layer DEFPOINTS ... it was a bad idea then (with the sole exception of PS viewports) and worse now.  NOTHING should be drawn on layer DEFPOINTS.  If you want something on a layer that doesn't plot, create a layer for that and set it to no plot. Layer DEFPOINTS mimics layer 0 in many ways.  It will follow the XREF and not be able to be turned off in the target drawing without turning off the entire reference file.

DON'T, just don't.

[jggerth]

Then you'll need to fix the reference file, and move everything from Layer 0  to an appropriate layer.  Or communicate with the entity supplying the file(s) and get them to fix them so they are usable.  At this point you're dealing with GIGO, and that's not a situation that will get you professional results.

[AIR_123]

Thx. That is already fixed.

Another related question I have. If I use VP overrides, why I need to specifically activate a viewport? It seems that if viewport is not active then VP features in LM not taking any effect while printing?

[Alfred.NESWADBA]

Hi,

>> Another related question 

For new questions please create a new thread, otherwise the search function in forums can't find these "sub"-questions.

>> If I use VP overrides, why I need to specifically activate a viewport? 

How should AutoCAD know which viewport has to have overrides if you don't have activated the one that you want to show that overrides?

- alfred -

[AIR_123]

---

@Alfred.NESWADBA wrote:

Hi,

>> Another related question 

For new questions please create a new thread, otherwise the search function in forums can't find these "sub"-questions.

>> If I use VP overrides, why I need to specifically activate a viewport? 

How should AutoCAD know which viewport has to have overrides if you don't have activated the one that you want to show that overrides?

- alfred -

---

OK. 

Why the overrides are there before I activate something? And what is then affected if I change something, before viewport activation?

[Alfred.NESWADBA]

Hi,

>> Why the overrides are there before I activate something?

Because AutoCAD-internally the paperspace itself is like a viewport 😉

- alfred -

[AIR_123]

---

@Alfred.NESWADBA wrote:

Hi,

>> Why the overrides are there before I activate something?

Because AutoCAD-internally the paperspace itself is like a viewport 😉

- alfred -

---

So what is affected when changing the override settings without viewport being activated? Everything in PS?

[Alfred.NESWADBA]

Hi,

>> So what is affected when changing the override settings without viewport being activated?

Objects in paperspace that are on overridden layers.

That does not mean objects visible through viewports in that layout.

- alfred -

[AIR_123]

OK. Thx

I was confused by the fact that XREF's also have VP overrides in PS, but indeed you can XREF things in PS...

[AIR_123]

Why custom colors in XREF blocks are not affected by overrides?

[Alfred.NESWADBA]

Hi,

>> Why custom colors in XREF blocks are not affected by overrides?

What are "custom colors"?

- alfred -

[AIR_123]

---

@Alfred.NESWADBA wrote:

Hi,

>> Why custom colors in XREF blocks are not affected by overrides?

What are "custom colors"?

- alfred -

---

Hmmm, your question makes me think now... 🙂
In order to not create custom plot styles, I'm using standard monochrome with small modifications, colors from 1 to 9 prints black, rest colors.

Say if I want to print XREF, which has block (set to layer_X) containing two lines, one set to "by layer", other set to specific color (say 132). If I make for XREF layer_X override to print to color 252, it prints "by layer" line - color 252 and other one - color 132... What is wrong with my logic?

[Alfred.NESWADBA]

Hi,

>> Say if I want to print XREF, which has block (set to layer_X) containing two lines, one

>> set to "by layer", other set to specific color (say 132). If I make for XREF layer_X override

>> to print to color 252, it still prints to color 132... What is wrong with my logic?

I marked in orange the critical part ...

Whenever you specify a layer to have a different color only those entities will be represented in that new color, which have color = byLayer.

So if an object has color=132 that object does not get it's color from the layer, so this object also does not get it's color from any layer-override!

In case you do have AutoCAD 2016 or newer there is a systemvaraible XREFOVERRIDE (>>>details<<<) which you can activate, then all objects from the XRef are seen as "color = byLayer" (independent of the real value).

- alfred -

[AIR_123]

---

@Alfred.NESWADBA wrote:

Hi,

>> Say if I want to print XREF, which has block (set to layer_X) containing two lines, one

>> set to "by layer", other set to specific color (say 132). If I make for XREF layer_X override

>> to print to color 252, it still prints to color 132... What is wrong with my logic?

I marked in orange the critical part ...

Whenever you specify a layer to have a different color only those entities will be represented in that new color, which have color = byLayer.

So if an object has color=132 that object does not get it's color from the layer, so this object also does not get it's color from any layer-override!

Yes, I already thought so, but this object is part of a block which has his own layers settings. So in my opinion, it is more logical to follow orders of higher level hierarchy settings (block in this case). It is especially important for XREF's which are produced by 3rd parties. It means I need to interact and change setup of their drawing before my overrides takes effect...

In case you do have AutoCAD 2016 or newer there is a systemvaraible XREFOVERRIDE (>>>details<<<) which you can activate, then all objects from the XRef are seen as "color = byLayer" (independent of the real value).

Time to upgrade...

What is the best solution for releases before 2016?

- alfred -

---

Thanks. My comments in red.

[Alfred.NESWADBA]

Hi,

>> Yes, I already thought so, but this object is part of a block which has his own layers settings

That does not matter, when an entity has a color <> byLayer (or within a block <> byBlock) then this entity has this color, independent of inside a block or not.

>> Time to upgrade...

>> What is the best solution for releases before 2016?

If you don't have the chance to update: If you can "destroy" the referenced drawing you can open the referenced drawing in AutoCAD, run command _SETBYLAYER (>>>details<<<) and all objects will be converted to color = byLayer ... but the previous setting is lost. So I recommend to do that only with a copy of the DWG.

- alfred -

[AIR_123]

---

@Alfred.NESWADBA wrote:

Hi,

>> Yes, I already thought so, but this object is part of a block which has his own layers settings

That does not matter, when an entity has a color <> byLayer (or within a block <> byBlock) then this entity has this color, independent of inside a block or not.

That I understand, but that is not logical from override point of view. Override should be leading in this case. But ok, it is how it is.

>> Time to upgrade...

>> What is the best solution for releases before 2016?

If you don't have the chance to update: If you can "destroy" the referenced drawing you can open the referenced drawing in AutoCAD, run command _SETBYLAYER (>>>details<<<) and all objects will be converted to color = byLayer ... but the previous setting is lost. So I recommend to do that only with a copy of the DWG.

- alfred -

---

Thanks again. Good suggestion!