Daniel Browne wrote:
> We are using -exportPathNames aaaaaaaaaa already but the paths still change=
> on us. Actually we're using -exportPathNames nnaaaaaaaa (relative shaders =
> and libraries) to accommodate linux and mac machines on our farm, but the o=
> ther path related flags are all absolute.
Eww.
Does the problem happen only with certain scene files,
or is the behavior random even /within/ a single maya scene file?
(ie. within a single render of the scene file)
If it's seemingly random within a single scene, have you checked
to see if the problem only happens on a certain machine or group of
machines?
If you can get both good and bad behavior from separate scene files,
it /might/ be something saved into the maya scene file causing this.
Also: can you show (a) the complete maya command line and
(b) a snip of the problem lines from the .mi file that shows the problem?
(include a few lines of context above and below the problem lines)
And if the behavior is seemingly intermittent, try to also include
the same info from a good run (command and sample .mi lines showing
the same info being correct).
If none of this helps, I think the next step would be to take it
to Autodesk, showing them the same info. Or bounce it off one of
the Maya groups that specialize in Maya + MentalRay rendering.
As far as working around the issue, you might need to hack a script
that massages the .mi file before passing it to mray standalone
to fix the bad lines.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|