I know.
But this is not a solution when sending 4 (or more) passes to the farm with attribute overrides. Basically I have to wait until one pass is rendered, then open scene, switch pass, re-save the scene, re-submit for the pass to pick up correctly... Or I have to create four scenes... and submit to farm... This kinda defies the whole passes workflow... Cheers, Juan - - - Juan Brockhaus | Head of CG Studio Prime Focus London Commercials T: +44 (0)20 7565 1000 | M: +44 (0)7944 720 557 A: 37 Dean Street, London, W1D 4PT, UK www.primefocusgroup.com ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Chris Chia Sent: 14 September 2012 13:29 To: <[email protected]> Subject: Re: picking up ICE attribute in RenderTree still buggy??? The pass issue is a known bug and has been worked on... But to workaround it, save and open the scene in that pass and the ice attribute should be evaluated fine (in that pass)... Chris On 14 Sep, 2012, at 7:19 PM, "Juan Brockhaus" <[email protected]> wrote: Hi, It's the pass changing which causes the problem. Everything is there, all attributes values are correct. (Cached, none cached, set after cache. etc.) As I said, I can see (get, set) the attributes and they are all fine. It's the render tree not picking it up correctly. As you said, if I manually just reselect the attribute it 'snaps' back and all is good. Then I change pass. Color attribute is lost. Deselect, re-select attribute. Everything is fine. Problem is the render farm... that one can't deselect and reselect manually... I will have a look into the OnPassChange event Pete mentioned. Cheers, Juan - - - Juan Brockhaus | Head of CG Studio Prime Focus London Commercials T: +44 (0)20 7565 1000 | M: +44 (0)7944 720 557 A: 37 Dean Street, London, W1D 4PT, UK www.primefocusgroup.com ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Rob Chapman Sent: 14 September 2012 12:10 To: [email protected] Subject: Re: picking up ICE attribute in RenderTree still buggy??? ok , well i believe any problems with the render tree attribute not getting passed over are more to do with the attribute not being stored. Like I said even though the attribute name is available from the cache, when connected to anything it produces a red node or an error about 'wrong type' or similar. This is where I would check first. For render tree , Ive noticed that sometimes the attribute selection gets lost if its anything other than default 'color' and I always turn the default color value to a purple or red so then its easy enough to see that its reverting to default value when rendering because the data is not there. Some folks here have had a problem with passes changing and materials not updating correctly. and in the case the best thing is go to the pass in question, relook at the material and from color_attribute node reselect the correct attribute again. then do a render region. sometimes it takes a 'jiggle' to remind the softimage stack of what you set it to in the first place. On 14 September 2012 11:54, Juan Brockhaus <[email protected]> wrote: The scene is already really basic... One is just random color which doesn't always get picked up... The other one is (as per other mail) just a color value driven from distance from camera to another object. Writing out the cache is not the problem. I can get the values and display them. They are fine. One of the values is also set after reading the cache... Next week I will have a look at the that onPassChangeEvent like Pete suggested. I am up against it and don't have the time to write a script just now... Thanks, Juan - - - Juan Brockhaus | Head of CG Studio Prime Focus London Commercials T: +44 (0)20 7565 1000 <tel:%2B44%20%280%2920%207565%201000> | M: +44 (0)7944 720 557 <tel:%2B44%20%280%297944%20720%20557> A: 37 Dean Street, London, W1D 4PT, UK www.primefocusgroup.com ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Rob Chapman Sent: 14 September 2012 11:47 To: [email protected] Subject: Re: picking up ICE attribute in RenderTree still buggy??? depends how or what you are trying to do. Lately Ive found adding a custom attribute display per attribute I need caching will always save that attribute in the cache. without then ICE saves the attribute name but not the type or any data. Always when bringing in the cache into a new scene I can check if the attribute has been saved correctly. Ive not had much problem with render tree attributes passing over is there anyway you can recreate in a simple scene? On 14 September 2012 11:33, Juan Brockhaus <[email protected]> wrote: Hi, Is it true, that it is still buggy as hell to pick up ICE attribute in the Render Tree? Or do I miss something here? Display attributes doesn't really help, getting and setting the attribute also doesn't help always. Tried to multiply the attribute with 1 and set a key. (remember that one from scops to get evaluated..) ... etc. Any ideas? Soft 2013 SP1 on Win7, btw Ta, Juan - - - Juan Brockhaus | Head of CG Studio Prime Focus London Commercials T: +44 (0)20 7565 1000 <tel:%2B44%20%280%2920%207565%201000> | M: +44 (0)7944 720 557 <tel:%2B44%20%280%297944%20720%20557> A: 37 Dean Street, London, W1D 4PT, UK www.primefocusgroup.com
