Grasshopper

algorithmic modeling for Rhino

Rhino defines layers and sub layers as "Layer::Sub-layer1::Sub-layer2" yes?

I immediately assumed that I could bake to a Rhino sublayer using this same syntax. This is not true. I'm using plug-ins like lunchbox and local code to bake and export, but I can't get anything onto specific sublayers. 

Any advice?

Views: 10185

Replies to This Discussion

Hi Will,

With Giulio's bakeattributes you're able to just have the name of the sublayer without having to define the parents. Have you tried that?

Yeah, what i'm working has dozens of duplicate sublayers, which is probably why I didn't think of just target a specific sublayer.

Iteration 1::Frames

Iteration 1::Planking

Iteration 1::Stringer

Iteration 2::Frames

Iteration 2::Planking

Iteration 2::Stringer

and a half dozen of those nested sublayers, and sub-sub-layers. So yeah, I just needed a bit more control.

Here's an updated version of Giulio's BakeAttributes that accepts "full layer path" notation. If you pass it "Layer::SubLayer" as the layer name it will bake to the appropriate sublayer. Danny is right that this is not necessary if you can just target the sublayer by name directly, but in the case where multiple sublayers might have the same name, this full path notation is helpful.

Attachments:

excellent!

Am I right in thinking that Rhino 4 doesn't accept duplicate layer names, is this now acceptable in Rhino 5.

I've always used a parent abbreviation in the naming of sublayers because I once had to save a Rhino file with geometry only option and it took forever to get everything back the way it was.

e.g.

Ships > ShipsName1 > S1_Profile

Ships > ShipsName1 > S1_Midship

Ships > ShipsName1 > S1_Decks > S1_D_ etc.

Hi!

I added this wish regarding layer names in R5.

This is helpful... although, the layers have to exist. I was hoping it would create the layers already nested. If the layer doesn't exist... it makes a layer called "layer::sublayer".

It isn't difficult to create a template layer and sub layer structure and duplicate them and change the highest level format to match, but it is it would be nice :D

Thanks for your help guys, this component is helpful.

Andrew,


Thanks for this update.  It is really helpful!

I haven't been able to get the sublayer part to work.  When I make a layer name called "layer::sublayer", I get hundreds of individual layers called "layer::sublayer", "layer::sublayer1", etc.

Any more hints or specifics on how to get the layers to bake properly?  It's not a huge deal for me to have them all on one individual layer, each object with its own color, but it would be nice to have the ability to pick the layers individually...


Thanks!

Apparently it does not work.

It does not create sub layer.Help me please !

take the quotes off the layer name.

Coucou::Sphere

Same result...

What is the correct syntax?

Ah sorry - my fault, this script depends on the layers already existing. Try the following workflow with the Human plug-in

Attachments:

Ok Andrew, it's work if a layer existing.

I know Human,

thank you for all...

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service