Object Node Refresh

This is a tip to avoid a lot of frustration when using an Object Node.
The problem with this node is that it doesn't always reflect the expected ports.

objectnode

Follow up:

I have made a little setup to make my point.
It is a very basic setup with a null containing 3 cubes.
In my xpresso I made a hierarchy node to point to the cubes.
So far so good, well no!!
Look at the ports on the object node, they do not reflect the expected ports of a cube. That is odd.
The strange thing is that the whole setup is 100% correct (you can check the name port on the object node and it will confirm it is a cube)

Here is the solution.
To make the object node do what you expect you have to help xpresso a bit.
You have to drag an example object in the editor (in this case a cube), reconnect the hierarchy to this node and everything works as expected. All the ports reflect a cube alright.

object_node

The point I am trying to make is that xpresso does not update the ports on the object node as expected.

2 comments

Comment from: base80 [Member] Email
I seriously think Maxon should fix this issue
2007-02-12 @ 17:23
Comment from: Fluffy [Visitor]
This is not a bug, just an Xpresso referencing setup that needs to be done properly.
The reference mode of the Object node needs to be set to "Use Start Position", and the start position parameter set to "Down in Hierarchy".
Once done, the object node will update properly, no matter what type of object your from as a child of your parent object.
2007-02-17 @ 19:39

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.
PoorExcellent
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)
This is a captcha-picture. It is used to prevent mass-access by robots.
Please enter the characters from the image above. (case insensitive)