All Softimage 2011 network licenses include five Batch

Posted on by
Reply

As of the 2011 release, there is no longer separate “Softimage” and “Softimage Advanced” products. There is just one “Softimage” product:

  • A network license of Softimage 2011 includes five Batch licenses.
  • A standalone licenses of Softimage 2011 does not include any Batch licenses.

So, for example, if you had a network license of Softimage 2010 under Subscription, then your Softimage 2011 network license now includes five Batch licenses.

Craft Animation Studio bundled with Softimage 2011

Posted on by
Reply

Craft Director Studio from Craft Animations is bundled with Softimage 2011 as a plug-in. You can install the plug-in from the Install Tools and Utilities section of the Softimage 2011 setup.

Craft Director Studio uses high-end artificial intelligence and autonomous control systems to streamline traditional animation processes, allowing you to spend more time on creating rather than on more tedious tasks.

Craft Director Studio includes:

• Craft Camera Tools: real-time camera control for immediate, professional-quality cinematic results.

• Craft Vehicle Tools: create the most realistic and accurate simulations for in-motion vehicles.

• Craft Accessory Tools: add the finishing touches to action-packed productions by simulating and animating props such as missiles, trailers, cog wheels, and other moving parts.

• Craft Freeware Tools: a free-to-use extended toolbox for Craft Director Studio allowing real-time recording, interaction, and depth orientation.

See beneath the fold for more details on which Craft tools are included.
Continue reading →

Not all numbers are exactly representable as floats

Posted on by
Reply

Representable numbers

The number of digits (or bits) of precision also limits the set of rational numbers that can be represented exactly. For example, the number 123456789 clearly cannot be exactly represented if only eight decimal digits of precision are available.

Inexactness

Floating-point arithmetic on digital computers is inherently inexact. The 24 bits (including the hidden bit) of mantissa in a 32-bit floating-point number represent approximately 7 significant decimal digits. Unlike the real number system, which is continuous, a floating-point system has gaps between each number. If a number is not exactly representable, then it must be approximated by one of the nearest representable values.

In Softimage, you can see the inexactness of floating point numbers with a floating point parameter on a PPG, or with the Scalar node in an ICE tree. In either case, try entering the value 123456789: you’ll end up with the value 123456792.

If you run this Python snippet in a script editor, you can try this out:

import win32com.client
from win32com.client import constants

xsi = Application

oCustomProperty = xsi.ActiveSceneRoot.AddProperty( "CustomProperty", False, "Test" )
oCustomProperty.AddParameter2("Int",constants.siInt4,0,None,None,0,None,constants.siClassifUnknown,constants.siPersistable + constants.siKeyable)
oCustomProperty.AddParameter2("Float",constants.siFloat,0,None,None,0,None,constants.siClassifUnknown,constants.siPersistable + constants.siKeyable)
oCustomProperty.AddParameter2("Double",constants.siDouble,0,None,None,0,None,constants.siClassifUnknown,constants.siPersistable + constants.siKeyable)

xsi.InspectObj( oCustomProperty )

xsi.SetValue("Test.Float", 123456789)
x = xsi.GetValue( "Test.Float" )

xsi.LogMessage( x )
# INFO : 123456792.0

Using Python for RV_Init callbacks of relational views

Posted on by
Reply

Want to use Python to implement an RV_Init callback in an .xsivw file? Here’s how:

<script language="Python"><![CDATA[
def RV_Init( in_rv ):
	Application.LogMessage( "RV_Init" )
	
	# COM programming ( in_rv is pointer to IUnknown ) 
	import pythoncom
	oRV = in_rv.QueryInterface( pythoncom.IID_IDispatch )
	
	import win32com.client.dynamic
	oRV = win32com.client.dynamic.Dispatch( oRV )
	
	Application.LogMessage( Application.Classname(oRV) )
	
	for i in range(0,oRV.Views.Count):
		oView = oRV.Views(i)
		Application.LogMessage( oView.Name + " " + oView.type 	)

]]></script>