Don’t do anything that interacts with a GUI.   That’ll crash XSIBatch as 
XSIBatch is essentially XSI.exe without any GUI, or support for a GUI.

How are you getting information from your custom properties?  That might be a 
factor.


Matt



From: [email protected] 
[mailto:[email protected]] On Behalf Of Jules Stevenson
Sent: Wednesday, June 11, 2014 11:40 AM
To: [email protected]
Subject: Python: Limitations / Differences in xsibatch versus interactive

Hey Gang,

We have a few custom properties and events which refuse to behave themselves in 
batch, are there any common gotchas / workflows / things to avoid when using 
XSIbatch.

Infuriatingly, all the logging I've been doing seems to suggest things are 
running just fine, but then the script still fails (specifically I'm pulling a 
value from a custom property and using this to change some parameters on a 
custom lens shader).

Any thoughts / help much appreciated.

Jules

Reply via email to