This has been my "goto" render settings for a good 18 months. It gets me what I usually need for a shot.

I realize there isn't a "one size fits all" but this has been working for me.

I swap between the CPU and GPU as needed for speed and file size.

I already tried this setting in Poser 13, but it tanked - on the scene I'd just rendered in P12 in under 5 minutes, it was easily going to take an hour + in P13.

Note : I take advantage of the 32 threads - and when I render in P12  - I can see 32 different buckets all rendering - but in P13 - I do not see this happening.

Platform AMD Ryzen X670E ATX

Motherboard Asus ProArt X670E-Creator WiFi

CPU AMD Ryzen 9 7950X 4.5GHz 16 Core 170W

Ram 2 x Kingston DDR5-4800 32GB

Video Card Asus GeForce RTX 3080 TUF OC 10GB Open Air V2 

So, all that said - any suggestions on what to adjust for P13 to get a similar result?

Thanks!

sturkwurk

sorry it should ask "NOW what do I change..."

You could try using the presets to see if anything provides what you want.  There have been changes to the Adaptive Sampling which seems to allow a drop in the pixel samples and thus a drop in render time.  I have so far used the GPU high preset which has Adaptive Sampling at 0.001 where I was using 0.002 in Poser 12 but the samples have dropped to 25 in Poser 13 where Poser 12 was set at 50.  The quality is about the same as what I was getting with the Ultra GPU preset in Poser 12 and the majority of my renders were much faster but it did vary a lot from scene to scene.

When using the CPU there was no sign it was using all the cores but checking Windows resources all the threads were maxed out, at least on my machine.

Try one of the presets that you see when you click the "Load Preset" button. Start with one of the Medium settings (there are some for CPU and GPU). If you need higher quality move up to High. And Ultra gives the best quality.  Naturally, the higher the quality, the longer the render will take. The Options menu should also allow you to choose OptiX since you have an RTX card.

The settings I show here are for OptiX High

I think your biggest issue might be the number of pixel samples  being really high, but your GPU should render much much faster than CPU. Especially with OptiX

