Finding all Store in Channel shaders

Posted on by
Reply 

// Get all shaders
var x = FindObjects(null, "{6495C5C1-FD18-474E-9703-AEA66631F7A7}" );
LogMessage( x.Count );
var oShaderCollection = new ActiveXObject( "XSI.Collection" );

// Build up a collection of all Store in Channel shaders
oEnum = new Enumerator( x ) ;
for (;!oEnum.atEnd();oEnum.moveNext() )
{
	var oShader = oEnum.item() ;
	try {
		//LogMessage( oShader.ProgID );
		if ( oShader.ProgID.indexOf( "_storeinchannel" ) > 0 )
		{
			oShaderCollection.Add( oShader );
		}

	}
	catch(e)
	{
		LogMessage(e.message);
	}
}


LogMessage( oShaderCollection.Count );

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.

JALSR: Just another licensing service request

Posted on by
Reply

Phone call from a customer who upgraded to Windows 7 and now gets “no interactive network license”.

  1. Ask whether license manager was reinstalled, and whether the license was installed. Yes.
  2. This is Softimage 2010 on Windows 7, so edit setenv.bat and change _ADSK_LicServers to @127.0.0.1 (Softimage 2011 automatically falls back on 127.0.0.1, so for 2011 I wouldn’t have to bother with this).
  3. Still can’t start Softimage. Disable firewall to quickly test whether ports are being blocked (telnet not installed on Windows 7 by default, so it’s quicker to just disable the firewall temporarily).
  4. Still cannot start, but it doesn’t appear to be a network connectivity issue. So check SoftimageLicense.log: it says “cannot connect to server”. So, server is probably not running.
  5. Start LMTOOLS and do a Perform Status Enquiry. Yup, server not running.
  6. Start Server, click Perform Status Enquiry to double-check
  7. Start Softimage. It works!
  8. Check that Start Server at Power Up is enabled. It’s not. Neither is “Run as Service”. Very strange. The server shouldn’t have started!!! Oh well. Select both check boxes.
  9. All done, except for the paperwork (case notes, final email, …)

ICE: Looping over group members and setting data

Posted on by
Reply

You can get data from the members of a group, and even loop over that data, but you cannot set data on individual group members. I’ve seen this question come up on several forums, mailing lists, and beta lists. You can’t store a reference in an attribute (so you can get it later and plug it into Set Data). You can store a string (eg the object name) in a string, but you cannot convert a string into a reference. And you can’t plug your Get Group into a Set Data.

Things like references and execute ports are part of the pre-evaluation stage. They must be resolved before the ICE tree is evaluated. Everything else in the ICE tree is the stuff that has to be constantly re-evaluated. So driving a reference port with another ICE node doesn’t really fit into the way ICE was designed to work.

For something like (resolving connections), you’re better off using a script to set up your ICE trees.

PS – Looping itself doesn’t seem that hard to figure out.

Lagoa & the Autodesk Subscription Advantage Pack for Softimage 2011

Posted on by
5

I see that Mark Schoennagel has let the cat out of the bag about Lagoa and the upcoming Advantage Pack release.

So, what’s an Advantage Pack ? It’s basically a collection of product enhancements and new features (like Lagoa) that are available exclusively to Subscription customers. The idea is to increase the [perceived] value of Subscription to customers.

There’s more to the Advantage Pack than Lagoa, but [unlike Mark] I can’t pre-announce stuff 😉 I’ve got to wait for the official announcements.

Softimage, Lagoa, premium Suites, and Autodesk marketing

Posted on by
8

The announcement of the new Max and Maya premium suites (which include Softimage and Lagoa) together with the relatively low profile of Softimage in the Autodesk marketing materials have caused a bit of a stir in the community.

Chinny (the Softimage product manager) posted this message to address the community’s concerns:

From: softimage-bounces@listproc.autodesk.com [mailto:softimage-bounces@listproc.autodesk.com] On Behalf Of Jason Brynford-Jones
Sent: Tuesday, July 27, 2010 11:13 AM
To: softimage@listproc.autodesk.com
Subject: A Softimage message

I thought the last time I wrote something like this, would be the last time.

I am beginning to sound like a broken record; a record no-one obviously likes listening to. So perhaps this really is the last time I will play this message as it seems to make no difference.

Marketing
It seems now the Softimage community is only focusing on Autodesk’s marketing as the barometer for Soft’s future. Not “no marketing” but “less marketing” than 3ds Max and Maya. Or that the new Max and Maya products WITH Softimage means no more Softimage? This does not make sense.

New Max and Maya Suites
From all our interviews Max and Maya customers want Softimage (not just ICE, but ICE is often a big reason) in their toolsets. At an affordable price, that interops well. OK let’s give it to them, in the way they want it.

There are many more Max and Maya customers than Softimage. Having product suites branded with the name 3ds Max or Maya are obviously targeted at selling to them. This represents a massive potential for Softimage. You might not agree with the naming, but you can’t argue the logic.

Softimage as a standalone product is of course continuing as before (with some very exciting stuff in the works) and having the standalone product available to all Max and Maya users is a huge endorsement of Softimage and commitment by Autodesk..

Development
Since the acquisition there has been repeated fear-mongering about Soft’s future. Even though in that time, we have had two major releases (3 in the last two years) and one minor (check what others have done in this time) and of course there is more to come.

Even though we have exceeded revenue expectations, even though we are expanding our development. Even though fundamentally NOTHING HAS CHANGED, people choose to focus simply on a lack of marketing and not Autodesk Softimage’s track record.

We still manage our own roadmap, with the exception of working well with other Autodesk apps. Something everyone has asked for repeatedly, especially ICE interop.

Our philosophy will continue around ICE as the architecture on which to build – that includes one day moving into modeling. We have not abandoned other parts of the Software (see the list at the end of this mail) far from it – we have a very well defined focus and future.

Final thoughts – for this is the last time I will do this.

If you take one thing away from this mail, it is this.

The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click
The future of Softimage is bright… click

It really is…

Chinny

Continue reading →

Softimage 2011 always falls back to 127.0.0.1 for network licensing

Posted on by
Reply

I’d forgotten about this until the other day when I tried to break my licensing for testing purposes.

I spent 20 minutes trying to get Softimage 2011 to not start! No matter what I did it kept starting up, and to make matters worse, my ProductInformation.pit file has some minor corruption that crashes Softimage when I try to use Help > About Softimage > Product License Information. So I couldn’t check where Softimage was getting its license.

I eventually resorted to using Process Monitor to watch the HKEY_CURRENT_USER\Software\FLEXlm License Manager\ADSKFLEX_LICENSE_FILE registry value, and I saw that xsi.exe was sticking 127.0.0.1 into the registry every time I started Softimage. So all I had to do was stop my local license server.