thank god we finally got to the bottom of this, it's been driving people nuts here!!!
a -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Blair Sent: 01 February 2013 14:50 To: [email protected] Subject: Re: Fcurve editor crashing soft Hi I can reproduce the freeze with either Arnold or V-Ray, so I'm logging an issue with Autodesk. Thanks Stephen Senior Support Engineer Solid Angle On 01/02/2013 5:10 AM, Sebastian Kowalski wrote: > AAANNNNDD, > seems to happen to vray to.. if somebody can confirm a similar behavior while using 3delight we can say it had something to with render support in xsi ;) > > > Am 01.02.2013 um 11:08 schrieb Sebastian Kowalski <[email protected]>: > >> hey chris, for now its sitoa 2.5.0 and softimage 2012. but i have that kind of glitches for a long time. >> >> sebastian >> >> Am 01.02.2013 um 02:42 schrieb Chris Chia <[email protected]>: >> >>> Sebastian, what version of XSI n Arnold are you using? >>> >>> >>> On 31 Jan, 2013, at 11:18 PM, "Sebastian Kowalski" <[email protected]<mailto:[email protected]>> wrote: >>> >>> yep, i am having this problems for a long time. for couple of soft releases. but i never could prove that with a proper repro scene. maybe now its the time to investigate (solids, soft devs?) >>> >>> sebastian >>> >>> Am 31.01.2013 um 16:06 schrieb Stephen Blair <[email protected]<mailto:[email protected]>>: >>> >>> Hi Matt >>> >>> I'm pretty sure I unloaded every plugin item except the renderer itself, and the freeze still happened. >>> So, it's either the renderer plugin, or the renderer integration framework in Softimage. >>> >>> Thanks >>> >>> Stephen >>> >>> >>> On 31/01/2013 9:42 AM, Matt Lowery wrote: >>> Spot on guys! Thanks! We are using an Arnold work group and disconnecting from it does solve this issue. ( amazing! The renderer would have been the last place I would have looked to fix this.) >>> >>> We're currently looking into the most effective work around for this little chest nut. Seems unloading the Arnold plugins from the work group is enough to set things straight. But does anyone know if it's a specific Arnold plug in that's causing this? Is it Arnold lights? Arnold renderer? Arnold shaders? Or do we need to unload them all? >>> >>> Thanks again. >>> m@ >>> >>> >>> On 31/01/2013 13:30, Stephen Blair wrote: >>> I have seen a case of this before. The entry of numeric values in the fcurve editor froze Softimage, but only when a certain renderer was installed. >>> >>> I had a repro scene from a customer, and the only way I could fix it was to freeze part of the op stack. >>> >>> On 31/01/2013 8:19 AM, Stephen Blair wrote: >>> What renderer are you using? >>> >>> On 31/01/2013 7:35 AM, Matt Lowery wrote: >>> Any attempt to enter a numeric value for anything in the editor freezes soft. >>> >>> >>> >>> >>> -- >>> >>> Matt Lowery >>> Senior 3D Artist >>> >>> [GLASSWORKS] >>> >>> 33/34 Great Pulteney Street >>> London W1F 9NP >>> T:+44 (0)20 74341182 >>> F:+44 (0)20 74341183 >>> http://www.glassworks.co.uk <http://www.glassworks.co.uk/> >>> http://www.glassworksamsterdam.nl <http://www.glassworksamsterdam.nl/> >>> http://www.glassworksbarcelona.com <http://www.glassworksbarcelona.com/> >>> >>> >>> Glassworks Terms and Conditions of Sale can be found at www.glassworks.co.uk<http://www.glassworks.co.uk/> >>> >>> (Company registered in England with number 04759979. Registered office 25 Harley Street, London, W1G 9BR. VAT registration number: 867290000) >>> >>> DISCLAIMER: This e-mail and attachments are strictly privileged, private and confidential and are intended solely for the stated recipient(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of the Company. If you are not the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If this transmission is received in error please kindly return it to the sender and delete this message from your system. >>> >>> >>> <winmail.dat> > ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2238 / Virus Database: 2639/5572 - Release Date: 01/31/13
