Re: Crashing scene with "transform" title.

Date : Wed, 28 Dec 2005 08:59:09 -0500
To : <XSI(at)Softimage.COM>
From : "Wayne Williams" <w1343(at)comcast.net>
Subject : Re: Crashing scene with "transform" title.

CreatePrim "Sphere", "MeshSurface"

SetValue "sphere.Name", "transform"

CreateModel

Then render region. XSI croaked on me as well.

----- Original Message -----
From: peter_b
Sent: Wednesday, December 28, 2005 7:20 AM
Subject: Re: Crashing scene with "transform" title.

before assuming any such thing,
did you try to merge the scene into a new one?
or export the model as emdl, and import that into a new scene?
or with all else failing, export/import as .xsi?
 
Just to make sure (as it sounds very unlikely crashing XSI with an object's name)
I just tried a model with an implicit named "transform" in there,
and some geometry, and it works without a glitch, with render region.
 
You can allways send off the offending scene to support(at)softimage.com, Im sure they will take a close look at it.
 
 
----- Original Message -----
To: XSI
Sent: Wednesday, December 28, 2005 11:48 AM
Subject: Crashing scene with "transform" title.

Hello.
Strange thing happened not long ago with scene I working with , the my scene suddenly stopped to render in render region and XSI has fallen down with an error.
The scene becomes impossible to work with , cause it has fallen every time I've opened it and attempted to render it and then I have found strange thing in XSi with name "transform".
If I named an object or implicit by "transform" name and put it in a model and when try to render it by render region the scene has fallen down.
Seems like the "transform" name has conflict with something which crash any scene which contain any object with name "transform" in a model.
May be there are some other names which could crash a scene by their title ???


--
Best regards
Andrew Konkin

Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.