Larger version in my gallery

@RedPhantom Looks good! Did you use a giant cube with a scatter volume node on it?

RedPhantom posted at 10:32 PM Thu, 6 April 2023 - #4461078

My first Poser 13 render. I had wanted to add some fog, but it wasn't working. I'm going to have to experiment and see if I messed it up or if Poser 13 is having an issue.

Edit to add it was user error.

Really cool picture.
And if you need a setup: BB showed us all a setup, at the  time of RDNA, that still works, but it's connected to a PoserSurface Node:

still tweaking the shader

You need to install the Core Content first into your Library.  On startup, the selections will show up on the splash screen.

I normally don't like to post something twice but I softened her face some and like it better now 8-)

And argh yes I just noticed that her right arm is poking into her stomach. I'll fix that in the gallery image.

I'm not the worlds best render person but wanted to see how my Jon for L'Homme rendered in Poser 13 with the updated Hivewire Cat's Cycles texture set up.  Very nice and very happy that Jon renders well.  I may return to my character packs when time permits and release some free Cycles updates for the skins and eyes.  I'm still finding my way with Cycles and testing allot on my newest character for L'Homme, Eliezer, a Latin man.  I really like developing for LH but am looking forward to Dawn 2 and eventually Dusk 2.  

And yes this is a composition cobbled together in Photoshop (just the close up)  I used the Background node in Poser to bring in that really pretty path with flora, I did add in the shadow as I wasn't sure, at the time, if a shadow catcher would work with Cycles for that but apparently it does so hopefully won't have to fake ground shadows.  I just did a quick object selection in PS and then inverted and used the Burn brush tool to put it in.  Little dark but worked!  

RedPhantom posted at 10:32 PM Thu, 6 April 2023 - #4461078

My first Poser 13 render. I had wanted to add some fog, but it wasn't working. I'm going to have to experiment and see if I messed it up or if Poser 13 is having an issue.

Edit to add it was user error.

Really cool picture.
And if you need a setup: BB showed us all a setup, at the  time of RDNA, that still works, but it's connected to a PoserSurface Node:

I know: a sunny day with fog is weird... 

The PhysicalSurface node has a Volume connector.

You're right I just forgot...
And there are slight differences, for example: the PoserSurface shows the back boundary of the capsule for I used

More doodles and shader tweaks.

Finally was able to get a render with the fog. I tried all three suggestions made, but it wouldn't render if I was using the hdri on the background. I had to switch to the environsphere.

Working without lights can be challenging, but fun.

I am very impressed!

The upgrade is worth it.

And I almost forgot about my mother-in-law... and then along came Poser 13.

Ok... that's a little bit better. I played around a bit on the denoiser... grunt.

So… I did my first render in gazillions of years, it seems :)
This was just to check that stuff was properly installed and working.
A few folk from an ancient runtime got to play together on a hillside.
I have to admit - I've almost forgotten how to use Poser, but it's coming back to me.

So… I did my first render in gazillions of years, it seems :)
This was just to check that stuff was properly installed and working.
A few folk from an ancient runtime got to play together on a hillside.
I have to admit - I've almost forgotten how to use Poser, but it's coming back to me.

I have to admit - I've almost forgotten how to use Poser, but it's coming back to me.

Maybe a little candlelight will help lighten things up...

Well, I'm still not liking Superfly enough to switch, but me and Vicky 1 Low Resolution are enjoying the improved Firefly speed quite a lot.

Had to play with the prime freebie. It doesn't have the Superfly shaders so I updated those.

Soo pretty!

Working without lights can get difficult, but it is fun.  Poser 6 with some post work.

@hornet3d I have a free light set that includes a light set that lights the scene while you work but does not light anything when you render.

https://www.renderosity.com/freestuff/items/86815/studio-lights-for-poser-12-and-poser-11

Not the best textures for the ship.....a pity.

Win 11, Poser 13, OptiX high - approx. 45 seconds, PostFX denoiser 0.5 etc.  Ryzen 9 5950X 16-Core, 64GB, RTX 2070 Super....

@hornet3d I have a free light set that includes a light set that lights the scene while you work but does not light anything when you render.

https://www.renderosity.com/freestuff/items/86815/studio-lights-for-poser-12-and-poser-11

Played a little with Dawn and Walk Designer and quickly came to this. It seems to work very well with Poser 13.

jroulin posted at 10:36 AM Sat, 8 April 2023 - #4461276

Played a little with Dawn and Walk Designer and quickly came to this. It seems to work very well with Poser 13.

This is the scene that my graphics card did not like, the log stated problems with a texture but with so many where do I start.  Thankfully it rendered in with CPU.

Yeah, I came to the conclusion that P13 does not like anything that is pre-P13 texturewise to render with graphics cards. Something with the new render engine is even more hostile to old setups then P12 was and even texture converter scripts don't help. Or are inconsistent.

It must be something with Physical vs. Cycles Surface. This may need at least a short manual/ documentation from those who understand the differences for us casual users, because it will cause quite a noise. There is a LOT more work to be done to convert to render correctly.

