For editing and selection purposes, there may be situations where you put certain "loose" geometry on a specific layer ... including hidden/smoothed edges. The script could then alter the intent of the user's layer scheme.

By the way, as far as I can tell, if you have geometry on a layers whose visibility is turned off, since its geometry can't be selected, the script will have no impact on those layers. On the other hand, you may want to turn on the visibilty of all layers before running the script.

TIG wrote:This script defaults all 'loose' geometry and any geometry in groups or component definitions to Layer0. The layers of groups or components are NOT changed.

.

Just d/l'd but not tried it yet. I think it will solve a problem I raised long ago to revert all selected group/comp internal geometry to layer0.

I have a question.Does it revert ALL groups on a visible layer, or only selected groups on a visible layer?

The reason I ask is because there are 2 conditions I employ that uses crossed layers within a group.1) This is where the object(s) within a layered envelope group is on layer0, and the documentation is also within the envelope group, but is assigned to a separate "documentation" layer. That way I can chose to make visible both the object and its doc by making both the objects and doc layers visible. By turning off the doc layer, ALL such documentation for all groups on all layers is invisible. By turning on the doc layer, only those object layers that are turned on will display their relevant documentation. This dramatically reduces clutter and gives the documentation more utility.

2) In a similar way, in complex models with many layers that contain subsets of a major object, I will place each subset object (on their own layer) into an envelope layer on its own layer.Imagine an airplane, with fuselage, wings, engines, landing gear, etc. I number my layers hierarchically such as;1.0 fuselage2.0 wing2.1 wing airfoil2.2 wing flaps2.3 wing engines3.0 other stuffSo, Wing grouped objects on layers 2.1, 2.2, 2.3 are contained in an envelope on layer 2.0. The raw geometry is always on layer0. Then I can make visible/invisible the whole wing by turning on/off only layer 2.0. And I can still turn on/off any other part of the wing. It's a bit easier and quicker than using a layer manager.

So if your pluggin reverts all groups/comps raw geometry to layer0, that would screw me up royally. But if it only reverted selected groups/comps, that would be of great use to me cleaning up old models that had all details on layers eschewing layer0. That happened in my early SU days coming from ACAD.

Just had to bump this up and thank you for the great plugin! I'd started a personal project years ago to try to learn SketchUp and was recently running into issues with pieces disappearing in renders unexpectedly. And then I figured out it was cause the raw geometry was on some other layer, that I had hidden, than the group itself. At first I was frustrated and puzzled as to why SketchUp's layers would operate like this, but when I looked into the issue and read some topics on the frame of mind you should have regarding layers and groups and components it all started to make more sense.

But then, sense or no sense, I was horrified at the prospect of trying to correct everything by hand, digging through every group and placing its lines on Layer0. It's just a silly, personal project, but I've put a lot of time into it and want to make it as properly and smartly as I can. So this plugin was an absolute lifesaver, saved me many hours of work and a good chunk of my sanity.

This is a fabulous script indeed, but why is it not listed on Didier's Ruby Depot? Default All Layers , IS listed but not this one "Default Layer Geometry".

Is it still working ? I ask because I use it one of my classes and a MAC user could not get it to do anything. It works fine on my PC but not on this fellow's MAC. Is that why it is no longer listed on Didier's site?

Here's v1.1 viewtopic.php?p=47033#p47033I've updated it to increase its speed slightly on large selections and recoded it a bit better - after 4 years of practice... It's a simple script that should run on all SUp versions and all OSs...

It's been updated to optimize its processing.Either on a Selection [including any nested geometry within selected 'containers'] OR the Whole Model [if nothing is preselected].It's also signed for v2016 compatibility in all Policies.