Tag Stacking Order (In lieu of Arranging)

Just playing around with Tags(Layers) and trying to test a statement in another post which said that the Arrange feature in Layout which permits you Move Back / Bring Forward can be achieved using Tags / Layers.

I have watched the very useful Tutorial on Tags / Layers which sets out the golden rules and explains how geometry is changed across layers. But it make no mention of arranging.

From my little experience it would appear that the order in which a Tag is creates dictates its stacking order. Rename Tags so that they appear in a different order alphabetically does not alter their stacking.

Am I correct it this thinking.

Is there another way to bring forward or move back so that this order is respected when multiple layers visible.

TIA

Forget about them being stacked, they are visibility tags, they do not do anything to the physical arrangement of anything.
Which is one of the reasons for the name change. People think they work like layers in 2d applications, just like you saying can I move them back and forward.
In 3d space that which is in front is the geometry that is physically in front.
Layers/Tags allow you to turn on and off the visibility of objects that have been tagged .

In the SketchUp universe, the word ‘LayOut’ refers to the accompanying App LayOut , not the commonly known term ‘layout’

LayOut has an ‘arrange’ functionality, SketchUp has not.

It’s easy to get them mixed up on this forum, watch the category in which they are posted.

1 Like

Yes yes I got that sorted and understand that arrange is a feature of layout.

Hi, yes indeed I got the 2D, 3D difference so was exploring if tags have any form of stacking order. My intent to reduce the amount of tidy up when two component overlap.

I have been using solid tools to effect that tidy up where needed and was looking for a quick way of doing this.

If you want to retain the component name, tags, materials …then use Eneroth’s solid tools

Thank you

That is true for Sketchup, but not for Layout. For some reason, Layout.app doesn’t draw lines based on which geometry is physically in front. You can test this by having two shapes whose edges meet on the same vertical plane. The bottom edge sometimes is drawn over the top edge, and other times it is drawn correctly. I am not sure if there is a rhyme or reason for why.


I don’t see what you are talking about in your video. Even though your roof is set to show dashed lines, it obscures the horizontal plane modelled below it, as it should.

In the two layers I’m toggling on and off, L-RTWL (which represents a retaining wall above the topography) and L-TOPO, you can see that the draw order inside Layout is incorrect (top plan) but is represented properly inside Sketchup (3D view). The 2D view has rendered the bottom lines (topography) instead of the top lines (retaining wall). Looking at the 3D view, you can see that this shouldn’t be happening as some of these lines are as much as 11’-6" below the retaining wall instead of above it. In the end of the 3D video, I’ve toggled “color by layer” if that helps identify what I’m describing better.

This becomes a large issue when establishing line weight hierarchy as you often have objects where edges meet.

You should perhaps post a LayOut file (with a model) that shows your problem.
Have you tagged geometry (edges) inside an object on a different tag than the object itself? “Raw” geometry should never be tagged without a very good specific reason.

No. I only tag groups and components (except for very rare cases not applicable to this topic). It renders correctly in Sketchup, and I even just noticed that it renders correctly in Raster view in Layout (but local permitting offices don’t accept files in raster format because they can’t inspect the geometry and it prints like hot garbage) but it won’t render correctly in Vector or Hybrid views.

This has been a well documented issue on the forums dating back to when tag control was first released in Layout (maybe before for dashed line types).

The top screenshot is vector view in Layout, which shows the lines incorrectly. The bottom screenshot is from Sketchup itself, which shows the lines correctly.

I’ve reset all overrides in Layout to show that the difference isn’t due to overrides, but due to the way the file is rendered.


C0081 Harris Deck v3.4.skp (1.1 MB)
C0081 Harris Deck v3.4.layout (10.9 MB)

OK, it seems to be one of those vector graphic glitches LO has been suffering from since time immemorial. Is your model far from the origin?

A workaround (people hate workarounds) would be to stack viewports with two copies of the same viewport with different tags overridden on two different LO layers.

In my opinion Raster rendering with the “High quality” (300 DPI) setting and with Jpeg compression turned OFF works OK in most cases. I use Vector only for export to DWG.

BTW, your file seems to contain personal information, you might remove that. I’ll delete it from my computer, too, asap.

I don’t use dashed lines in SketchUp much – just for a visual aid for myself when working in SketchUp, e.g. to represent the damp proof level.

If I needed to show the damp proof level in Layout I would trace using a Layout dashed line.

But what is the “correct” representation of the dashed line in SketchUp anyway?

I don’t go deep into trying to understand how SketchUp should or should work in this respect but on my machine and screen – the scene 00 Site Plan is at zoom extents but if I zoom out the dash “scaling” changes and when you start to zoom right in the “scaling” changes again but then at a certain point remains at the same “scaling” the further you zoom in.

But in Layout regardless of the zoom factor in SketchUp the dashed line scale remains the same.

In this situation I might have used the tag override feature to change the contour line type to how I want it in Layout.