All of a sudden all my Poser 13 renders come out black; it started yesterday. It shows progressive rendering fine and when I either stop the render or finish, the window turns to complete black.

I checked error messages; this is the latest one:

Above error was for OptiX. here is what I get as anerror with GPU:

Have you tried to reboot the PC? (not turn off/on: restart)

The GTX 970 does work. I have 2 of them. It's possible there's something in that scene it doesn't like. First try rendering one of the included scene. That will eliminate some kind of hardware issue.

If a simple scene renders but not the scene you're having problems with it could be there's a material setup in that scene that's making the GPU unhappy. If this is the case we'd like to get that scene in the support system so we can track down the exact issue.

If it's just the one scene, go to https://support.posersoftware.com/ and create a support ticket. Use Poser 13's scene export (File > Export > Save for sharing ... ) that will create a scene complete zip file that can be attached to the ticket. If it's too big to attach we can provide an upload link for your scene. We can use that ti try and isolate the problem.

Well, one of the included Bedroom scenes renders *grey* with the exact same settings. I am somewhat stumped and a bit irritated. Do you have a suggested scene I try from the Included content? Right now not a single anything I tried worked today.

Nothing renders with OptiX or graphics card. The only way I can get anything to work right now is with direct CPU rendering and even that is a hit and miss--some scenes render but grainy like I was an absolute noob at this, or greyed out). Was there an update? Do I need to reinstall?

Rhia, which bedroom set are you trying to render?  I can try it here

Interior Sets --> MA Bedroom

Checked and updated graphics drivers as well.

OK I will try that here and see if I can figure out what's going on

You guys are super kind, this is very mysterious.

We try 8-)  You are super kind too. We got your back 8-)

The superfly version in the included items computes correctly on my system, but I have to say that Poser13 claimed that there was an update today, and I have no details as the version remains 13.0.287

Ouch. Well I did the preload of the MA Bedroom and it rendered fine. So now we have a REAL mystery.  But hopefully since Nerd has the same video card as you he can reproduce it.

I've had the same black render phenomenon a few times, along with random body parts turning black or light purple, and I use CPU rendering which is currently a ryzen 7 on win10. I have a gtx 970 as well but it hasn't rendered anything from Poser since the SM days of P11. It hangs up and does nothing so I have to force close or Poser crashes completely so I just have stuck to cpu rendering ever since cause I can't afford an upgrade and I don't want to stress my ancient card or I'll be out completely lol.

I haven't checked the error messages but if it happens again I will.

Re-rendering randomly fixes the problem, or I'll click a setting on the affected material and that seems to fix it. Sometimes re-importing the image texture has fixed it. Just reloading textures does nothing.

I'm going to go through the shaders on that stuff and see if anything looks suspicious.

Hm, here is a thing:  I had render going fine for a bit, then I toggled Post-render FX and that caused black render no matter what I tried. I am re-rendering without post-effect to see if toggling that causes it and if I have to completely close Poser, reload scene and render again to fix.
If that's what it is, the post-effect selections may be buggy.

I think the key to this issue could be the usage of the PostFX.
Rhia474 mentioned that the render turned black after the render is finished or after the canceling of the render.
This sounds like the PostFX is on and working, right?
This happened to me a few days ago and it was a negative value setting for exposure.
I also had some difficulties to get rid of the setting, it jumped back to the negative numbers after closing the PostFX dialog.
To fix this I had to set a positive number and use one or both save options in the dialog.
Hope this helps.

Exposure = -1 means black result, at least on my PC but I suppose that with -1 it should be correct, shouldn't it?

OK. Try this:

From the Launcher, choose Empty Scene.

Choose Props > Interior Sets > MA Bedroom > !!!Preload.  That will load the entire scene.

Choose Lights > INterior Sets > MA Bedroom > MABedroom_SuperFly lights

Choose Cameras > Interior Sets > MA Bedroom > Camera 4.

Set your Optix render settings.  Quality doesn't matter because we are testing PostFX.  Just let the render finish (if it can)

After the render is done, a thumbnail should appear at the top of the recent renders palette.

Right-click on the thumb and choose Edit Post Effects.

Check Apply Intel Denoise and enable Bloom.

Does that work for you?

I'm going to add to the confusion here.

