With more time to study the problem comes more details. Scenes I create behave normally on all computers in the studio, but when I receive a certain set of scenes from others, the problem shows up. One of my office mates is affected the same way from those problem scenes. We both have Dell precision workstations but of different vintages. The person who created the problem scene has no issues whatsoever, nor does anybody else with his brand of computer/motherboard (alienware).
One of the scenes exhibiting the problem is quite simple - a character rig acting as a stand-in for enveloping armor/clothing pieces. No custom tools living in the scene other than the custom properties we've been using for years. Everything else is native softimage tools and data. All other scenes using the character rig do not exhibit the problem. Deleting my user profile (renaming, more like it) and letting Softimage auto-generate a new one seems to have cleared up the issue, but would like to know why this happens. Matt -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Luc-Eric Rousseau Sent: Friday, November 22, 2013 9:43 AM To: [email protected] Subject: Re: Events/updates stop working baffling. the only thing I could think of is if something is causing a messagebox to pop behind the softimage window, or some other plugin is doing custom UI (PyQT?) because it sounds like a message queue constipation problem. On Thu, Nov 21, 2013 at 10:34 PM, Matt Lind <[email protected]> wrote: > On Thu, Nov 21, 2013 at 6:46 PM, Matt Lind <[email protected]> wrote: > > We have an issue on select scene files where once they are loaded, > events (including PPG events) are no longer triggered, and any updates > to the viewports are one click behind. For example, pressing 'R' to > reset camera in a viewport doesn't take effect until you click somewhere in > the UI. > Once the problem is present, the only solution is to restart Softimage > as the problem persists the rest of the session. Most of our scenes > behave normally, but we're getting more and more with this particular problem. > > > > I seem to remember a similar problem occasionally happening in > Softimage > 2010 SP1. Anybody remember what caused the issue and the solution?
