So sometimes when I'm creating, I run quite a few renders to check on my textures/mesh to see my progress. More often than not, I hit render, and Poser freezes some....then when it comes back, I hit cancel on the render about 20 times and it just doesn't take. So I end up waiting 10 minutes until it'll let me.

My quesiton is, has anyone discovered a keyboard shortcut to 'Cancel' a render? Is there a way to stop it without clicking cancel? Just seems it takes sooooo long =)

Thanks in advance

Jackie

i also want to know this.

Hehe, I figured there were others who have dealt with this too =)

I know this isn't the answer you're looking for, but, sometimes, the only thing that works for me is ALT-F4.  Which forces Poser to close.  :(

Oh yeah, LOL - well maybe I'll fool around with it and see if there's something I haven't discovered yet about the render/cancel. I'm too stubborn to give up with closing poser haha

Count me in on wanting to know this! I seriously don't like having to close poser when it hangs like that...'specially as I'm always forgetting to save my work...sigh

If I figure out anything, I'll let ya'll know.

Quote - Count me in on wanting to know this! I seriously don't like having to close poser when it hangs like that...'specially as I'm always forgetting to save my work...sigh

Me, too.  And it only screws up when I've done something that looks COMPLETELY awesome...and haven't saved.

There HAS to be something.....one would think....There's a keyboard shortcut to render, so i would imagine theres something to cancel a render

Quote -

Me, too.  And it only screws up when I've done something that looks COMPLETELY awesome...and haven't saved.

Yes! And after I've spent quite a bit of time on it as well...:(  I know I should do incremental saves, but when one is in the 'zone', that's a distraction! At least for me it is XD

Esc key works for me ;)  Hope it will for you

The ESC key works normally, but when Poser is completely frozen,
it doesn't work any better than the Cancel button.  There isn't a magic
unfreeze key! 

In Poser 5 the only way to cancel a render is CTRL ALT DEL and close Poser.  

In later versions IE: Poser 6, cancel does work. However, the time it takes to cancel depends on your bucket size.  Before the render will cancel, Poser will finish the current bucket that it's working on. If you have a high number for your bucket size, then Poser will continue to process that bucket amount until it's done, and then cancel the render.  If you have a smaller bucket size, the time to cancel the render will be less, but obviously the time to render the image will be longer.

That's true.  I usually render with a bucket size of 8.  I could probably go lower, but why?

Here's a little script that saves the current document then renders.
The script is very simple; the key to making it work is to substitute
the script for Ctrl-R so it's the first thing you hit.  (Thus forcing you
to autosave without thinking about it.)

The script:

import poser
poser.SaveDocument()
poser.Scene().Render()

The trick:

Save the script into the runtimepythonposerScriptsScriptsMenu folder,
under this exact name:

SaveAndRender###Ctrl+R.py

And then find the Poser.XRC file, back it up somewhere else,
and delete line 743, which assigns Ctrl-R to the usual render.
Line 743 looks like this:
        Ctrl+R

Note: the script will work in any version, but the hotkey assignment trick
only works in P7 SR3.  (I don't know if Pro is the same.)

If you tick 'Separate process' in your render Preferences, you can go into the Task Manager (Activity Monitor in OS X) and 'End Task' ('Force Quit') on the FFRender process without stopping Poser.

In Poser Pro, Render in Background also uses a separate process, whether or not you have the option ticked in Preferences.

Quote - Here's a little script that saves the current document then renders.
The script is very simple; the key to making it work is to substitute
the script for Ctrl-R so it's the first thing you hit.  (Thus forcing you
to autosave without thinking about it.)

The script:

import poser
poser.SaveDocument()
poser.Scene().Render()

The trick:

Save the script into the runtimepythonposerScriptsScriptsMenu folder,
under this exact name:

SaveAndRender###Ctrl+R.py

And then find the Poser.XRC file, back it up somewhere else,
and delete line 743, which assigns Ctrl-R to the usual render.
Line 743 looks like this:
        Ctrl+R

Thanks for that :)

I always do save my images before rendering, but a script that will save mouse clicks is always welcome.

Of that script above, do I just save up to "The Trick" or do I save all of it down to the "accel>" portion?

Acadia - the script is just those 3 lines.

On a Mac, the file is called PoserMac.xrc. It's in the main Runtime/ui folder.

It works fine in Poser Pro too.

Note that it only works for a saved document. If it's a new 'Untitled' document, it gives a script error.

Thanks for the script, ockham!  And thanks for the tip on saving the document first, IsaoShi; hopefully, I'll remember to save at least once from now on...LOL!

Cancelling a render seems to take a very long time . For test I use the area render .

Oh no! I followed the instructions exactly, but Poser will not open at all now! It gets to the splash screen and freezes. I tried reversing what I did, but it still doesn't work! What could I have done wrong?? :crying: :sad:

I had exactly the same problem a few days ago, MadameX, except it was after a render crash.

First of all, make sure that your original Poser.xrc file is named correctly (you saved the original version under another name, right?)

If that does not fix it, then try a re-install of the latest SR for your version of Poser. Just install it over the top of your current Poser program, and keep your current preferences. Nothing in your Poser Runtime will be deleted.

If you have Poser Pro, make sure to install the separate Queue Manager SR1 update as well.

Thank you for your reply.

But I uninstalled and reinstalled Poser, also reinstalling the SR3 as well. Unfortunately, it didn't work. It installed with my registration # and everything, just as if it hadn't been removed at all. When I opened it, it did the same thing. I'm devastated. I love my Poser. This is ver. 7, btw.

I don't know what to do! I have DAZ Studio, but can't get it to run on my new pc, for some reason. But Poser does...or did.

:crying:

An uninstall may not delete your preference files, which are stored in your user profile somewhere. There is information on the Smith Micro web site, somewhere under Support I think, about deleting your preference files (or renaming the folder). That might be worth a try.

Don't cry... it will be okay!

Thank you, I'll try to find that and see if it works. I really, really hope so! I still have ver. 5, but much prefer 7, especially since I spent money on it!

And I DID cry...lol. Posering is one of the joys of my life, and I'd be lost without it. :blink:

Well, I found out how to delete the preferences and all, but the location the instructions sent me to only had the Library prefs xml. I copied that to my desktop, just in case, and deleted it. Started Poser again, but no luck. It still will not open. I noticed that the windows dialogue box had a button for more details on this, so I opened it and copied what was there. But have no clue what is happening and not sure if anyone here would either, but here is what it had:

Problem signature:
  Problem Event Name:    BEX
  Application Name:    Poser.exe
  Application Version:    7.0.4.220
  Application Timestamp:    486c3039
  Fault Module Name:    StackHash_db6c
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Offset:    0012efc4
  Exception Code:    c000001e
  Exception Data:    badc0de1
  OS Version:    6.0.6001.2.1.0.768.3
  Locale ID:    1033
  Additional Information 1:    db6c
  Additional Information 2:    4e5d5dc6aabf76cc679d707f73217047
  Additional Information 3:    b51e
  Additional Information 4:    c3f4f21ff0efa95302412e4fece51da2