|
i think all this would be solved by the addition,
as Halfy suggests, of a browse-able absolute path button on each
pass
thus allowing us to choose the output ocation of
each pass individually if we need to
also ensuring firstborns are left
uneaten
;o)
----- Original Message -----
Sent: Wednesday, July 18, 2007 10:50
AM
Subject: Re: xsi 6 render options
I'm a little disturbed by this system. I like to point and
click, create folders and sub-folders, and see the actual output path
displayed in the render options.
With this system, it relies heavily on my
typing skills at the end of a long day and / or night, ie. what happens if I
miss out a [ or spell framebufer wrong, etc etc. *and* I can't see the actual
path I'm rendering to, as demonstrated by Sams example below.
In that
example, why are the frames going to c:\temp?
What if I have 1 pass
rendering stills to a network shared folder, 1 pass rendering a sequence
locally in Render_Pictures, and another rendering something else to another
location? This system doesn't allow for this situation, or maybe I'm missing
something.
Sam Cuttriss wrote:
pass
options: [pass]\[pass]_[framebuffer].[frame].exr
results in:
c:\temp\reflection\reflection_main.0001.exr
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
|