I got the same error message as Rhia's second with an RTX 2060 when I tried to do a scene with a fog cube and an image on the background shader

@RedPhantom if you still have that scene handy, zip it up as Nerd instructed above and attach the scene to a support ticket

I will try as soon as my back at my computer. Thanks y'all!!

The exposure set to -1 is my bad. Some of the default scenes and the factory scene got shipped with the Post FX exposure set to -1. That will be fixed with the first service release. So change those to 0. Zero is no change in exposure and was supposed to be the default value.

@DCArt: holy moly, yup, that worked. Look!

@nerd, glad we nailed this one down!!

I have to say, this is starting to irritate me!  Quite a few of the models render all black for me and I do not use postfx.  In Firefly I can almost bet it will be black, while in Super, the scene is a light blue screen.

I looks as though some of the older content in my runtime is going to have to be used with care.  I have an aging GTX 1080i graphics card which I found to to my utter disappointment would not work with Poser 11 but thankfully did with Poser 12.  It has been working fine with Poser 13 but today I tried to render a scene with a lot of old content but all I got was a grey screen.  Looking at the logs I am getting a Cuda warning similar to the one already shown here.  The scene will render using the CPU but there is still a slight issue with some old content in that I find glass looks as though I has been set up for emissions, I have seen this on content created by three different vendors so far.  

I don't really blame Poser 13 for this as, despite all the efforts made to make it backwards compatible, there is bound to be a limit somewhere.  I think that using textures from old content will continue to be an issue as we move forward.   I thought the glass problem was due to a cellular node plugged into the defuse colour with a setting of 2+ on the diffuse but changing this alone does not sort the problem as both the specular and reflection needs to be looked at.  I now use a PhysicalSurface node to correct the problem.

Be careful with old scene: they often have ambient occlusion. Till Poser12, the presence of this node used to make the render turn black.
I haven't tested this aspect with Poser13 because since 2019 I use one of the scripts provided with Sasha: it deletes all these nodes in one shot, and it's something I'm launching it systematically

It looks like all older content material will need to be reworked for P13 then. A pain, but at least we have GoPhysical to help with it.

Can confirm: CUDA illegal address error persists with older content if trying to render older content with OptiX or GPU. Can only use CPU. Does not seem to matter is I reworked the materials with script to Physical Surface. There is some sort of reaction between the render engine using the GPU or OptiX that makes renders error out.

Should I add this as a bug to look into, or will this be an unfortunate feature or progress?

Add it to the bug Rae!  :-)

Same here...

I tried a few of the supplied Poser 13 scenes.

They render fine in Firefly as well as CPU/Superfly, but are 100% black with GPU/Superfly.

ACER Nitro 5, Windows 10, 32.0 GB RAM, GTX 1650, i7-10750H CPU

*

Doesn't really bother me that much, as I'm sticking with Firefly for now, at least I until I have a proper GTR card.

And you can't expect a completely different render engine to work with a shader it doesn't understand, anyway.

(Although I noticed that some of my "optimized" Firefly skin shaders render nicely even with GPU/Superfly after some minimal modifications.)

Even the preview still looks "nice", too. (Unlike the "pure-breed" Superfly shaders that just show up white in OGL.)

So there might actually be a type of "hybrid" skin shader possible that works with both engines with none or just little modifications?

Just successfully rendered a really old scene from DM "Moon Cult" and it renders fine in both FF and SF.  This is the SF render.  This set is set up for Poser 6/7 so pretty old.  

Right, the issue is with specifically GPU and OptiX renders. Did you use those or CPU?

Silly me, didn't look.  

Now that I've converted using the Go Physical though the flames for the candle flames are all rendering like blocks/  Transmaps are all connected so it's another weird moment!  LOL 

Yeah, sorry, methodical me is methodical, lol. :)

Silly me, didn't look.  

Now that I've converted using the Go Physical though the flames for the candle flames are all rendering like blocks/  Transmaps are all connected so it's another weird moment!  LOL 

For the flames you need to play with the transparent settings at the top of the PhysicalSurface, set the transparency 'GO Physical' usually leaves this set to zero.  Set the Emission strength to something above 0.000 to make the flames glow.  You may need to toggle the TransparencyMode from Opacity to Transparent but it seems to depend on the nature of the map you have plugged into color.