DigitalDreamer opened this issue on Aug 26, 2008 · 7 posts
DigitalDreamer posted Tue, 26 August 2008 at 1:06 PM
When Poser is rendering for a long time, does the app claim to be 'not responding'? I've got used to it, and ignorte it, but I wonder how many renders have been interrupted, and maybe pz3's damaged, by people believing the message and closing Poser?
FrankT posted Tue, 26 August 2008 at 1:36 PM
Probably because Poser is too busy rendering to answer whatever things windows uses to check if an app is still running or has died
Daymond42 posted Tue, 26 August 2008 at 3:58 PM
I've found it responds quicker if you set the rendering as a separate process. Granted, task switching probably isn't too good of an idea when rendering, since you're using the computer to do things that could otherwise have been used for rendering... but yeah.. When not set as a separate process, Poser will not be visually changed as the foreground program until it renders its next "square", whereas if set as a separate process, it does so almost immediately.
Currently using Poser Pro 2012 (Display Units = feet)
AMD Phenom II 3.2ghz (6 cores)
8gb RAM
Windows 10 Pro 64bit
DigitalDreamer posted Wed, 27 August 2008 at 1:42 AM
That sounds interesting - how does one do that, Daymond?
Daymond42 posted Wed, 27 August 2008 at 8:20 AM
Go up to "Edit" and select "General Preferences". Then, click on the Render tab, and put a checkmark in the box marked "Separate Process".
There ya go. :>
Currently using Poser Pro 2012 (Display Units = feet)
AMD Phenom II 3.2ghz (6 cores)
8gb RAM
Windows 10 Pro 64bit
DigitalDreamer posted Wed, 27 August 2008 at 8:37 AM
ty, you sir are a gentleman!
Daymond42 posted Wed, 27 August 2008 at 8:44 AM
Oh, I try! :> Might be the first time I've doled out the help. I'm usually the one asking! :) Though.. as you can tell by my "joined" date and my post count, I'm more of a reader.. :)
Currently using Poser Pro 2012 (Display Units = feet)
AMD Phenom II 3.2ghz (6 cores)
8gb RAM
Windows 10 Pro 64bit