I found upon loading the scene a new that a number of odd things have happened... Totally unexplainable and stuff I have never seen before. One refmodel had moved into a hidden partition, the object that flickered was in a wrong shader group, one refmodel had shifted its SRT relative to its original position, a unused shader had replaced a shader in a partition with shader overridden. I have never experienced this, so I a dumbfounded.
Morten Den 16. april 2015 kl. 16:55 skrev Mario Reitbauer <cont...@marioreitbauer.at>: > I guess you need to debug a bit to find the actual problem. > What happens when you only rerender one of the broken frames ? > What was the log saying ? Any error or anything ? > > Are there potential overrides which could somehow cause problems ? > > 2015-04-16 14:20 GMT+02:00 Morten Bartholdy < x...@colorshopvfx.dk > <mailto:x...@colorshopvfx.dk> > : > > Thanks to all who helped me hit the ground running with an alembic workflow > > moving animation from Maya to XSI for rendering. > > > > I have run into something puzzling tough - I have a textured and shaded > > model in XSI where each subpart is referenced in (the total filesize for > > the models is about 3GB). I then load the alembic animation file attaching > > it to my local model based on naming convention. This basically works fine, > > but in last nights render one object (out of 4700+ objects) rendered with > > a wrong shader on a few frames. It gets its shader from a group in its > > parent model, there is no duplicate geometry, it is a standard Arnold > > shader so no 3rd party stuff that might not be present on all render nodes > > and it is not present in another group where it could get a different > > material, so I am wondering if somewhere here with alembic experience has > > come across something similar? > > > > Thanks - Morten > > > > > >
