Re: [Rendering/scripting] - camera override at render/save scene outside project directory

Date : Mon, 12 May 2008 16:09:22 -0400
To : XSI(at)Softimage.COM
From : Raffaele Scaduto-Mendola <raffaele(at)turbolinea.com>
Subject : Re: [Rendering/scripting] - camera override at render/save scene outside project directory
Hi Cornelius,

Yes, yes and yes.

1 - xsibatch -script will give you complete access to any XSI parameter through scripting. So you can basically start xsibatch, run your script to make sure everything is setup, and then as part of your script run a renderpass command + you get access to things like ActiveX Object component should you be tied to a sql database or need to do some FileSystem operations.
You should have full access to do so.


2 & 3, you can setup a publishing scheme where you can save out your scene outside the "provided" XSI/SoftImage directory structure. Unfortunately to run the save scene, you need to save it inside a xsi database. So what I do is create a localDataBase/user/system (so you have a backup in case hell breaks loose on your production), save your scene out and then copy your .scn (and .scntoc file) using the fileSystem Object to which ever location you might provide (through web browser or file directives).
Be aware, if you are using point baking, spring caching, etc... you will have to account for these extra files in your copy commands.


Cheers,
RSM.

Cornelius Porzig wrote:

Hi all,

I’m trying to write a render submission script for XSI which sends render jobs to Rush. At the moment I’m at a very early development stage and (python) scripting in XSI is new ground for me.

Currently I have basically 3 questions if my ideas can be achieved:

- Is it possible to override the camera XSI is using at batch-rendering? With a flag perhaps? Sometimes I have several cameras in one scene and I don’t want to create different render passes for all the cameras. I tried to change the camera in the SCNTOC-file, however it seems, that this file is not evaluated prior rendering. Or is duplicating the passes with a script, setting the camera, save the scene for rendering and then deleting the new passes the way to go?

- Can I save a scene for rendering as copy without messing with the current working scene? E.g.: When I submit a scene for rendering, my current scene is saved as copy at a different location under a new name while preserving the current active scene name. At the moment I store my current scene name in a variable, save the render-scene in different location and then recall my initial scene name and save once to have my old scene name at my old location back.

- Is it possible to save scenes outside the project directory with the help of scripting? Whenever I try this with a script, the file browser opens. Can this behavior be overridden or am I doing something wrong?

These are my questions for the moment and perhaps you can point me in the right direction. Thanks in advance for your input!

Kind regards,

Cornelius

------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG. Version: 7.5.524 / Virus Database: 269.23.16/1428 - Release Date: 5/12/2008 7:44 AM


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.