Troubleshooting installation failures

Posted on by
Reply

When a Softimage (or any other Autodesk product) installation fails, you’ll have to check the install logs to see what went wrong. Typically the only error message you’ll see during the actual install will be too generic to be helpful (for example, Error 1603, which could mean almost anything).

The installation log files are found in your %TEMP% folder.

The main log file is Autodesk_Softimage_IF.log.
If the installation works, you’ll see something like this:

2010/5/4:16:41:15	blairs	MTL-EXAMPLE	=== Setup started on MTL-EXAMPLE by blairs ===
2010/5/4:16:42:17	blairs	MTL-EXAMPLE	Install	Microsoft Visual C++ 2005 Redistributable (x64)	Succeeded	
2010/5/4:16:42:23	blairs	MTL-EXAMPLE	Install	Microsoft Visual C++ 2008 SP1 Redistributable (x86)	Succeeded	
2010/5/4:16:42:30	blairs	MTL-EXAMPLE	Install	Microsoft Visual C++ 2008 SP1 Redistributable (x64)	Succeeded	
2010/5/4:16:44:10	blairs	MTL-EXAMPLE	Install	Autodesk Softimage 2011 Subscription Advantage Pack 64-bit	Succeeded	
2010/5/4:16:58:36	blairs	MTL-EXAMPLE	=== Setup ended ===

If the install failed, Autodesk_Softimage_IF.log tells you which component failed to install.
For each component, there will be a [much] more detailed log.

Depending on whether you installed 64-bit (x64) or 32-bit (x86) Softimage, you’ll see these log files for Softimage:

  • Autodesk_Softimage_x64_Install.log
  • Autodesk_Softimage_x86_Install.log

For the Visual C++ Redistributable, these are the log files to look for:

  • vcredist_x64.log
  • vcredist_x86.log
  • vcredist_x64_2005.log
  • vcredist_x86_2005.log

In these files, I generally look for the point where the install rollback started, and the look back up the file from there. Or I search for things like “error” or “result”.

Once you find the error, it’s off to google to see what you can find.

Learning movies play in the wrong language

Posted on by
Reply

A customer in Germany reported that he couldn’t play the Softimage learning movies (aka Essential Skills movies) from NetView, and that when he used Windows Explorer to open the movies, they were playing in Japanese. I had a similar problem on my own machine, where the Maya learning movies played in Japanese instead of English.

First, the links in the NetView learning movies page just “run” the files using the default program for .mov files. If nothing happens when you click a link, check the default program registered for the .mov file type. If you cannot get the links to work, you can find the movies in the folder %XSI_HOME%\Data\NetView_Database\Movies.

The movie files contain multiple audio tracks. Here’s a video that shows how to change to the English audio track:

ERROR : 2004 – Invalid pointer – [line 2]

Posted on by
Reply

When you render with xsibatch, you get this error even though the frame does render successfully.

ERROR : 2004 – Invalid pointer – [line 2]

For example:

COMMAND: -render "C:\Users\blairs\Documents\Support\Project\Scenes\Sphere.scn" -
frames 2-4
>Loading: C:\Users\blairs\Documents\Support\Project\Scenes\Sphere.scn...
' ERROR : 2004 - Invalid pointer - [line 2]
' INFO : 4034 - Loaded scene was created with build number: 9.5.184.0 - compatibility version: 900
' ERROR : 2004 - Invalid pointer - [line 2]
OpenScene "C:\Users\blairs\Documents\Support\Project\Scenes\Sphere.scn", False,True
' INFO : Rendering all passes: Passes.Default_Pass
' INFO : Rendering frames '2-4'
' INFO : Rendering pass 'Default_Pass'...
' INFO : Rendering frame 2 (0.0% done)
' INFO : Rendering frame 3 (33.3% done)
RenderPasses "Passes.Default_Pass", , , , siRenderVerbosityDefault

If you running xsibatch from a render manager, this error may cause the render manager to quit the render job.

You can workaround this by renaming the ICEFlow plugin (Application\Plugins\ICEFlow.dll). This plugin manages the transfer of data between Softimage and Maya (the one-click ICE workflow).

Object model methods for finding objects

Posted on by
1

The Softimage 2011 Subscription Advantage Pack includes new methods for finding objects.

These FindObjects methods are more efficient than X3DObject.FindChildren, because the FindObjects methods don’t go through the scene hierarchy (they go directly to an internal database of objects).

Model.FindObjects( siClassID )
Finds all objects under the model that match a specified class ID (for example, all shaders or all ICE Trees). For example:

 # Enumerate all shaders under the scene root.
 from win32com.client import constants as c
 shaders = Application.ActiveSceneRoot.FindObjects( c.siShaderID )
 for s in shaders:
 	LogMessage( s.ProgID )
 # INFO : Softimage.soft_light.1.0

Supported siClassIDs:
siCameraID | siClusterID | siClusterPropertyID | siConstraintID | siCustomOperatorID | siCustomPropertyID | siEnvelopeID | siEnvelopeWeightID | siExpressionID | siGeometryID | siGroupID | siICETreeID | siLightID | siMaterialID | siModelID | siNullID | siNurbsSurfaceMeshID | siNurbsCurveListID | siOperatorID | siPolygonMeshID | siPropertyID | siShaderID | siShapeKeyID | siX3DObjectID

Application.FindObjects( siClassID )
Finds all objects that match a specified class ID. For example:

from win32com.client import constants as c
oICETrees = Application.ActiveSceneRoot.FindObjects( c.siICETreeID )
for x in oICETrees:
 	LogMessage( x.Nodes.Count )

Supported siClassIDs:
siCameraID | siClusterID | siClusterPropertyID | siConstraintID | siCustomOperatorID | siCustomPropertyID | siEnvelopeID | siEnvelopeWeightID | siExpressionID | siGeometryID | siGroupID | siICETreeID | siImageClipID | siLayerID | siLightID | siMaterialID | siModelID | siNullID | siNurbsSurfaceMeshID | siNurbsCurveListID | siOperatorID | siPassID | siPolygonMeshID | siPropertyID | siShaderID | siShapeKeyID | siX3DObjectID

Model.FindObjectsFomCLSID( sCLSID )
Finds all objects that match a specified CLSID. You can determine the CLSID of an object using XSIUtils.DataRepository () or by inspecting Softimage objects with the SDK Explorer.

# Enumerate all visibility properties under the scene root.
 props = Application.ActiveSceneRoot.FindObjectsFromCLSID( "{11EBE301-A20C-11D0-8478-00A024C7919C}" )
 for vis in props:
 	LogMessage( vis.FullName )
 # INFO : Camera_Root.visibility
 # INFO : Views.ViewC.SpotCamera.visibility
 # INFO : Camera.visibility
 # INFO : Views.ViewB.SpotCamera.visibility
 # INFO : Camera_Interest.visibility
 # INFO : Views.ViewD.SpotCamera.visibility
 # INFO : Views.ViewA.SpotCamera.visibility
 # INFO : light.visibility

C++ versions: