OctaneRender for DAZ Studio 2021.1.5 - 72 [OBSOLETE] Tweet

[toby_a]

This is the recommended thread for downloading, and posting any questions, suggestions or support queries for OctaneRender for DAZ Studio - TEST (ie. pre-release) and STABLE releases.

SOLUTIONS TO COMMON ISSUES

1) Make sure your NVIDIA drivers are up to date.

2) Make sure you are running the latest version of the OctaneRender for DAZStudio plugin.

3) If you experience a DAZStudio crash - deleting C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb may resolve the issue.
This also resolves the "COULD NOT INITIALISE IN-MEMORY DB!" error on startup and a number of other issues.

4) If the Save button is disabled when using the Final button - disable the Final button and in Render settings select the SuperScope (2:1) Size / aspect ratio and drag the Viewport height or width until you reach required resolution.

5) If rendering an animation fails after 11 frames - make sure the DAZStudio viewport is visible when you render the animation.

6) If Octane materials are not loading when you load a previously saved scene - tick Preferences->Load OctaneRender materials from .duf user presets. If ticking this option does not stick between DAZStudio restarts, delete OctaneRender_settings.oczdb as per NOTE 3 above.

7) If you get a "Could not save a frame for X times!" - please refer to the thread at [url]
[/url] for potential solutions.

8) If you get a "Bogus Scene Path" error - this is due to having an apostrophe in the filepath of a texturemap (so store your textures in foldernames which do not have apostrophes).

9) Octane panel title bar is off the screen and cannot be closed - click anywhere on the Octane panel and then press Alt-F4.

10) Rendering animation results in the scene emitter intensities changing - this is because rendering animations is done in "Final" mode, where meshes are merged. To resolve this, UNTICK the Preferences->Use Combined Mesh, or ENABLE the Surface Brightness pin on each of the emission materials in the scene.

11) Denoiser is not working - make sure you have a graphics card selected for Denoising in the System tab->Open Device Settings window, and that you are using the Path Tracing kernel.

12) Render artifacts near eyebrows - this is due to the eyebrow geometry going inside the head mesh surface. So morph, move or scale the eyebrows so they do not intersect with the head mesh.

13) Octane panes do not appear on the screen (ie. they open off the screen) - Main Menu Bar->Window->Workspace->Select Layout->Accept (you might choose a different layout to the current layout to make this work).


KNOWN ISSUES AWAITING RESOLUTION

1) Custom LUT, Panoramic camera and OSL nodes are not currently supported.

2) Templating is not currently working for specular and roughness maps from Iray materials. - FIXED (please report any issues)

3) UDIM Tiles are not currently supported.

4) Some of the newer OctaneRender material and texture types are not supported. - FIXED (please report any issues)

DAZ Studio Version
DAZ Studio 4.8 or later on Windows 8, 10 or 11 64bit

To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped.
Also, make sure you use an Nvidia Studio driver of version 451.xx or higher.

Network Rendering

For Network Rendering, you must use the OctaneRender Enterprise Node release from the Octane Standalone forums/download page which matches the exact Octane version of the plugin you are using. This version matches OctaneRender Enterprise 2021.1.5 Render Node builds.

Support Issues
If you have a support issue, pls provide the following information:
- Operating System (ie. Win 8, 10, 11)
- Amount of RAM
- Graphics Card(s) - model (ie. GTX 580, 3GB)
- Nvidia driver version
- DAZ Studio version
- OctaneRender for DAZ Studio version (e.g. 2021.1.5_72)

- The most important part of resolving a problem is being able to reproduce that problem. So pls provide as much detail as possible in order for me to do this, and if the problem is specific to the scene, send me the scene.


Change logs since 2021.1.5 - 71 [Test]

• Added the ability to add/remove inputs on certain node types in the nodegraph editor
  
  • In particular, it is now possible to add extra control points to the Color Gradient node
• Added several node types that rely on being able to add/remove inputs:
  
  • Layered Material and Layer Group
  • Composite Material
  • Composite Texture and Composite Texture Layer
  • Vertex Displacement Mixer
• Minor bug fixes

Download Links

For users with an Enterprise subscription license

- OctaneRender for DAZ Studio 2021.1.5 - 72

For users with a Studio subscription license

- OctaneRender for DAZ Studio 2021.1.5 - 72

