Baking Attributes

Hi everyone...

I am trying to also bake attributes like color and material ...

I found Giulios brilliant Component:

http://www.grasshopper3d.com/forum/topics/bake-color-gradient

it seems it is just working with Gh 8.002?

I can´t find out how to change the code to 8.010....

Can anyone help?

or is there any workaround?

ok, worst case: go back to 8.002

thx,

robin

Replies to This Discussion

Permalink Reply by Giulio Piacentino on June 20, 2011 at 6:42am

Hi Robin,

could you please see if the newer version posted here works on your system?

Thanks,

- Giulio

__________________

giulio@mcneel.com
McNeel Europe

Permalink Reply by Robin on June 20, 2011 at 7:54am

Giulio,

Thx,

Version 807 works fine now...

I appreciate your work very much....

Permalink Reply by Jonathan Sheridan on January 1, 2014 at 10:32am

Co-incidentally - is GH 0.8.52 w/ groups - the most recent version of that component too? I am trying to use your tool to bake layer names, as text objects onto the single objects contained within my named layers.

Just wondered why the component states it is old in GH 9.0061??? And if it is an old version, what might the new one bring?

In Hindsight it seems I can't do this… i.e. use the Rhino Layer names to create text from and bake into the parts respective layers… shame.. I will take another look at your tools which might be able to help.

Permalink Reply by Hannes Löschke on January 2, 2014 at 2:55am

The "OLD" icon just indicates that a component was compiled for a GH version that dates a few versions back. In most cases, it will continue to work just fine.

I'm a little confused about what you want to do exactly. I guess, you somehow select geometry and want to extract the attributes (like the layer). Then create a Text tag with that layer name and bake that back to the objects location and to the specified layer.

There are several Tools to extract Attributes (Horster, Elefront, ...) and even more to bake them (Horster, Elefront, Scarab, ...).

Permalink Reply by David Rutten on January 2, 2014 at 3:57am

Eh, no. The OLD icon means the component has been replaced with a newer version. The component that was used in the file is no longer available on the toolbars. It could be that the newer version has more inputs or outputs, or -in rare cases- it behaves differently. If it's just a matter of more inputs or outputs then there's usually an automatic upgrader provided which can be used from the Solution->Upgrade Components... menu item. If there's a functionality difference there might not be a straightforward upgrading possible and it requires human intelligence to replace the old with the new.

For GHA developers, whenever a component class has been tagged with the Obsolete() attribute or if the word "OBSOLETE" occurs in the component class name then the OLD icon will be drawn. If you want to know how to provide your own upgraders I can explain that, but it's cumbersome.

David Rutten

david@mcneel.com

Permalink Reply by Hannes Löschke on January 2, 2014 at 4:22am

Thanks. This had me confused. Should have looked it up instead of guessing. :D

At a superficial glance, for this case the OBSOLETE attribute doesn't apply since Giulio didn't actually make the BakeAttributes obsolete or provide a newer version. I forgot that it is a script and the scripting component it was written in got outdated. So while my thinking was all wrong, my statement in general terms is kind of true for this special case...

Anyway, I'd love to see the upgrader process explained for future reference if you don't plan on changing that for GH2.0.

Permalink Reply by David Rutten on January 2, 2014 at 4:24am

I am planning on making it easier, so any information would be GH 1.0 only.

David Rutten

david@mcneel.com

Permalink Reply by Hannes Löschke on January 2, 2014 at 5:41am

I think most of us can wait until the first Rhino 6 Betas.

Permalink Reply by David Rutten on January 2, 2014 at 6:10am

Rhino6 betas will ship with Grasshopper 1.0

Grasshopper 2.0, which I'm slowly typing on, is months, maybe even a year away from seeing the light of day.

David Rutten

david@mcneel.com

Permalink Reply by Hannes Löschke on January 2, 2014 at 8:42am

hmm... so what's the expected life time of GH 1.x once I leaves Beta?

Do you think it worth to fully implement all upgrading stuff when I might need to in maybe half a year? I mean, I could live with a beta component that needs to be manually replaced after an update...

Permalink Reply by David Rutten on January 2, 2014 at 9:28am

The last release saw the move from WIP to Beta. There will be no new features in GH1, only bug-fixes.

I do not know what the life-time is for GH1. I suppose we'll keep shipping it with Rhino releases until GH2 is out of Beta.

I don't think it's worth spending a lot of time writing upgraders. The old components work just as well as they always have, there's nothing 'wrong' with them that needs to be fixed, it's just that newer ones are available should you like to use them.

David Rutten

david@mcneel.com

Permalink Reply by Danny Boyes on January 2, 2014 at 4:41am

I think it should also be noted that the OLD tag refers to the GH component only. Where someone has written a VB/C# SCRIPT, like Giulio's Bake Attributes, it doesn't necessarily get an update but the GH Script Component does, it will show the OLD tag, which can lead to this confusion.