Yeah go the way that Dave is suggesting. No reason to have expressions when you can pull the params directly. Just make sure you use the tools I'm the user menu to use this model. On Oct 7, 2013 6:30 PM, "David Barosin" <[email protected]> wrote:
> I would bring the parameters in directly into the ice tree using a get > data node rather than an expression. > > > On Mon, Oct 7, 2013 at 6:14 PM, Jeffrey Dates <[email protected]>wrote: > >> Hiya guys, >> >> I'm running into something I don't remember coming across before and was >> hoping you guys can point out what I'm doing wrong. >> >> I have an ICE Shape mixer controlled by a Custom Property Params.. ( >> just expressioned an == to the weight. ) Nothing fancy. >> >> However, when the scene is reloaded or a model is exported, the >> expressions set themselves to Pass.Through and nullifies the connection. >> >> What are some things to look at that cause this!? >> >> OR, if the flaw is my workflow, how are you guys typically controlling >> the ICE Shape mixer!? >> >> I feel like this has come up before.. but I've never experienced it >> myself as of late. >> >> thanks in advance. >> >> Jeff >> >> -------------------------- >> To unsubscribe: mail [email protected] with >> subject "unsubscribe" and reply to the confirmation email. >> > > > -------------------------- > To unsubscribe: mail [email protected] with subject > "unsubscribe" and reply to the confirmation email. >
-------------------------- To unsubscribe: mail [email protected] with subject "unsubscribe" and reply to the confirmation email.