hornet3d posted at 11:29 AM Sat, 8 April 2023 - #4461288

This is the scene that my graphics card did not like, the log stated problems with a texture but with so many where do I start.  Thankfully it rendered in with CPU.

What scene is that, hornet?   And can you PM me with your email addy so that I can get a copy of that error log?

I feel that Poser will move away from the PoserSurface and replace it with the PhysicalSurface node.  There are fewer parameters to keep track and the connections are more efficient.  I will need to run Firefly renders with both PoserSurface and PhysicalSurface but from what I see, the PhysicalSurface node produces better results.

hborre posted at 12:03 PM Sat, 8 April 2023 - #4461294

I feel that Poser will move away from the PoserSurface and replace it with the PhysicalSurface node.  There are fewer parameters to keep track and the connections are more efficient.  I will need to run Firefly renders with both PoserSurface and PhysicalSurface but from what I see, the PhysicalSurface node produces better results.

And for the record, Physical Surface root works MUCH better with PBR Metal and Roughness maps than the Spec and Gloss maps used in PoserSurrace. 

Yeah, I came to the conclusion that P13 does not like anything that is pre-P13 texturewise to render with graphics cards. Something with the new render engine is even more hostile to old setups then P12 was and even texture converter scripts don't help. Or are inconsistent.

It must be something with Physical vs. Cycles Surface. This may need at least a short manual/ documentation from those who understand the differences for us casual users, because it will cause quite a noise. There is a LOT more work to be done to convert to render correctly.

Alt Diffuse and Alt Spec on the PoserSurface node might be suspect. There really isn't an equivalent on the Cycles-friendly root nodes (Physical Surface and Cycles Surface).

But here is the thing. Even after I used the Physical Surface root for conversion, those scenes still rendered black. Used Ken1171's script specifically. That led me to the conclusion that there must be something P13's Sfly renderer using GPU or OptiX does not like even in the PS node.

Will test a bit further tonight, but based on this morning's tests, that was my preliminary observation.

But here is the thing. Even after I used the Physical Surface root for conversion, those scenes still rendered black. Used Ken1171's script specifically. That led me to the conclusion that there must be something P13's Sfly renderer using GPU or OptiX does not like even in the PS node.

Will test a bit further tonight, but based on this morning's tests, that was my preliminary observation.

Oh ,no, this was not included content and I think that's at the root of the thing. There is a LOT of content people (like me) purchased here or elsewhere for good money that are solid items but cannot use them under current conditions. Let me see what I got as an example.

And the maddening part of it is, there is no consistency. Some old scenes I open render fine, some immediately render black. It looks as if there must be some particular material settings that causes this.

Oh ,no, this was not included content and I think that's at the root of the thing. There is a LOT of content people (like me) purchased here or elsewhere for good money that are solid items but cannot use them under current conditions. Let me see what I got as an example.

Oh ,no, this was not included content and I think that's at the root of the thing. There is a LOT of content people (like me) purchased here or elsewhere for good money that are solid items but cannot use them under current conditions. Let me see what I got as an example.

And the maddening part of it is, there is no consistency. Some old scenes I open render fine, some immediately render black. It looks as if there must be some particular material settings that causes this.

Firefly chokes on hair for me, like it always did, but otherwise the two scenes I tried render, no problem.

Yeah, give me a few hours so I can get some links and such when I'm not with family and will send some linkies. THANKS!

I have not been using included shaders for anything for years because of problems. Even before Superfly I'd see crazy node setups that did not make any sense and now that I'm rendering using a GPU that craziness just equates to an OPTIX crash or something rendering total black. It's one of the reasons I really hate buying/using large scene props from the marketplace. None of the mats are optimized for Superfly or worse, they generate a crash.

When I do use something I have to replace EVERY material with my own. Here is anexample

Right, sure, but what if you HAVE those because you work on certain genres and you NEED them? I mean, it's not that I can pick and choose for historical furniture for P13?

@DCArt, I just tested Montespan Interior Scene:
https://www.renderosity.com/marketplace/products/97411/montespan-interior-scene

I used Go Physical to convert every prop into Physical Surface. It *still* remders black both with OptiX and in GPU.

Gorgeous set Rhia, it goes back to Poser 5/6 days (eeeekkkkkkk) .... when converting the figures, each generation I went back had more challenges. So this should be a fun one LOL. Still suspecting Alt Diffuse and Alt Spec connections not converting, but we shall see. 8-)

I don't see any of those connections in my Matroom active...

Rhia474 posted at 1:33 PM Sat, 8 April 2023 - #4461315

I don't see any of those connections in my Matroom active...

Are there any props in particular in that set that are giving you problems that I should look at?

OptiX Ultra Caustics  without PostFX

I would need to do a one-by one by prop. I loaded it as a whole scene. Need some time for that.

hornet3d posted at 11:29 AM Sat, 8 April 2023 - #4461288

This is the scene that my graphics card did not like, the log stated problems with a texture but with so many where do I start.  Thankfully it rendered in with CPU.

What scene is that, hornet?   And can you PM me with your email addy so that I can get a copy of that error log?