OctaneRender for DAZ Studio 3.02 [OBSOLETE]

[face_off]

On the standalone, there is just a possibility to choose GPU tone-mapping. Do you think that you will integrate this feature in the plugin ?

I will add this to the next release.

Also, I just see that there is on the system tab many information about number of triangles on the scene and especially the "hair" information. Is it to count "octane hair" ?
Is it possible "now" or in the future any way to tell the plugin that fibermesh (use in LAMH) is "octane hair" ?

Adding support for LAMH is on the "todo" list, but it is a major job, so I cannot look at it for a few more months.

Paul

[ForceX]

After installing the 3.0.10.19 octane plugin for Daz 4.9.1.30, Daz crashes on load after entering octane account information.

Here is a debug log provided by Visual Studio:

Unhandled exception at 0x0000000019CD3F10 (octane.dll) in DAZStudio.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

Error reported from Daz Log file:

E:\Programs\Daz\DAZ Software\x64\DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\plordazs.dll failed to load. Cannot load library E:\Programs\Daz\DAZ Software\x64\DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\plordazs.dll: The specified procedure could not be found.

Installing previous version 3.0.6.18 restores Daz ability to load & octane rendering.

[face_off]

E:\Programs\Daz\DAZ Software\x64\DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\plordazs.dll failed to load. Cannot load library E:\Programs\Daz\DAZ Software\x64\DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\plordazs.dll: The specified procedure could not be found.

That is an odd folder for the plugin to be in (DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\) - is it possible you have multiple versions of the plugin and Octane dll's on your system and the wrong one if being loaded?

Paul

[Notiusweb]

Hi Paul,
Was looking to try out using the selectable Tonemapping feature that was introduced in standalone Aplha 10, but the OcDS plugin doesn't have yet. Will that be added soon?
Just FYI - The tonemapping processing (used in Post Processing and Baking Camera) was making the Nvidia & DirectX drivers clog up CPU when some PCIe 1x splitters were used, causing a PC freeze and crash. Marcus introduced the ability to disable tonemapping per GPU so those GPU cores on a splitter could still be used for the rendering, without being involved in the tonemapping processing, thus avoiding crashing the PC. Ie in my case I can assign the main GPU tone mapping while disabling tonemapping on all the other cards, so no more PC freezing crashing (on the standalone)
Thanks!

[face_off]

Was looking to try out using the selectable Tonemapping feature that was introduced in standalone Aplha 10, but the OcDS plugin doesn't have yet. Will that be added soon?

It should be in the next release.

Paul

[Hubby72]

Is there some kind of feature list for this new version ? I meanto compare the Plugin 2 with the Version 3 Plugin.

I for sure found a the new feature overview from Octane 3 Standalone, but what of the features do we have in OCDS Plugin ?

I am looking for a reason to upgrade as a user who never uses Standalone version. I work 100% in DAZ and the Plugin.
And i ask me what changes for me ?

[kiatar]

Do not activate 3.0.10
3.0.6.18 OK

[ForceX]

That is an odd folder for the plugin to be in (DAZ 3D\DAZStudio4\plugins\OctaneRender\bak\) - is it possible you have multiple versions of the plugin and Octane dll's on your system and the wrong one if being loaded?

Not sure. Sunday I did a clean windows 10 install. Reinstalled daz, installed octane 3.0.6.18. Then yesterday I installed 3.0.10 and got those errors. Should I manually uninstall 3.0.6 prior to installing 3.0.10. I have always let the installers handle everything.

[itou31]

Hi Paul,

Adding support for LAMH is on the "todo" list, but it is a major job, so I cannot look at it for a few more months.

Paul

Yes ! it's just a minor feature, but when it will be supported, it will render a lot faster. thanks.

[ForceX]

So i uninstalled Daz deleted any remaining files and folders from it's directory then reinstalled Daz and installed 3.0.10. Worked fine this time around.