yep, i am aware there is no ICE or python in your pipeline... i just know we had issues were someone complained about these weird issues, only they got. then in desperation they renamedd their user profile and it worked. i dug into that profile and found many debugging options were on. i restored their profile and then adjusted the preference and all was well.
i would divide and conquer, load that profile back up along with the scene... slowly removing parts of the profile and reloading softimage/scene until the problem is gone again. On Fri, Nov 22, 2013 at 12:16 PM, Matt Lind <[email protected]>wrote: > No. I wasn’t in debug mode as this problem only occurred on select > scenes. We do not use ICE or Python either. > > > > Most scenes open and function as expected, but we have a small number of > scenes that contain something that causes events to stop functioning when > they’re opened and the problem persists until you restart softimage. > > > > Since the problem disappeared by deleting my softimage user profile, it > seems to be related to a plugin cache or whatever it is softimage maintains > in that regard. Either the cache was corrupt, or the presence of a certain > type of data/scenario in the scene triggers a certain logic which doesn’t > work so well with that cached data. > > > > >
