Luc-Eric mentioned python and messaging. We have not been able to isolate the problem as earlier this year we had a similar issue where certain commands in softimage would no longer function once a particular scene was opened. This only happens in 2013 SP1, not 7.5.
Example: We have a tool (custom property) which is a UI for animators to specify which frame range they want active for animating as each character is currently one giant timeline containing nearly 100K frames. The tool contains a listbox listing custom properties which contain the start/end frame values for each sequence they're animating. When they select a property in the listbox, the tool's PPG OnClicked() event is triggered which finds the selected custom property and sets the global timeline start/end to match those found in the custom property. What we experienced is when a particular scene is loaded, the timeline can no longer be set from inside the PPG OnClicked() event of the tool. The only fix is to restart softimage to clear the state. We were able to isolate it to a particular sequence of cut/paste actions performed in the FCurve editor to trigger the problem, but it wasn't fully reproducible on all computers. My computer, for example, could not reproduce the problem no matter how hard I tried. Renaming the user's softimage profile and having it regenerated on next startup seemed to clear up the issue, but only temporarily. We still haven't found the cause. Matt From: [email protected] [mailto:[email protected]] On Behalf Of Steven Caron Sent: Friday, November 22, 2013 12:22 PM To: [email protected] Subject: Re: Events/updates stop working 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]<mailto:[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.
