Our licenses expired last November and we had to get replacements. Upon doing so some of our batch scripts no longer functioned. Apparently something has changed with licensing. We had to revise all our scripts by appending "-processing" as an argument to xsibatch.exe before anything would work again.
Try that. Matt From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, April 22, 2013 4:39 PM To: [email protected] Subject: Re: Wots changed w/ cmd and/or bat rendering.. Yes, I have it working as before with a call to setenv.bat (thanks to Dan Yarguci), on all my other computers and a few remote servers, it is just my main "do it here" computer w/ various vanilla installs of 2011, 2012, 2013 that fails. I have checked all the setenv.bats and related w/ User Tools and also checked my paths and env vars.., nothing yet however. I also re-registered jscript.dll and vbscript.dll, ran runonce.bat, and all the Stupid User Tricks I know from way back to Softimage 2 or 3.. My last hope will be to un-install the XSI's, and the Python, and etc, start fresh and see when it fails. No big deal at present, but it bugs me. -Robert On 4/22/2013 9:46 AM, Pete Edmunds wrote: This works fine for me xsibatch -r -scene "path_to_scene_with_backslashes\*.scn" -pass "pass_name" -startframe 1 -endframe 100 -step 1 On 19 April 2013 22:42, Stephen Blair <[email protected]<mailto:[email protected]>> wrote: Hi Why don't you use xsibatch instead of xsi?
