Category Archives: Known Issues

Copy error when creating a network deployment

Posted on by
Reply

Before you create a network deployment, create an empty toxik folder in the source folder where the you extracted the contents of the downloaded .exe. Otherwise you’ll get this error, even if you clear the MatchMover and Composite checkboxes:

---------------------------
Autodesk Softimage 2011 Subscription Advantage Pack
---------------------------
The copy functions cannot be used.

Failed to copy the following files:

    C:\Autodesk\Softimage_2011_Subscription_Advantage_Pack_English_Japanese_64bit\toxik	
to
    \\EXAMPLE\Deployments\SAP\AdminImage	

---------------------------
OK   
---------------------------

MatchMover FBX export doesn’t work

Posted on by
Reply

When you try to import an FBX file into Softimage 2011 Subscription Advantage Pack (SAP) from MatchMover, you get an error:

The following error(s) occured while attempting to read the FBX file:
-Corrupted or invalid file.

That’s because MatchMover exports a REALVIZ XML file instead of actual FBX.

Try using the Softimage VB Script export instead. That gives you a VBScript you can run in Softimage 2011 SAP to set up the exported tracking data.

Crash when you open the render tree or Material Manager

Posted on by
2

Some users have reported crashes when they open the render tree or Material Manager. For some users, this happens after a period of extended usage; for others, it appears to be scene- or geometry-specific.

I’ve had users send me scenes with geometry that appeared to crash the render tree and Material Manager, but when I tried on my machine, everything worked fine. So, it’s a bit of a mystery.

There is a workaround however: open the render tree and Material Manager before you load your scene. After that, you can work normally.

You could use an OnStartup event to automatically open those views when Softimage starts. I believe you could just open and close them at startup, and then everything will be ok afterwards.

VBScript compilation errors with Python PPG logic

Posted on by
3

On a machine that has Softimage 2011 or 2011 SP1 installed, but not Python, you’ll get VBScript compilation errors when you run a script or plugin that uses Python for the PPGLayout.Logic of a dynamic (on-the-fly) property. For example, running this script

xsi = Application
oRoot = xsi.ActiveSceneRoot
oProp = oRoot.AddProperty("CustomProperty", False, "test")
oLayout = oProp.PPGLayout
oLayout.Language = "Python"
oLayout.Logic ="""
Application.LogMessage('Hello world')
"""
xsi.InspectObj( oProp )

will give this VBScript syntax error:

# ERROR : Syntax error - [line 2]
# ERROR : Property Page Script Logic Error (Microsoft VBScript compilation error)
# ERROR :    [1] (null)
# ERROR :   >[2] Application.LogMessage('Hello world')
# ERROR :    [3] (null)
# ERROR : 	Syntax error

This happens because Softimage 2011 doesn’t detect the Python installed with Softimage, so it falls back to the default VBScript when it tries to execute the Python PPG.Logic code. However, Python works as usual in all other respects (note that the above errors are logged as Python comments!).

You can workaround this by setting PPGLayout.Language to “pythonscript”.

Or you could leave the Language set to “Python” and add these registry entries to your system.
This way you don’t have to update existing code.

[HKEY_CLASSES_ROOT\Python]
@="Python ActiveX Scripting Engine"

[HKEY_CLASSES_ROOT\Python\CLSID]
@="{DF630910-1C1D-11d0-AE36-8C0F5E000000}"

[HKEY_CLASSES_ROOT\Python\CurVer]
@="Python.AXScript.2"
[HKEY_CLASSES_ROOT\Python\OLEScript]

To add the registry entries, save the above in a .reg file and then double-click it.

Ambient Occlusion number of samples

Posted on by
1

If the Number of samples is set to 0 for the XSIAmbientOcclusion shader, Softimage 2010 memory usage will go through the roof as soon as Softimage has to render. This didn’t happen in 7.5, so it’s easy to load up an existing scene, open the Material Manager or Render Tree, and then see Softimage hang up while rendering a shaderball. That’s how this issue was originally discovered.

On a related note, here’s a JScript snippet that shows how to find all the XSIAmbientOcclusion shaders and check the samples values. 

// XSIAmbientOcclusion Class ID
var sClassID = "{FF66A9F8-BB42-480D-834D-BC5FC6E3AD23}"
var oColl = FindObjects( null, sClassID ) ;

oEnum = new Enumerator( oColl ) ;
for (;!oEnum.atEnd();oEnum.moveNext() )
{
	var oAOShader = oEnum.item() ;
	LogMessage( oAOShader.Parameters("samples").Value );
//	LogMessage( oAOShader.samples.Value );
}