Thanks for the suggestions. Have managed to recover the scene with a copied scenetoc and some model name guesswork... Will make sure scenetocs are always recorded in the future! And scene toc manager is now part of the toolset.
Cheers! On 4 November 2014 11:20, Cristobal Infante <[email protected]> wrote: > Hi Matt, > > Use the Scene Toc Manager created by Alok, it's been a great time saver > here. > > Search for "ScnToc" in http://rray.de/xsi/ > > If the plugin doesn't work with your version of Softimage, you can always > use the standalone. > > > > On 4 November 2014 00:21, Matt Lind <[email protected]> wrote: > >> make sure you have all the required plugins and shaders installed or >> else you’ll get all sorts of problems like this. >> >> Next on the list of things to try is activate all levels of script >> logging and verbosity you can, and make sure to dump it out to a script log >> on your hard drive (.log). then load the scene. hopefully something will >> be dumped to the log you can work with such as an error or warning message >> indicating the problem. >> >> I would write a few simple event scripts to dump the model names and >> actions attempted as the scene is being loaded. You can use the >> information to incrementally build a new .scntoc file and offload the >> model(s) that give you problems. This, of course, would be iterative. >> >> To isolate the problem of being a graphics issue vs. a data integrity >> issue, try loading the scene using xsibatch.exe instead. If it doesn’t >> crash, you can save the scene to generate a .scntoc so you can offload your >> models when loading with xsi.exe. >> >> >> Matt >> >> >> >> >> >> >> > > -- www.matinai.com
