Setting the default browser for online help



On Windows, Softimage uses the default Web browser to display help.
On Linux, the default is Mozilla, and if that is not available, then Firefox.

You can use the SI_HELP_PROGRAM_ENV environment variable to override the default help browser.

If the folder containing the executable program is not in your system PATH environment variable, you must include the full path to the executable in this variable.

Diagnosing startup crashes: testing xsibatch


When you’ve done all the usual startup troubleshooting (running runonce.bat, resetting your preferences, and testing the display driver), but you still crash, it’s a good idea to test whether xsibatch can run. Sometimes this will give us a different error message, or another clue as to what’s going wrong.

  1. Open a Softimage command prompt
  2. In the command prompt, run these commands:
  3. echo LogMessage "Hello" > %TEMP%\test.vbs
    xsibatch -processing -script %TEMP%\test.vbs
    
  4. You should see something like this:
    =======================================================
     Autodesk Softimage 10.0.422.0
    =======================================================
    
    License information: using [Processing]
    COMMAND: -processing -script C:\Users\blairs\AppData\Local\Temp\test.vbs
    ' INFO : Hello
    

ShaderOp.com | Using wxPython with Autodesk Softimage


Using wxPython with Autodesk Softimage

“Here’s the issue as far as I understand it: On Windows operating systems, every process that has a window (i.e. any none-console application) also has a message loop, and each process can only have one message loop. The problem with PyQT and wxPython is that they will try to create their own message loops inside the Softimage process, which somehow leads to the whole process shutting down. I don’t know Linux that well, but the same issue should arise there.

It turns out that the solution to this is to run wxPython or PyQT on their own separate threads, so that both message loops will run in isolation from each other.

Apparently Houdini 9.5 had the same thing happening with PyQT, and its documentation contains a code sample that addresses this issue. All I had to do was repackage it inside a Softimage plug-in, although I used wxPython instead of PyQT because I’m more familiar with it. But it should be trivial to change the code to use PyQT instead.”

–ShaderOp

Softimage 2012 Info


Here’s some hopefully helpful links:

2012 Service Packs

2011 Service Packs: