Hm; there is no images path in the workspace file from that sample. I wonder if it's getting erased/overwritten? I'll try locking during the next render.
On Mar 28, 2011, at 10:43 AM, Michael Vaglienty wrote:
[posted to rush.general]
Hey Daniel,
I ran into a problem very similar to this a few months back. What fixed it
for me was making sure the paths in your workspace.mel in the maya project
folder look correct and then making it read-only. I noticed during some
renders some of the fields would disappear. Not sure if this a bug with Maya
or what.
Hope this helps.
Michael Vaglienty
Giantsteps VFX
> -----Original Message-----
> From: Daniel Browne [mailto:dbrowne@(email surpressed)]
> Sent: Friday, March 25, 2011 12:10 PM
> To: void@(email surpressed)
> Subject: Maya and MR Images Directory
>
> [posted to rush.general]
>
> Hi All,
>
> We're experiencing an odd phenomenon when rendering .mi files
> exported fro=
> m Maya2011 with MentalRay Standalone 3.8. Even though we have it
> explicitly=
> set to export absolute paths, often at least half the batches in the
> rende=
> r job will end up with their output path at the base of the project
> instead=
> of in the images sub directory as specified in the scene. Could this
> be a =
> result of having the Maya -proj parameter set during export?
>
> Thanks,
>
> -Dan
>
>
>
> ----------
> Dan "Doc" Browne
> System Administrator
> Evil Eye Pictures
>
> dbrowne@(email surpressed)
> Office: (415) 777-0666 x105
----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures
dbrowne@(email surpressed)
Office: (415) 777-0666 x105
|