guapador
05-19-2009, 01:35 AM
Essentially, the issue I'm having is that when I use a any Maxscript to copy, align or distribute an object with a Float Expression constraint, it behaves slightly differently than a standard copy or array.
When I copy or array the object in Max, the variables in the copied expressions get updated to point to the copied object. For example in rectangle01 the variable Panel Pos points to rectangle01. When I copy the object rectangle02 is created and the PanelPos variable now points to rectangle02. When I run a maxscript to distribute the panel, the PanelPos variable in Rectangle25 still points to Rectangle01, (the original object). This destroys the parametric behavior I'm trying to build into my system because all the rectangles behave the same rather than vary based on their unique position.
Is there a way to make the Maxscript copy function mimic the behavior of the internal max copy function? The script I'm using to distribute my geometry is using the maxops.clonenodes function to make copies.
When I copy or array the object in Max, the variables in the copied expressions get updated to point to the copied object. For example in rectangle01 the variable Panel Pos points to rectangle01. When I copy the object rectangle02 is created and the PanelPos variable now points to rectangle02. When I run a maxscript to distribute the panel, the PanelPos variable in Rectangle25 still points to Rectangle01, (the original object). This destroys the parametric behavior I'm trying to build into my system because all the rectangles behave the same rather than vary based on their unique position.
Is there a way to make the Maxscript copy function mimic the behavior of the internal max copy function? The script I'm using to distribute my geometry is using the maxops.clonenodes function to make copies.