I’ve noticed that one comp don;t render but instead start and stop at:
0: STDOUT: # INFO : Rendering pass ‘Scene001_Shot006’…
0: STDOUT: # INFO : Rendering frame 70 (0.0% done)
0: STDOUT: # INFO : LINK 0.2 progr: module #3 (C:\Softimage\Softimage_2010_SP1_x64\Application\bin/nt-x86-64/sibase.dll) loaded
Then after trying anything I could remember I’ve reinstalled whole system … and got same problem again…
In the mean time I’ve bin using another comp that was rendering just fine all night long. And I’ve installed python there as well for submission script and then noticed that now that comp is not rendering in slave at all but same thing as the other one just stops there at the same part sibase.dll loaded.
Submission script works fine, but only difference is that I’ve installed python on that copm and then it stopped rendering as well.
Now even after de-installing python problem is still there.
Any idea??
That’s really strange that installing python would affect Softimage’s ability to render. If you do a google search for xsibatch hangs, you’ll see that this used to be a common problem in XSI 7.5, but I can’t find anything for 2010. Also, that hanging problem was a random thing, whereas this seems to hang at the same spot.
Here’s something to try. On the machine that this problem is occurring on, open a DOS prompt and run this command:
C:\Softimage\Softimage_2010_SP1_x64\Application\bin\xsibatch.bat -render "path\to\scene.scn" -verbose -frames 1
This will try to render frame 1 of the scene file you pass to it (just swap out the path to the scene as appropriate). Let us know if you run into the same problem with this test.
Cheers,
Just tested.
this is, after bunch of other informations what it says at the end:
Command failed, returned -2147467260
#FATAL: Render passes failed.
Running from SI directly renders fine. And it worked just before I installed python to have submission script.
Also I’ve tried adding -pass just to be sure and still nothing
Since the problem also occurs when rendering from the command line outside of Deadline, I think it’s safe to conclude that the problem isn’t related to Deadline. I wish we could help you out more, but we don’t have any experience with this particular problem. It might be best to contact Autodesk about the problem. Just make sure to mention that the problem occurs when rendering from the command line, otherwise I’m sure the first thing they would suspect would be Deadline (which we’ve already ruled out here).
Cheers,