ice compound references

[Sam Cuttriss]

is this all there is ion the docs about references?

http://download.autodesk.com/global/docs/softimage2013/en_us/userguide/index.html?url=files/iceref_Get_Data.htm,topicNumber=d30e557572

I use references a bunch but i start to falter when i want to use them more than a couple of times.

i would love it if i could find a way wholesale change the context of everything within a compound.

so that all self.* attributes update to the new referenced context

as it stands i have to seriously reengineer my compounds if i want to use them outside their original context.

another oddity is references do not respect pass through nodes.

curious if thats an intended limitation?

[Grahame Fuller]

You can use the In and Out Name ports of an empty Get Data as if it was a Passthrough node. That way you can use a single Get Data node to pass its reference via Out Name to a bunch of different subcompounds, each of which uses an empty Get Data to pass the object reference along to various other Get Data nodes to get specific attributes.

gray

[Sam Cuttriss]

It would be great to be able to take a functioning compound from one polymesh, 

copy it to something else,

and have it continue act identically by assigning its original context with a reference to the original polymesh.

ie: internal self.* would be assessed relative to the compounds reference context.

once these changes need to be propogated several compounds deep with other peoples published compounds, things get far more squirrely.

i cant see the value of the exposed "reference" when compared to in_name?

is there any good documentation in this area?

[Peter Agg]

This is actually my second biggest gripe with Softimage at the moment - having to make people add references twice/whatever just makes things feel soooo sloppy when you're making compounds! Using a GetData node as Gray mentioned covered a lot of cases, but there's enough exceptions to make it painful nevertheless (usually with instancing from groups, sharing fcurve profiles and a couple of other things I forget...).

[Sam Cuttriss]

second...?

do share

[Peter Agg]

Ah, yeah. Python 2.6 on Linux, forgot to add that. :)

On 12 June 2012 23:51, Sam Cuttriss <tea...@gmail.com> wrote:

second...?

do share