|
Hey Kim,
I was thinking that xsicab needed to access
a crashed scene that was recovered to gain access to the data that
crashed XSI in its prior session. If this isn't how it works, what's
actually going on behind the scenes to get this data. Also, what are the
exact steps that should be taken to use xsicab whenever a crash/disappearing act
occurs?
----- Original Message -----
Sent: Monday, October 31, 2005 5:49
PM
Subject: RE: How to deal with
unrepro'able bugs
use xsicab.
Wayne Williams wrote:
Im having some stability issues with XSI 5 insofar as modeling is
concerned. The problem is, I can't repro the steps that make it crash. It
doesn't actually even crash, it just disappears. These are basic tasks
like double clicking the geo. approx. in the selection drop
down.....poof...gone. Sometimes it will be while doing a modeling
operation like bevel....poof...gone. Using the new tweak tool and middle
click moving an edge loop...poof...gone. XSI doesn't show in the task
manager after the crash and when i reopen the scene it doesnt ask me to
recover. I go and do the exact same step as the last one that killed it
and then it works....only to crash a while later doing something
different. How does one go about getting a repro'able scene
to Soft to have a look at when this occurs. This has happened on a
box with certified hardware/os/drivers along with a box running
uncertified hardware/drivers. Win32bit and XSI32bit. Any suggestions
would be greatly appreciated.
-wayne-
I can only relay a similar experience
where XSI crashed repeatedly while in the fcurve editor, no warning, so
hanging, just gone. I ended up deleting the preferences file on a
colleague's recommendation and it's been fine since. There was a theory that
the preferences and our custom coding didn't mix.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
|
