Thanks Jordi, We are in the process of setting that up, we have a pretty good shot management database/toolset here, we are currently publishing a single 'live' cache from Maya until we get the animation cache > asset system sorted.
All fun and games though ; ) N ________________________________ From: [email protected] [[email protected]] on behalf of Jordi Bares [[email protected]] Sent: 28 May 2013 16:48 To: [email protected] Cc: [email protected] Subject: Re: Enveloping a referenced mesh If you go the cache route (which I also recommend) the thing to remember is that you will put yourself on a new problem as suddenly cache versions, automated naming and various other tools will be vital. Plus disk space will be increasing as you won't be able to delete old caches given you won't know who is using them. If this takes you to asset management you better be ready to spend some serious money on RnD. (I rather buy hard drives than add more complexity but if course developers love it Si careful there) My 2 cents Jb Sent from my iPhone On 28 May 2013, at 06:35, Nick Angus <[email protected]<mailto:[email protected]>> wrote: You are of course right Alan, that will always be my preferred workflow. We normally do that as we animate in Maya generally, ironically Soft > Soft is the one giving us the trouble ; ) All sorted for now though, but yes, Alembic pointcache will eventually be our weapon of choice... N ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Alan Fregtman [[email protected]<mailto:[email protected]>] Sent: 28 May 2013 00:30 To: XSI Mailing List Subject: Re: Enveloping a referenced mesh Or you know, more simply, you could... have a rig model + a shaded model for rendering... and apply pointcaches exported from the animated rig, into the rendering model. New shading? export new rendering model. New rig? export new rig model. As long as your topology and naming is consistent across the two, it's win-win. On Mon, May 27, 2013 at 1:18 AM, Nick Angus <[email protected]<mailto:[email protected]>> wrote: Thanks Orlando, as it turns out (courtesy of Chris Gardner) you need to build a model node node to contain the two other model nodes then reference in the 'container' node and it works perfectly! Cheers, Nick ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Orlando Esponda [[email protected]<mailto:[email protected]>] Sent: 27 May 2013 15:16 To: softimage Subject: Re: Enveloping a referenced mesh You could use this technique http://www.softimageblog.com/archives/169, it's very stable. This way you can load just the mesh model in your rendering scenes and load caches on it to avoid evaluation problems on the rig at render time. On Sun, May 26, 2013 at 9:45 PM, Nick Angus <[email protected]<mailto:[email protected]>> wrote: Is this advisable or even possible?, this is the first time I am encountering this problem as we usually animate in Maya and go into Soft via Alembic. We need to keep the rig and mesh seperate so we can work on shading/look dev and rigging simultaneously. The idea was to double reference, ie ref the base mesh into the rig file, skin it then ref that into shots. Any avice greatly appreciated! N -- IMPRESSUM: PiXABLE STUDIOS GmbH & Co.KG, Sitz: Dresden, Amtsgericht: Dresden, HRA 6857, Komplementärin: Lenhard & Barth Verwaltungsgesellschaft mbH, Sitz: Dresden, Amtsgericht: Dresden, HRB 26501, Geschäftsführer: Frank Lenhard, Tino Barth IMPRINT: PiXABLE STUDIOS GmbH & Co.KG, Domicile: Dresden, Court of Registery: Dresden, Company Registration Number: HRA 6857, General Partner: Lenhard & Barth Verwaltungsgesellschaft mbH, Domicile: Dresden, Court of Registery: Dresden, Company Registration Number: HRB 26501, Chief Executive Officers: Frank Lenhard, Tino Barth -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
