I tried the same file in Poser 12, and it's fine. Click "cancel," and the render cancels nearly instantly.

But with Poser 13, it just hangs. Task Manager shows CPU usage is high, but nothing seems to be happening. Maybe it would resolve eventually, but after several minutes, I killed Poser. Tried it again after rebooting, same results.

I am not seeing that on my system, it immediately stated it is cancelling and odes so after 10 seconds or so.  The only problem I am having is Poser going walk about with the CPU showing high usage but nothing appearing to be happening in Poser.  Problem often occurs if I have been working on a scene and then take the 'New' route from the file tab, if I shut down Poser and then load the same scene form scratch there are no issues.  It is almost as though Poser is not letting go of the old scene. 

randym77 posted at 5:12 PM Thu, 27 April 2023 - #2979035

I tried the same file in Poser 12, and it's fine. Click "cancel," and the render cancels nearly instantly.

But with Poser 13, it just hangs. Task Manager shows CPU usage is high, but nothing seems to be happening. Maybe it would resolve eventually, but after several minutes, I killed Poser. Tried it again after rebooting, same results.

Ive run into this too.  For test sake, next time it hangs, see what happens if you press Alt+F4  (make sure you saved your work before attempting, or try with a test scene).
See if instead of forcing Poser closed (as Alt+F4 normally would), see if it cancels render, freezes Poser for a few seconds, and then go back to normal.  If it does, now try to render with Superfly against and then also cancel it again once it starts.   Curious if we are getting the same results.

ShaneNewville posted at 10:14 PM Thu, 27 April 2023 - #4463618

randym77 posted at 5:12 PM Thu, 27 April 2023 - #2979035

I tried the same file in Poser 12, and it's fine. Click "cancel," and the render cancels nearly instantly.

But with Poser 13, it just hangs. Task Manager shows CPU usage is high, but nothing seems to be happening. Maybe it would resolve eventually, but after several minutes, I killed Poser. Tried it again after rebooting, same results.

Ive run into this too.  For test sake, next time it hangs, see what happens if you press Alt+F4  (make sure you saved your work before attempting, or try with a test scene).
See if instead of forcing Poser closed (as Alt+F4 normally would), see if it cancels render, freezes Poser for a few seconds, and then go back to normal.  If it does, now try to render with Superfly against and then also cancel it again once it starts.   Curious if we are getting the same results.

Yes, that's what happens! Though Poser freezes for more than a few seconds. Maybe a minute or so. But then it works fine. Superfly seems to render a lot faster afterwards, too.

The first time after Poser installs, or after you update some specific drivers on your computer, Poser needs to rebuild render kernels. This can take some minutes to do, and then it won't do that again unless something (installation/drivers) changes.

If you're rendering directly, Poser will say it's building render kernels in the progress bar of the render, but if you're rendering on background, nothing will warn you of this, it'll just build the kernels, and it might feel frozen or crash if you interrupt it. Could this be what's going on?

Could be. But what does it mean if I've shut down Poser using the task manager during the process? Does that mean the kernels aren't fully built or something?

randym77 posted at 11:56 AM Fri, 28 April 2023 - #4463661

Could be. But what does it mean if I've shut down Poser using the task manager during the process? Does that mean the kernels aren't fully built or something?

That's a bit above my knowledge - no idea, sorry xD

ShaneNewville posted at 10:14 PM Thu, 27 April 2023 - #4463618

randym77 posted at 5:12 PM Thu, 27 April 2023 - #2979035

I tried the same file in Poser 12, and it's fine. Click "cancel," and the render cancels nearly instantly.

But with Poser 13, it just hangs. Task Manager shows CPU usage is high, but nothing seems to be happening. Maybe it would resolve eventually, but after several minutes, I killed Poser. Tried it again after rebooting, same results.

Ive run into this too.  For test sake, next time it hangs, see what happens if you press Alt+F4  (make sure you saved your work before attempting, or try with a test scene).
See if instead of forcing Poser closed (as Alt+F4 normally would), see if it cancels render, freezes Poser for a few seconds, and then go back to normal.  If it does, now try to render with Superfly against and then also cancel it again once it starts.   Curious if we are getting the same results.

Quoting myself since Edit is not an option.  

I haven't run into this again since it first happened.  Ive been trying to replicate it but no luck so far. 

I suspect Ohki! is correct. It's building the kernels or whatever that takes so long.

I had it happen more than once, but it was probably because I killed it too soon.

Here's what I suspect:
- I installed Poser13 last April 7
- an update took place on April 12th, around 23h30

And if I take a look the the "gpu" folder, in the "Runtime" folder, but the one located where the executable lies, there are two binary files with the same date/hour of modification:

It's probably already managed in Poser, at a programming level but I suspect that these files are automatically rebuilt if they are missing or invalid.