it's not necessarily unusual to get the "unresponsive" message if you're doing "heavier sims and/ or try to cache" It might also worsen if the file I/O is expensive, for example if you're writing to the network of a compress/encrypted drive. The UI is not running in a separate thread in XSI, so when it runs a sim it's taking breaks every once in a while to process messages (especially for the Cancel button on the progress bar), but those pauses can be too far in-between if each frame is heavy.
Windows's window manager is putting up that message for any application that stops processing windows messages for more than a couple of seconds. It doesn't mean the application is hung and needs to be killed. It just means it's hasn't redrawn its window and processed mouse messages for a while. On Wed, Apr 17, 2013 at 6:34 AM, Sebastian Kowalski <l...@sekow.com> wrote: > ive updated the gpu driver, lets see how softimage behaves today.. > cant really repro that, kinda random behavior. > its a brand new hp z820 i am working on. but i had this flaws for some time > now, on different machines. > > well get back at you > s. > > Am 17.04.2013 um 04:02 schrieb Chris Chia <chris.c...@autodesk.com>: > >> Hi Sebastian, >> Could you give us some info? Like any repro steps? And what's your machine >> specs? >> Also have you updated your graphics driver and cleared the XSI preference >> folder? >> >> >> Regards, >> Chris >> >> -----Original Message----- >> From: softimage-boun...@listproc.autodesk.com >> [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Sebastian >> Kowalski >> Sent: Tuesday, April 16, 2013 10:28 PM >> To: softimage@listproc.autodesk.com >> Subject: unresponsive under win7 >> >> it doesnt matter if I have aero switched on or not, soft is unresponive, >> switching to other apps in the background or freezing up when running some >> heavier (even when they are running only on one thread) sims and/ or try to >> cache. and sometimes its not even writing the caches. its not crashing, it >> is coming back at some point (end of framerange) is this something only my >> side, or is somebody experiencing the same? >> >> its so frustrating!