For users with a Prime/Free Tier license

- OctaneRender for DAZ Studio 2021.1.5 - 72

Please feel free to report any issues you encounter.



Happy rendering
Your OTOY team

[toby_a]

The link for the Studio license installer was incorrect. I've fixed it now but please make sure you really have version 72 if you've already downloaded.

[Sorel]

Toby thank you so much for this release! The layer material seems to be working perfectly from my short tests.

[SiliconAya]

Another great update, lots of new nodes and improvements to use!
Time to work on version 11 of my skin material I think.

Thank you!

[Hun73rdk_1]

Another great update, lots of new nodes and improvements to use!
Time to work on version 11 of my skin material I think.

Thank you!

Do you ever share your skin material ??

[SiliconAya]

Another great update, lots of new nodes and improvements to use!
Time to work on version 11 of my skin material I think.

Thank you!

Do you ever share your skin material ??

No, not the material itself, I've had people steal parts/ideas from this forum before and put them into the next version of their paid product without even a mention, credit or thank you.
I'm always open to questions though.
I'm currently working out a good way to use micro skin detail maps like the ones used by Daz 8.1 characters using the new nodes we now have. I've got normal maps working without quality loss, roughness maps are next and I'll post my method here when I'm done. However, I just lost some of my progress due to the crash bellow


Clicked the add input button in one of the new nodes and got this crash:

Historically Access Violation crashes have been somewhat common when clicking/doing things in the plugin, so I'm not sure if this is related to the new add input button specifically or is just a general crash from clicking something.

[sudisk]

Hello, I noticed a weird behavior starting maybe on release 70, I'm not actually certain.

When the color selector is open, the cpu usage starts to jump. In these days of high heat, with some cooling issue, this may be problematic.

Anyway if you could put that somewhere in in your backlog, it would be greatly appreciated.


On a more joyful note, thanks for the multiple layer support. I could progress greatly with my wet skin shader.

Also, if you could add a node name selector for the templating system, based on the DAZ current surface, that would be great. Some hair makers like OutOfTouch have a repetitive shading system for their hair, that could be easily put into a template if we could access the current surface node names.

[Hun73rdk_1]

Another great update, lots of new nodes and improvements to use!
Time to work on version 11 of my skin material I think.

Thank you!

Do you ever share your skin material ??

No, not the material itself, I've had people steal parts/ideas from this forum before and put them into the next version of their paid product without even a mention, credit or thank you.
I'm always open to questions though.
I'm currently working out a good way to use micro skin detail maps like the ones used by Daz 8.1 characters using the new nodes we now have. I've got normal maps working without quality loss, roughness maps are next and I'll post my method here when I'm done. However, I just lost some of my progress due to the crash bellow


Clicked the add input button in one of the new nodes and got this crash:

Click-add-pin-button-crash.png

Historically Access Violation crashes have been somewhat common when clicking/doing things in the plugin, so I'm not sure if this is related to the new add input button specifically or is just a general crash from clicking something.

I am sorry to hear that, i hate when people just take peoples stuff and sell on.
But i can pay for the skin shader to use in renders

[toby_a]

Clicked the add input button in one of the new nodes and got this crash:

Click-add-pin-button-crash.png

Historically Access Violation crashes have been somewhat common when clicking/doing things in the plugin, so I'm not sure if this is related to the new add input button specifically or is just a general crash from clicking something.

Ah, sorry about that! I'll have a double check in this area. Thanks for reporting.

[toby_a]

Hello, I noticed a weird behavior starting maybe on release 70, I'm not actually certain.

When the color selector is open, the cpu usage starts to jump. In these days of high heat, with some cooling issue, this may be problematic.

Anyway if you could put that somewhere in in your backlog, it would be greatly appreciated.

Hmm, that is strange. Just to make sure I'm looking in the right place, can you please post a screenshot of the color selector that causes this issue?

On a more joyful note, thanks for the multiple layer support. I could progress greatly with my wet skin shader.

Also, if you could add a node name selector for the templating system, based on the DAZ current surface, that would be great. Some hair makers like OutOfTouch have a repetitive shading system for their hair, that could be easily put into a template if we could access the current surface node names.

Sorry for being a bit slow, but I don't understand what you're asking for here! What is a "node name" in this context? And how would you use it in an Octane material?