If you create a new object(not a null) and add it to the simulation, does moving it crash the scene?
Did the problem start after you saved and reloaded the scene? I'm wondering if its possible if something was left out of the save or didn't get reread properly. -- Joey Ponthieux LaRC Information Technology Enhanced Services (LITES) Mymic Technical Services NASA Langley Research Center __________________________________________________ Opinions stated here-in are strictly those of the author and do not represent the opinions of NASA or any other party. From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Paul Griswold Sent: Thursday, October 24, 2013 10:56 AM To: softimage@listproc.autodesk.com Subject: Re: I'd like to punch Softimage in the face today It seems to be related to physX. If I try to move a null, it's fine. But any object that is part of the simulation - whether or not simulation is active or not - crashes Softimage. Maybe it's an nVidia driver issue.. On Thu, Oct 24, 2013 at 10:44 AM, Simon Reeves <si...@simonreeves.com<mailto:si...@simonreeves.com>> wrote: bloody clients Simon Reeves London, UK si...@simonreeves.com<mailto:si...@simonreeves.com> www.simonreeves.com<http://www.simonreeves.com> On 24 October 2013 15:31, Paul Griswold <pgrisw...@fusiondigitalproductions.com<mailto:pgrisw...@fusiondigitalproductions.com>> wrote: Yep - running the script crashes Soft as well. The good news is, at least with this crash I was able to submit a crash report. If anyone on the dev team is here, it's: CER_86953364 On Thu, Oct 24, 2013 at 10:05 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] <j.ponthi...@nasa.gov<mailto:j.ponthi...@nasa.gov>> wrote: Do you get the same result if you move an object via command line or script editor? This will nudge the selected object by 1 unit in X from its current position: Application.Translate("", 1, 0, 0, "siRelative", "siGlobal", "siObj", "siXYZ", "", "", "siXYZ", "", "", "", "", "", "", 0, "") This will set the object to X=1,Y=0, Z=0: Application.Translate("", 1, 0, 0, "siAbsolute", "siGlobal", "siObj", "siXYZ", "", "", "siXYZ", "", "", "", "", "", "", 0, "") Testing it in this way will possibly tell you if the error is at the interface level or something much deeper such as the transformation matrix. -- Joey Ponthieux LaRC Information Technology Enhanced Services (LITES) Mymic Technical Services NASA Langley Research Center __________________________________________________ Opinions stated here-in are strictly those of the author and do not represent the opinions of NASA or any other party. From: softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com> [mailto:softimage-boun...@listproc.autodesk.com<mailto:softimage-boun...@listproc.autodesk.com>] On Behalf Of Paul Griswold Sent: Thursday, October 24, 2013 9:51 AM To: softimage@listproc.autodesk.com<mailto:softimage@listproc.autodesk.com> Subject: I'd like to punch Softimage in the face today I'm working under a tight deadline in 2014 SP2. Doing an animation that involves physX simulation, which I know virtually nothing about. Client has been loving everything so far, then we have the dreaded conference call when they have a list of "little tweaks", none of which are little. Today I come to the office at 5am, load my scene and start to try to make the tweaks. The moment I try to use translate, scale or rotate on anything in my scene - BAM, Softimage crashes. Reboot the machine - same thing. Run "runonce.bat" - same thing. Delete the Softimage 2014 SP2 folder from my User profile - same thing. Disable physX - same thing. Merge the scene into a new one.... same thing. WTF??? There's no crash dump, no attempt at recovery - just Autodesk Softimage 2014 has stopped working. The only option I can find is to go back to a version of the scene prior to physX being applied. Stuff like this makes me want to throw my system out the window & become Amish. -Paul
