OctaneRender 3 for DAZ Studio [TEST and STABLE] [OBSOLETE]

[Notiusweb]

Hi Paul, it would be #1, Bitmap on the alpha areas of viewport. In Daz it's called a 'Backdrop'.

Got you. The backdrop would not save in the PNG/EXR - would that be confusing to users?

Paul

Is there a way it could be saved, 3Delight and IRAY both save the background to a PNG, at minimum could OcDS do the same for PNG if the backdrop is brought over into OcDS.
Otherwise, users would be confused by this inabaility, yes. However, the ability to visually in-screen set the rendered foreground against the background (colors, lighting) would be highly useful, even if this means we still later have to merge the PNG to background outside of OcDS . I know I can do these things with the Sky Texture but the image is warped (i.e. not just the simple flat background.), so there is a lot of trial and error.

Thanks so much Paul!

[face_off]

Is there a way it could be saved, 3Delight and IRAY both save the background to a PNG, at minimum could OcDS do the same for PNG if the backdrop is brought over into OcDS.

This is an Octane engine limitation - so I suggest requesting this feature in the Octane Standalone test thread, or viewtopic.php?f=9&t=37045&p=304954.

However, the ability to visually in-screen set the rendered foreground against the background (colors, lighting) would be highly useful, even if this means we still later have to merge the PNG to background outside of OcDS . I know I can do these things with the Sky Texture but the image is warped (i.e. not just the simple flat background.), so there is a lot of trial and error.

Pasting a background image under the Octane render bitmap is not trivial, because the Viewport will not necessarily be the same size as the bitmap, so there are a lot of decisions to be made over whether the image is stretched or shrunk or cropped, and if the aspect ratio (W vs H) is changed. The Poser and Modo plugins both offer this function, and it is poorly implemented, and I doubt anyone actually uses it. So I don't think adding it to the DAZStudio plugin would be of value unless the Octane engine was enhanced to save the background image with the PNG/EXR.

Paul

[face_off]

Following is a pre-release of the plugin compiled with Octane 3.06 TEST 3.

3.6.2.32 PRE-RELEASE
- Compiled with Octane 3.06 TEST 3 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements
- Renamed the Camera->OctaneRender->Bokeh sharpness parameter to Aperture Edge
- Added Camera Visibility to the OctaneRender parameters group (for meshes)

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

[zx13275744718]

Following is a pre-release of the plugin compiled with Octane 3.06 TEST 3.

3.6.2.32 PRE-RELEASE
- Compiled with Octane 3.06 TEST 3 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements
- Renamed the Camera->OctaneRender->Bokeh sharpness parameter to Aperture Edge
- Added Camera Visibility to the OctaneRender parameters group (for meshes)

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

Thank you!

[itou31]

Hi Paul,

I come back with the texture resize aspect.
The texture resize information is not save with the duf file. I reload a scene on another PC and textures are not resized.
Can you tell me where is stored this information ? Or how to transfer this information to another PC.
And about network, are resized textures transmitted to the slave node. Not test it yet, as I don't like to use OOC feature that slow down rendering (1X PCI riser).
Thanks.

[Notiusweb]

Is there a way it could be saved, 3Delight and IRAY both save the background to a PNG, at minimum could OcDS do the same for PNG if the backdrop is brought over into OcDS.

This is an Octane engine limitation - so I suggest requesting this feature in the Octane Standalone test thread, or viewtopic.php?f=9&t=37045&p=304954.

Wait, a background image can be saved in a rendered PNG in the standalone if it is the visible environment, or sky texture, so the ability is there already, no?
I know there is that alpha-background dialogue button in the standalone where you can set a background image but it does nothing to save, but the mechanics still exist there, no?

However, the ability to visually in-screen set the rendered foreground against the background (colors, lighting) would be highly useful, even if this means we still later have to merge the PNG to background outside of OcDS . I know I can do these things with the Sky Texture but the image is warped (i.e. not just the simple flat background.), so there is a lot of trial and error.

Pasting a background image under the Octane render bitmap is not trivial, because the Viewport will not necessarily be the same size as the bitmap, so there are a lot of decisions to be made over whether the image is stretched or shrunk or cropped, and if the aspect ratio (W vs H) is changed. The Poser and Modo plugins both offer this function, and it is poorly implemented, and I doubt anyone actually uses it. So I don't think adding it to the DAZStudio plugin would be of value unless the Octane engine was enhanced to save the background image with the PNG/EXR.

Paul

I see what you are saying about the complexity, in that you could have Daz stretching resizing the image to meet its own render-settings aspect ratio and resolution, and then you would have OcDS taking it all in, and now running with its own aspect ratio and resolution on top of that. What I think would work here is not for the image to be 'matched' to what is happening in Daz, but rather to be merely 'brought over' to OcDS, and then like Daz does, OcDS could just stretch or resize the image to meet whatever aspect ratio or resolution is decided in the OcDS settings.

Additionally, this idea I am speaking of is not only an idea unto itself of a feature upgrade to OcDS, but also an alternative to OcDS not having the ability to run 2 separate environments (1-Environment, and 2-Visible Environment) like the Standalone can in fact do. (originally brought up by Linvanchene)

And most importantly, why do only Modo and Poser get to mess with a poorly implemented version of this....I would LOVE to!
But seriously, your work is excellent, this is why I try to request!
Would this cause issue if a scene was exported as an ORBX?

Thanks Paul!

[face_off]

Wait, a background image can be saved in a rendered PNG in the standalone if it is the visible environment, or sky texture, so the ability is there already, no?
I know there is that alpha-background dialogue button in the standalone where you can set a background image but it does nothing to save, but the mechanics still exist there, no?

No - the background image is not saved even when the Visible Environment is enabled.

but rather to be merely 'brought over' to OcDS, and then like Daz does, OcDS could just stretch or resize the image to meet whatever aspect ratio or resolution is decided in the OcDS settings.

You are assuming users want the image stretched - they may not.

And most importantly, why do only Modo and Poser get to mess with a poorly implemented version of this....I would LOVE to!

Unfortunately is it a lot of work to implement what you are asking for (the background image needs to be pasted into the actual Octane render buffer bitmap), and I know from other plugins that it would be of almost no value - so it is hard to justify the effort required to make this change. The best path forward would be for Otoy to allow the background image to be specified in the Visible Environment, and to have the background image saved with the PNG/EXR.

Paul

[Notiusweb]

Hi Paul, understood. thanks for putting me in the right direction!
-Notiusweb

[Notiusweb]

Paul, any roadmap for when the Daz plugin might have the functionally implemented 'Visible Environment' like you were able to give the Poser, Modo, and Rhinoceros plugins? (IE next couple months, later 2017)

Be well and thanks again,
Notiusweb

[MyRho]

Hi.

I've found some strange problems with "3.6.2.32 PRE-RELEASE"; maybe it's because I'm using the redspec-shaders on my G3 but when I try to re-render a scene (HDRI, pathtracing) there are some strange/weird colours in my renderings so I've re-installed the old version immediately. Tried a few old scenes without any changes. The renderings looked like 8-bit BMPs, there were no smooth but very hard shadows (contrast). Am I the only one having problems like these?
After re-installing 3_5_3_31 octane is running without any problems.

MyRho