Simple question

[bpzen]

Can someone explain the purpose for the Final Render button what dose it do that letting a render go and stopping when happy with results? Is there a benefit to using this?

[Notiusweb]

This is s good topic, for me anyway...I have no idea what that button does differently compared to the scene rendering normally.

( I also don't know what purpose an alembic export serves, you can render an animation via Daz, why does one want an alembic export if you already have a rendered animation? )

[linvanchene]

@ Final Render Button

- In theory all the geometry in the scene is treated as "one unit" when using the final render button.
This was supposed to actually speed up render times.

- Another purpose for using Final render mode was also to "lock" cameras and the settings while rendering so you do not by accident restart the render.

Several users started to report issues happening when rendering in final mode so I simply stopped using it and so far do not think I am missing out on anything.

- - -

Update / Edit:
removed outdated information about alembic export

[TRRazor]

Can someone explain the purpose for the Final Render button what dose it do that letting a render go and stopping when happy with results? Is there a benefit to using this?

I've read in the To-Do-List (and the corresponding poll) that this "Final" render button is still a requested feature, why?
The button does exactly what it is supposed to do - ignoring GPU priorities set in the "System" tab of OctaneRender, channeling all available GPU resources into the OCDS plug-in for rendering.

Just used it yesterday for a render I did and the S/P-values were:

Without "Final": ~ 4.38 S/P
With "Final": ~ 6.12 S/P

Just remember that you can't change any render settings while being in "Final" mode without restarting your render.
Also: This stresses your GPU(s) to the max - only use it when you're absolutely sure, that your cards are cooled well enough.

[SiliconAya]

The button does exactly what it is supposed to do - ignoring GPU priorities set in the "System" tab of OctaneRender, channeling all available GPU resources into the OCDS plug-in for rendering.
.

For me at least, this is only true if I don't touch the performance sliders in the system tab, soon as I do, the sliders will overrule what the final button sets the priority to.

However, this isn't the only speed increase you get from the final button, as mentioned above it's meant to "merge" all the meshes into one (and does from what I can see). From testing, I've found that the more complicated the scene, the bigger speed increase you'll get from this, so a simple scene with 1 figure wont see much gain, but one with 4+ figures with props etc will see a much bigger speed increase.

But it does have issues as mentioned, most recently I've found it ignores the Surface Brightness setting under emissions, so it's best to test and see if it works for your scene.

[Notiusweb]

I am assuming the 'mode' can't be used for animations, just for a single frame, right?

[TRRazor]

For me at least, this is only true if I don't touch the performance sliders in the system tab

That's the whole point of a "FinaL"-button- you're not supposed to touch anything while using it- hence the word "final"

I am assuming the 'mode' can't be used for animations, just for a single frame, right?

Never tried animation in DAZ Studio - maybe somebody else can answer this question...

[SiliconAya]

Being about the change the throttling while in final mode is a good thing to me, sometimes you just have to use your computer while it's rendering and being able to change it so as not to have the UI lag is a good feature.

[linvanchene]

( I also don't know what purpose an alembic export serves, you can render an animation via Daz, why does one want an alembic export if you already have a rendered animation? )

I just found out that somewhere between PreRelease 5th 2.21 and the last beta 2.23 the alembic export functions may have changed.

In the PreRelease 5th 2.21 there was still an alembic geometry export option.

Now it seems since 2.23 there is only an alembic camera export option.

- - -

It seems in general just exporting as .abc offers more limited options compared to exporting as .ORBX where all OR specific material information is also included.

The .abc export may have been an alternative export option for some workflows until the .ORBX export was fully functional.

Still it seems odd that the alembic geometry export option was removed but the alembic camera export option was kept.

That being said:

The alembic camera export option CAN still be of use when trying to export just the cameras to other applications that do not support ORBX import.

Having the same cameras including their movement in other applications can make it easier to composite scenes.
- - -