Sorry about the typos, i have thumbs like breadsticks, and tablets and i never seem to get along.
On Saturday, September 20, 2014, Ognjen Vukovic <[email protected]> wrote: > I assume when working withn ref. models you should plan on having > everything locked more or less... so baisicly to set your rig up in the > model with finalized shaders and then move foreward, and avoid having to > change anything latter on, names and such should be frozen in the modeling > phaze, shader paramters can be changed this way in the model and it will > propagate to your scenea. the rest you can manipulate with overides to > avoid breaking anything.. > > On Friday, September 19, 2014, Jason S <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Too bad, but it's good that it's in great contrast with the rest of the >> referencing system :] >> >> On Friday, September 19, 2014 17:12:28, Matt Lind wrote: >> >>> No. >>> >>> We've found trivial things such as renaming any object using a material >>> from the referenced material library can cause all referenced materials to >>> lose their assignments. Adding/removing an object from a referenced model >>> using the referenced material library can trigger it too. >>> >>> In short, the system is too fragile to be of use in it's current state. >>> If the bugs were fixed, it could be really useful. >>> >>> >>> Matt >>> >>> >>> >>> >>> -----Original Message----- >>> From: [email protected] [mailto: >>> [email protected]] On Behalf Of Jason S >>> Sent: Friday, September 19, 2014 1:45 PM >>> To: [email protected] >>> Subject: Re: external material libraries..... >>> >>> >>> I recall exporting an .xsi with a bunch of materials, importing it as a >>> reference model, and assigning materials from that, but it wouldn't stay >>> referenced. >>> >>> Even if end functionality is a bit sketchy, is there a specific process >>> to make it work? >>> cheers >>> >>> On Thursday, September 18, 2014 13:30:51, Ognjen Vukovic wrote: >>> >>>> I reckon its safer to import them through referenced models. >>>> >>>> On Thursday, September 18, 2014, Paul Griswold >>>> <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Holy cow, talk about deja vu! >>>> >>>> I was up until 2:30 am dealing with the same issue. >>>> >>>> Are you using Mental Ray or something else? >>>> >>>> I'm using Redshift on this project. The only solution that >>>> managed to work was to merge the dysfunctional scene into a new >>>> scene, make sure the external material library had all locks >>>> removed, and then save save save save as I fixed everything. >>>> >>>> I tried some of the solutions for the old disconnected shaders bug >>>> from previous versions of XSI, but all that did was crash >>>> Softimage. Merging was the only solution. >>>> >>>> -Paul >>>> >>>> >>>> On Thu, Sep 18, 2014 at 5:02 AM, Rob Wuijster <[email protected] >>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>> >>>> Hi, >>>> >>>> Do people use external material libraries a lot? >>>> >>>> We tried them on a (now finished) project, but had some weird >>>> issues along the way; >>>> Objects loosing materials and rendering the default gray >>>> material, tons of non-used materials that magically appeard >>>> between sessions in scenes etc. >>>> In the end we made everything local again to fight the >>>> deadline. >>>> >>>> Any thoughts, tips on this? >>>> >>>> -- >>>> >>>> cheers! >>>> >>>> Rob Wuijster >>>> [email protected] >>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>> >>>> \/-------------\/----------------\/ >>>> >>>> >>>> >>> >>> >>> >> >>
