Hey there folks,

We're experiencing some dodgy issues with Softimage and external Python,
possibly the on pywin side. This morning we walked in to find all our
in-house shaders having spontaneously given up service, across different
and mutually unrelated workgroups and versions of Softimage. Whatever scene
we opened, all of our in-house would show up disconnected and glowing red
in the render tree.

I tracked down the problem to their shader definitions, where all commands
calling python constant values (deriving from* from win32com.client import
constants as c*) throw errors. In this case that means the likes of *
shaderDef.AddShaderFamily(c.siShaderFamilySurfaceMat)*. Softimage's own
plugins aren't immune either - in SI2013 CrowdFX_Plugin.py fails on load
when registering events such as *
in_reg.RegisterEvent("UpdateRigProxyHierarchy",C.siOnEndCommand)*.

Reinstalling Python has made no difference. Switching to the Python
installed with Softimage seems to fix the problem, but it doesn't really
explain why this is happening so out of the blue in the first place. Has
anyone seen this kind of behaviour before? We're using Python 2.7.3 and
Softimage 2013.

Thanks for any insight,

Nic


-- 
Technical Pretty Picture Making Person
Kettle <http://www.kettlestudio.co.uk/>

Reply via email to