Hey guys,
So it is sure it was not Species. I just referred to it because I have a species figure in my scene, and someone mentioned he had a rigged character causing the same issue. I do not really know what was the issue, it's impossible to backtrack, however a cool scene debugging lecture would come handy. As for this specific scene, I have installed MoveNormal addon yesterday, tried it, but the result was bad, so I removed the operator from the object. The saved scene was unloadable after this. Even when I removed the addon, and deleted everything that reminded me to have this addon, the scene was unloadable. It would be nice to do something to avoid such cases. A more proper scene load manager would be the best. How? I do not know...I have some basic ideas, for example list the used operators in the scntoc file? It would give some hint. About the stability and data loss, it's quite interesting thing. I have never ever met the issue our artist met, a scene after load has corrupted UVs. I'll collect those scenes and send for investigation. Cheers Szabolcs From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Eric Thivierge Sent: Friday, July 06, 2012 3:35 AM To: softimage@listproc.autodesk.com Subject: Re: WHATTA HELL??????? As an FYI, Species doesn't rely on any plugins except for the custom properties used for UIs so there shouldn't be any plugin issues related to it (that I know of). If you find something please let me know so I can track it down. -------------------------------------------- Eric Thivierge http://www.ethivierge.com On Fri, Jul 6, 2012 at 1:28 AM, Szabolcs Matefy <szabol...@crytek.com> wrote: Thanks for all the comments and help! I managed to find an older crashsave, and I recovered the scene from it. I had Species rig in the scene, but it was working just fine, yet it removed it. I also had installed Move Normal prior to the disaster, so I removed it also. The scene was not opening any on our computers. I tend to believe what our artists say, SI 2013 line is cursed...they returned to 2012 SAP, and I am the sole 2013 user... Cheers Szabolcs
