As discussed in previous threads, you can nest a model under another model then export that model to then be referenced in another scene and it works fine.
However, as Matt said, stay away from referencing models under other models then referencing those. (I'm feeling an xzibit meme coming for this). Bad things happen. -------------------------------------------- Eric Thivierge http://www.ethivierge.com On Wed, Sep 18, 2013 at 11:49 PM, Nick Angus <[email protected]> wrote: > I guess the most common use for us would be to reference the rig into > the model, then reference the model into a shot. > > Cheers, Nick > ------------------------------ > *From:* [email protected] [ > [email protected]] on behalf of Matt Lind [ > [email protected]] > *Sent:* 19 September 2013 13:27 > > *To:* [email protected] > *Subject:* RE: 2014 > > Out of curiosity, Why do you need nesting? > > > > > > Matt > > > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Eric Cosky > *Sent:* Wednesday, September 18, 2013 8:26 PM > *To:* [email protected] > *Subject:* RE: 2014 > > > > > > Good to know, thanks for the reminder about those other issues. Perhaps if > I use the nesting only as a way to maintain initial setups before making > them local I can avoid these problems. > > > > It would sure be nice if they hammered out all the ref model bugs and made > the system something people could trust, and then proved it with a bunch of > sample scenes that verify all these concerns have been resolved. It’s one > of the things I was really looking forward to using when I first got into > Softimage so long ago now, and I never really got to use it as advertised. > > > > > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Matt Lind > *Sent:* Wednesday, September 18, 2013 8:14 PM > *To:* [email protected] > *Subject:* RE: 2014 > > > > I do not advise using nested models. > > > > When you get to the more complicated relationships such as model deltas, > group relations, animation mixer propagation, instances, and so on, you’re > just asking for trouble. > > > > Glad to see improvements, however, as it has far reaching effects beyond > nesting. > > > > > > Matt > > > > > > > > > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Nick Angus > *Sent:* Wednesday, September 18, 2013 8:10 PM > *To:* [email protected] > *Subject:* RE: 2014 > > > > Thanks Eric, we had huge troubles with nested references in 2013, in fact > we gave up on it. So that is definitely a tick in the pro box! > > Cheers, Nick > > Sent from my Windows Phone > ------------------------------ > > *From: *Eric Cosky <[email protected]> > *Sent: *19/09/2013 9:18 AM > *To: *[email protected] > *Subject: *RE: 2014 > > I’ve been successfully using referenced models that contain other > reference models with SI2014. This used to cause stability problems in > earlier versions, but it’s been a while since I checked.. it might have > been 2012 or earlier that I last checked. I’m pretty happy to see it > working these days, regardless. My usage is generally limited to game > export related stuff without referenced material libs, so YMMV. There’s > been enough problems with refmodels over the years I’m not about to say > it’s problem free but being able to nest referenced models is pretty useful > for my workflow and I’m glad it is working for me. > > > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Nick Angus > *Sent:* Tuesday, September 17, 2013 10:12 PM > *To:* <[email protected]> > *Subject:* 2014 > > > > About to take the plunge and update from 2013 (not sp1) to 2014 (latest > build). > > Are there any caveats I should be wary of? > > > > Appreciate any advice either way! > > > > Cheers, Nick > > -------------------------- > 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.
