I have a dual processor Athlon 1800 MP system, 512M mem, Win2K, all patches up to but not including SP3. 1. Run task manager and minimize to task bar 2. Start P5 3. Open the "object browser" (whatever) tray 4. Check CPU utilization 5. Close the tray 6. Check CPU utilization 7. Switch to the task manger 8. Check CPU utilization On my system with the tray open, one of the CPU's is up at 100%. Close the tray, utilization back to normal. Switch to another task, utilization back to normal. Doesn't seem right. Looks like some code is spinning in a loop while the tray is open. Thanks, Frederick C. Wilt

Yep, I see this happening on XPHome as well. Good thing to know: close the drawer when rendering.

Tried it on my Dual PIII system with Windows 2000, and got the same thing. Pretty wierd.

I have notice that as well. It only takes all the cpu usage when it not waiting for you. (ie, minimized and rendering) Here is my theory. Poser does that by design. It is waiting for you to move something or load something. It takes all the cpu time checking to see if you have moved something. It also has to continully update the screen with its very memory intensive graphic interface. It would take all the cpu usage for faster response time. That is my theory.

Windows is an event driven system and as such when an application is waiting for something to do, it should "go to sleep" until the Windows OS "tells" it that the user has done something of interest to the application (like clicked on a menu item) or that some other event of interest has occurred. The application then should "wake up" and deal with the event. If an application isn't doing anything "useful" such as responding to user input, printing, rendering, etc it shouldn't be spinning in a loop waiting to do something. This is not necessary under Windows and just wastes CPU time. Regards, Frederick C. Wilt

I feel that it should not do that. As an application developer, I feel that programs should be efficient in the use system resources. This means you need quality in design and production. However, quality takes time. In this business market, applications a extremely rushed to market and quality is tossed out the window, run over, burned to a crisp, thrown into a river, and the river is hurled into deep space. Poser should not take 100% cpu usage waiting for us, but it does. You will need to complain to Curious Labs for any change to the situation.

I suspect this is a by-product of the fancy user interface, and I seriously doubt they can do anything about it short of ditching the current user interface, and I doubt that will happen.