(Crossposted with Hornet, that's what I get for typing too slow LOL)

I had tried the presets - but my images were getting blown out - I guess I have to rethink my lights now too - needling less.

Thanks!

I find that even in P12 I needed way less lights, often just using HDRI on background was plenty. I imagine P13 is even more sensitive.

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

Whoa, no kidding about the lights being blown after P12. I just got P13, setup was a dream, linking runtimes was easy with the included script, old scene opened up fine. It renders in P12 with nice soft glow. In P13...wowza, the reflections are all blown on surfaces they should not be, like sofa cloth. 

This will be fun.

That 128 Pixel Samples translates into 16,384 runs through the rendering process.  For a quick and dirty test I use 4 and for final around 16.  As far as lights try setting up one of the Startup scenes Mondello beach or Wild Street.  They have a single IBL light over head to provide lighting for working on the scene which does not render in final.  So basically you can now do scenes just using the surrounding HDRI image and have no lights.  You probably will want to add lights to get the effect you want much like Hollywood does in making a movie.  But without those lights it is like you taking your camera and taking a picture.

Also you should use the Progressive Mode to render as it has been found to render faster then the old bucket system.  That shocked me the first time I ran a default render and did not see the little buckets.

Also the small bucket size you have means that a lot of time is spent setting up the data to send out to be rendered.  There is a spot where too small and time is wasted in packaging and too large no more improvement is seen.

(Crossposted with Hornet, that's what I get for typing too slow LOL)

The bucket setting is used no matter which render mode you use.  Think of it as you giving a person a task to sort a stack of papers.  You grab a stack of say 32 pages and walk up ten flights of stairs to hand to the person doing the sorting (this is the setup phase) Then you go get some more.  By the time you go down the stairs and back up with another 32 pages, the sorter has been sitting waiting for you.  However if you give them 512 pages you have a better change they will still be sorting or just finishing when you return.  That is why your render times can be longer, is because the render engine is sitting waiting for you to give it more info to process.

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

That 128 Pixel Samples translates into 16,384 runs through the rendering process.  For a quick and dirty test I use 4 and for final around 16.  As far as lights try setting up one of the Startup scenes Mondello beach or Wild Street.  They have a single IBL light over head to provide lighting for working on the scene which does not render in final.  So basically you can now do scenes just using the surrounding HDRI image and have no lights.  You probably will want to add lights to get the effect you want much like Hollywood does in making a movie.  But without those lights it is like you taking your camera and taking a picture.

Also you should use the Progressive Mode to render as it has been found to render faster then the old bucket system.  That shocked me the first time I ran a default render and did not see the little buckets.

Richard60 posted at 5:37 PM Fri, 31 March 2023 - #4460242

That 128 Pixel Samples translates into 16,384 runs through the rendering process.  For a quick and dirty test I use 4 and for final around 16.  As far as lights try setting up one of the Startup scenes Mondello beach or Wild Street.  They have a single IBL light over head to provide lighting for working on the scene which does not render in final.  So basically you can now do scenes just using the surrounding HDRI image and have no lights.  You probably will want to add lights to get the effect you want much like Hollywood does in making a movie.  But without those lights it is like you taking your camera and taking a picture.

Also you should use the Progressive Mode to render as it has been found to render faster then the old bucket system.  That shocked me the first time I ran a default render and did not see the little buckets.

ah - that's good to know too - thank you!

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

caisson posted at 4:29 PM Fri, 31 March 2023 - #4460231

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

I know this is an old thread, but I'm not finding that to be the case with the last update of P13.  It does render one bucket at a time, but watching resources, it only uses a couple of threads per bucket, significantly slowing things down.  It does the same in progressive mode.  Previously, it would use all available cores and render much faster.

beas62 posted at 2:24 PM Sat, 14 September 2024 - #4489319

caisson posted at 4:29 PM Fri, 31 March 2023 - #4460231

The Superfly render engine has changed a lot under the hood. In P12 one thread would render one bucket, so you'd set the number of buckets to match the threads available for CPU rendering. However in P13 that has changed - all threads render one single bucket at a time.

Two options - either increase the size of the bucket (more threads = bigger bucket, though RAM will play a role too) or switch Progressive Rendering on which will then ignore the bucket setting.

The Log will give you an exact time for each render to compare different settings.

In addition, I've found that P13 needs less samples than P12, I'd suggest try halving the setting first. With both P12 and P13 installed you should be able to do some comparisons. Also the Denoise post-process option is imo better than P12.

Basically I've found that P13 is significantly faster for me.

I know this is an old thread, but I'm not finding that to be the case with the last update of P13.  It does render one bucket at a time, but watching resources, it only uses a couple of threads per bucket, significantly slowing things down.  It does the same in progressive mode.  Previously, it would use all available cores and render much faster.

Okay, Poser tech support admitted they broke it with the newer releases.  They said to fall back to 13.3.686.  I did and it fixed it.

If you don't want to use a render preset from the ones included, here's what I'd do starting from yours:

-Switch to Optix instead of CPU rendering - your 3080 should be more than enough for that! And that will give you much faster render times. 

-Increase your bucket size - rule is usually smaller buckets for CPU rendering, larger buckets for GPU rendering. You'll probably want something around 500 there, but a divisor (is that the word in english?) of your render size if you REALLY want to optimize it. I usually leave it at 500 exactly because I tend to render at 1500x1500, 2000x2000 or 3000x3000px.

-Reduce your pixel samples - P13's version of Superfly uses less of them for the same quality.

-I'd also use Progressive Refinement mode - this way I crank up the pixel samples and then stop the render whenever it looks good to me, instead of waiting per bucket.

Yes I saw that this post is a bit old, but perhaps that information is still valuable for anyone that might end up here and wants to understand a little bit more of the differences between P12 and P13 Superfly :)