Issue with entity on multiple layers (tags)

Zaacharms · 18 Aug 2020, 10:41

Hi,
I've had this happen before and never really figured out how to undo the situation.
Some parts are stuck on more than one layer and I'd like to get them separated.
Another issue, which may have caused the problem is the errant edges of the stringer that seem to have resulted from the subtraction made to create it.
Thanks, Marc

entity on two layers.skp

TIG · 18 Aug 2020, 11:44

You have fallen into the Layer trap !
ALL raw geometry - edges and faces - should be assigned to 'Layer0' [called 'Untagged' in newest versions] - never reset your current layer/tag away from that - and when exploding containers ensure the contents don't get the previous container's layer/tag.
You can then assign other layers [or tags in newest versions] to the various 'containers' of this 'unlayered' geometry - e.g. your groups or component-instances...

If you gave got things in a tangle, edit the container and select all, then use Entity Info to default the geometry's layer/tag. Or simply delete the unwanted layer and let its assigned geometry revert to Layer0 etc...

There are tools to help if it's really FUBAR...
e.g. in the PluginStore my LayerWatcher, warns you about making these mistakes to start with, always assigns no-layer/tag to geometry you draw, lets you explode without messing up geometry's layer/tags, and also has tools to 'default' selected geometry's layer/tag, even inside nested 'containers' in the selection...

Zaacharms · 18 Aug 2020, 13:03

Thanks, Tig
I was able to delete the offending layers and let the geometry go back to untagged (layer 0). Then recreate the tags and move the correct geometry back to where I wanted it. It's hard to remember when I got things messed up but I'll be keeping an eye on what layers I'm working on.
Thanks again,
Marc

Dave R · 18 Aug 2020, 14:47

@zaacharms said:

Then recreate the tags and move the correct geometry back to where I wanted it.

It sounds like you missed TIG's point. The geometry should always keep Layer0/Untagged assigned to it. Only groups and components should receive Layer/Tag assignments other than Layer0/Untagged.

Zaacharms · 18 Aug 2020, 15:14

Hi Dave,
That is helpful. I generally don't have any geometry hanging around that isn't grouped nor do I move any that isn't grouped. So the geometry I moved back to 'untaged' were grouped except for some errant wireframe (lines not in any group). It seems that the wireframe could have been the issue. That wireframe showed up after doing a subtraction.
Marc

Dave R · 18 Aug 2020, 15:19

I don't quite understand what you are describing but as long as you follow the "rules" and keep all geometry (edges and faces) untagged and only assign other tags to groups and components, you should save yourself a lot of headaches.

BTW, you are referring to "tags". Does that mean you are using SketchUp 2020 and not 2016 as indicated in your profile? If so, could you please update your profile. That information helps us help you.

Zaacharms · 18 Aug 2020, 16:17

Updated my profile.
I get the rules now on raw geometry vs groups and components.
I was just trying to explain how I got the model sorted out by moving everything back to untaged. It's behaving normally now.
Marc

Dave R · 18 Aug 2020, 16:23

Good deal.

FWIW, TIG has written an extension that will parse through a model file and correct the tagging for all edges and faces back to Untagged. It's called Default Layer Geometry and despite the word Layer used in it, it does work in 2020 with tags as well.