Done with ICE
This case illustrates a common troubleshooting technique for some install/uninstall problems: deleting the Installer registry key.
Way back when I started support Softimage, this was how we fixed problems like “Uninstall says Softimage already uninstalled”, even though that was not true.
In a recent MotionBuilder case, the customer got this error when he tried to uninstall MotionBuilder 2011:
There was an error reading the registry key SOFTWARE\autodesk\motionbuilder\2011//defaultproductkey.
- In the Registry Editor, find this key:
- Search for MotionBuilder in the Data.
- You should find a DisplayName value under an InstallProperties key.
The full key name will be something like:
- Export the key (as a backup) and then delete it. For example, on machine, I would delete this key:
On your machine, the key name may be different than “83E7ADBE34330A442ACF348F731E5F87”
- Try again to uninstall MotionBuilder.
So the story we revealed at GDC was the notion of using Maya, a standard content creation tool and a known visual language, together with Softimage ICE-like visual programming technology to make the gameplay and game editing process interactive.
If you’re still having problems with disconnected shaders, even with HotFix2, you could try using dotXSI to remove any corrupt materials from your material library.
Here’s the basic procedure. You may want to create a temporary copy of your material library, and then use the explorer to copy all the materials into the temporary material library.
- Load the original asset (scene or model).
- In the explorer, switch to Materials scope, and click the icon for the material library.
- In the library PPG, change the storage to External (dotxsi text) and click Export Library.
- Save the scene.
- Close and restart Softimage.
- Open the scene.
- In the explorer, right-click the material library and click Locks > Unlock All Levels.
- In the material library PPG, change the storage back to Internal.
- Save or export the asset.
There is strange user interface lag that affects Softimage XSI when you use a Wacom tablet. With heavy scenes or simulation, you may never be able to stop playback. Other users have reported problems with the render region.The best work-around is to disable tablet support in Softimage any version. This will not affect any other program.
I had a bit of time yesterday, so I started playing with ICE procedural modeling and I managed to put together a rough prototype of an auto-fencer. Given a curve, I use ICE to build a fence by placing posts and rails. I’ve still got some problems with the rotations of the rail, but it’s a lot better than it was yesterday 😉
HotFix2 cannot fix render trees that are already broken. You’ll have to repair those materials after you remove the corruption.
Here’s how to recover a scene and remove the material corruption with HotFix2.
It is critical to restart Softimage during this procedure.
- Load the corrupted scene into Softimage 2011 (with HotFix2).
- Save the scene.
- Restart Softimage.
- Load the scene again.
- Now you can start repairing your materials.
The connections of corrupted materials are broken upon initial load, but corrupted shaders themselves still remain. After saving, restarting XSI.exe, and reloading the scene, corrupted shaders that are not salvageable have been removed and whatever shaders remain can be used to reconstruct materials.
From my colleague Manny, a tutorial on normal mapping with Ultimapper.