Steven I saw you mentioned it does not persist any data - BUT we have had some wierd stuff go down here, including scenes that completely lose render options. You could render a region, but try and render the scene either preview or proper and you get script errors all over the place. Also scenes that crash on the farm AND the batch crash on local machines first time, then if you just leave them they suddenly work fine.
There are greater forces at work here [tongue in cheek] S. _____________________________ Sandy Sutherland Technical Supervisor [email protected] _____________________________ ________________________________ From: [email protected] [[email protected]] on behalf of Steven Caron [[email protected]] Sent: 18 May 2012 08:02 To: [email protected] Subject: Re: Merging Scene Fixes qtSoftimage plugin error why? as i said, the plugin does not depend on any data persisted in a scene. if the example plugins run without issue then its not the plugin's fault but the gui/app they are trying to run. s On Thu, May 17, 2012 at 10:36 PM, Sandy Sutherland <[email protected]<mailto:[email protected]>> wrote: Maybe there is something in the scene data that Qt uses/needs? And that data is fubar in that scene at scene level. S. _____________________________ Sandy Sutherland Technical Supervisor [email protected]<mailto:[email protected]> _____________________________ ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Eric Turman [[email protected]<mailto:[email protected]>] Sent: 17 May 2012 22:07 To: [email protected]<mailto:[email protected]> Subject: Re: Merging Scene Fixes qtSoftimage plugin error why? Did this scenes happen to originate in an older version of Softimage where QuickTime wasn't supported by 64 bit? On Thu, May 17, 2012 at 1:40 PM, Jared Glass <[email protected]<mailto:[email protected]>> wrote: Hi Steven and Jo A few days back I had to open an animators scene to do some tests and for some reason the qtSoftimage plugin just wouldn't work at all. Xsi would load the scene and it would automatically report that COM Error: Out of present range. (0x-7ffdfff6) error. Luckily this doesn't happen too often anymore, but with this specific scene no matter how many times I closed and reopened it, not once did the plugin work. BUT...when I merged it into a new scene all of a sudden the plugin started working again, without any issues. This new merged scene I have opened and closed several times just to make sure this isn't random and so far the plugin has been absolutely fine. My question to you is do you have any idea as to why this could happen? And to the rest of the list; does anyone know what is stored in an xsi scene that gets lost when the scene is merged that could cause conflicts/errors? Thanks for all the help so far :) -- Kind Regards, Jared Glass<mailto:[email protected]> | Technical Lead Triggerfish Animation Studios<http://www.triggerfish.co.za> Zambezia Movie<http://www.zambeziamovie.com/> | Khumba Movie<http://www.triggerfish.co.za/khumba/> -- -=T=-
