well.. I feel your pain :) Why "workaround" now is
1.) Rush Script (with gui) that does the MI generation
2.) Rush Script (with gui) that submits the mi files
With Maya we have those two baked into each other. And we will have
that for XSI too once we can get hold of a programmer that can make
the proper adjustments to our pipeline.
It's been interesting though, I learned a lot so far from batching out
stuff and what XSI is doing in the background. What is interesting
though is that XSI exports the same scene as Maya but to a fraction of
the time. Niiiiiiiiiiiice....
To be continued.
/stefan
On 10/2/07, todd akita <takita(at)earthlink.net> wrote:
> Stefan Andersson wrote:
> > I'm getting close to it now though :) I'm trying to adjust one of our
> > Rush scripts to do a export and then render.
> >
> > So far it's exporting! hehe...
> You're trying to chain jobs doing the -dependson flag?
>
> The way I was submitting Rush jobs before was something like this: XSI
> writes the job to text, then spawns a windows shell and passes the
> textfile as an argument to a "Rush -submit". Unfortunately all the
> examples they have are cshell, and we're on windows (I'm not great at
> windows shell scripting either) so I kind of let that one slide.
> Granted I probably could have rethought how I was doing it (and I'll
> probably have to if I want to chain those jobs) but for now it's on the
> "to do" list.
>
> -T
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi
>
--
__________________________________________
Pixel Abuser (at) http://www.swiss.se/
Blog (at) http://sanders3d.blogspot.com/
Web (at) http://sanders3d.googlepages.com/
work e.mail: stefan [at] swiss.se
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
