Sun, Feb 16, 10:45 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 15 11:01 am)



Subject: Poser Crashed in the middle of a background render - Firefly still running...


monkeycloud ( ) posted Wed, 05 December 2012 at 2:56 PM · edited Thu, 30 January 2025 at 5:03 PM

So, I've had a background render running a while now... a day or so. So not too long. He he.

But Poser has decided to crash out, probably around 80% complete.

Firefly is still happily chugging away, presumably still working on that render.

Is there any way I could retrieve the render once Firefly finishes... if I leave it to do so???

Is the render being written out to a temp file somewhere... I'm guessing it is?

I'm on a Mac...

Many thanks for any help anyone can offer here ;-)

 


wimvdb ( ) posted Wed, 05 December 2012 at 3:34 PM

If you are lucky it will be in the Poser Background render cache or PoserFFRendercache - this in the temp folder of Poser. I do not think it will be in the "normal" rendercache, but you might check it out anyway

But be warned - if you start Poser, usually the temp caches are cleared, so it might be gone if you have started Poser already.

The files are in EXR format - So you need a program that can read these files (like Photoshop or a special HDR viewer)

No idea where the caches are located on the Mac

 

 


monkeycloud ( ) posted Wed, 05 December 2012 at 3:37 PM · edited Wed, 05 December 2012 at 3:39 PM

Using lsof command in terminal shows me the open files are in:

/users//Library/Caches/TemporaryItems/Poser Pro/9/

Theres an icache and a pcloud file in there, that look like they relate to my render, then there's some files in the "BackgroundRender" subfolder under that path...

...which are:

AUX_CAMERA indirectLightPrepass.objs
AUX_CAMERA indirectLightPrepass.xml
AUX_CAMERA subsurfacePrepass.objs
AUX_CAMERA subsurfacePrepass.xml
AUX_CAMERA.objs
AUX_CAMERA.xml

Then there's exr versions of my various textures in a "PoserTextureCache" subfolder.

But all these files look just like the object, texture and IDL, SSS, pre-pass data for my render...

I have restarted Poser already... so it has maybe been cleared :-(

Firefly is still running though...

But can't see a PoserFFRenderCache folder anywhere round there...


WandW ( ) posted Wed, 05 December 2012 at 3:41 PM

Irfanview (free) has a plugin for EXR files, but it may not open a partial...

http://www.irfanview.com/

----------------------------------------------------------------------------------------

The Wisdom of bagginsbill:

"Oh - the manual says that? I have never read the manual - this must be why."
“I could buy better software, but then I'd have to be an artist and what's the point of that?"
"The [R'osity Forum Search] 'Default' label should actually say 'Don't Find What I'm Looking For'".
bagginsbill's Free Stuff... https://web.archive.org/web/20201010171535/https://sites.google.com/site/bagginsbill/Home


wimvdb ( ) posted Wed, 05 December 2012 at 3:41 PM

The exr files are real image files. But in the chache they may well be image files of the different passes. I never looked at them

The posertexture cache files are not your render files, they are the textures your scene used to create the image.  Why EXR? Because now the same poser code can handle 32bit textures as well as the 8 and 16 bit ones.

 


monkeycloud ( ) posted Wed, 05 December 2012 at 3:47 PM

Running find command in terminal to see if there's a PoserFFRendercache folder anywhere else.

The Firefly process is still certainly running and busy, with all those files above open.


monkeycloud ( ) posted Wed, 05 December 2012 at 3:51 PM

Many thanks guys :-)

I can open exr in Photoshop, so that wouldn't be an issue... at least... if I can find an exr of the render.

Whereabouts are all the recent renders stored usually, under OS X... do you know?

Not sure it'd be in there anyway though, yet?

Still waiting on that find command completing... trawling the disk as I type this.


monkeycloud ( ) posted Wed, 05 December 2012 at 4:10 PM

Okay... found a .exr here:

/users//Library/Application Support/Poser Pro/9/RenderCache/

With filename:

2012-12- 3_23h 7m57s.exr

Looks like it is still being written to... last modified is 21:59 currently (it is now 22:10 here).

Guess I will just keep an eye on that file / leave it till the Firefly process terminates then.

Take a look then...

Fingers crossed ;-)


Miss Nancy ( ) posted Wed, 05 December 2012 at 4:24 PM

exr files also viewable in preview.app

those in rendercache, along with tmp files (only readable by poser AFAIK), are held for some time after render.  six in my rendercache;  last five appear to be blank, causing APS to freeze.



monkeycloud ( ) posted Wed, 05 December 2012 at 4:42 PM · edited Wed, 05 December 2012 at 4:43 PM

Hmmm... yeah cp'd that exr to desktop and Photoshop has just froze trying to open it.

It opens in preview.app

But it is just totally black...

Timestamp is still showing 21:59 on the original... guess I'll wait some more and see if the timestamp is updated.


monkeycloud ( ) posted Wed, 05 December 2012 at 4:52 PM · edited Wed, 05 December 2012 at 4:54 PM

Timestamp has now changed to 22:44 and the file size has grown a bit. Firefly is still running away, with plenty CPU and Memory utilization.

Well... reckon I will leave it overnight then.

Now - I think the thing is that I asked the D3D Firefly Render script to give me Shadow / Specular and Z-Depth layers, along with the render.

So I'm guessing that probably all this extra data is being compiled into that .exr format file.

I wonder, on that basis, if I will be able to open it?


Miss Nancy ( ) posted Wed, 05 December 2012 at 6:08 PM

I tried one with poser droid and d3d script.  when I hit "apply" in script and went back to poser to render, it was o.k., and saved 4 pngs to desktop.  however, exr file in rendercache was  only addition, nor did said exr file show any extra layers nor channels when opened in APS.



monkeycloud ( ) posted Thu, 06 December 2012 at 1:40 AM

Thanks Miss Nancy

Well, its still rendering... I will leave it to continue for now. Take a look once Firefly finishes...

...assuming it does ;-)


monkeycloud ( ) posted Thu, 06 December 2012 at 5:46 AM

Well, the file was still being written too at around 7am this morning (now 11:45 am here).

Will see if it is done this evening. He he. Then have a go at retrieving an image...


monkeycloud ( ) posted Thu, 06 December 2012 at 2:56 PM

Nope... it was goosed.

Bizarrely, whilst I could recover my render in some form, in the half of the render that continued after Poser crashed, all the figures are naked... missing their clothing. Weirdness.

Ray tracing seemed to have gone pear-shaped too though however.


CaptainMARC ( ) posted Thu, 06 December 2012 at 9:49 PM

Shame. I was following this and rooting for you.

Next time try the strange and wacky world of the Queue Manager, where Genesis does not exist, but at least a Poser crash is usually of little relevance.


monkeycloud ( ) posted Fri, 07 December 2012 at 3:22 AM · edited Fri, 07 December 2012 at 3:22 AM

Content Advisory! This message contains nudity

file_489228.jpg

Here's a reduced size version of what I got out.

Yeah, my issue is this render is really a proof of concept using Genesis, in a more content heavy scene...

So far, concept unproven... he he ;-)

Going for it again. This time I was going to try that tip you gave in another thread CaptainMARC... about halving that precalc value in the D3D renderer.

If it bombs again I'm going to give up on it for now.

Or else replace the Genesis figures with V4 or K4...

...althought I'm getting keen to concentrate on some other stuff now.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.