OTOY Forums

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 search the forum 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) 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. - FIXED (please report any issues)
4) Some of the newer OctaneRender material and texture types are not supported. - FIXED (please report any issues)
5) VDB volume and volumetric spotlight nodes are not currently supported.

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

Important notes:
[*] The minimum NVIDIA driver version required is R528 (R572 for GeForce RTX50 Series)..

Network Rendering

For Network Rendering, you must use the OctaneRender Studio+ 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 Studio+ 2026.4 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

- The most important part of resolving a problem is being able to reproduce that problem. So please 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

• - Updated to latest Octane engine 2026.4 (viewtopic.php?t=85726)

Workflow to create OctaneVDB>Load the VDB via Parameters>Apply Volume medium>Render

The format of file names should be like this: the frame number should be padded by zeroes in front, and surrounded by dots. Like some_file.00014.vdb, some_file.00118.vdb, etc. Just select the first file of the sequence into a "VDB file" property.
There is one more property added to a new VDB node: "Frame offset". This may be needed if you have e.g. VDB-files' sequence starting with 0001, but your first frame to render is "0". In this case you set the frame offset to "1".







Please keep in mind, some VDB objects are really heavy for GPU-rendering. Thus, to not get your DAZ or other Windows processes crashed, it is a good idea to have additional GPU only dedicated for rendering, and all the GPUs that have monitors connected to them - completely disabled for rendering in Octane "Device Settings". Something like this:





FAQ
Q: How to change light brightness/color?
A: You need to assign a material to the light and adjust the emission of the material. You can do it either by dragging a material to the light in the Materials tab (similar to assigning materials to geometry) or by right clicking on the light and selecting menu item under "Create as new light source".


Q: How do I enable analytic light?
A: Create a point light (or linear point light, they are the same). Then turn on "use analytic light" in the OctaneRender settings.


Q: I selected "rectangle" light geometry, but light didn't change
A: "rectangle", "disc" and "cylinder" geometries are only supported for analytic lights

Q: I assigned emission material to the light, but it's still not visible
A: If the light is analytic, make sure the emission node is expanded (i.e. is a separate node, connected to emission pin). It's required for analytic lights to work.


Q: How to make light beams work?
A: 1) Set the light to be analytic, rectangle or disc shape, enable "use in post volume".
2) In render settings enable post processing and light beams


Download Links

• For users with a Studio+ subscription license
  • - OctaneRender for DAZ Studio 2026.4 - 410
  For users with a Prime/Free Tier license
  • - OctaneRender for DAZ Studio 2026.4 - 410

Please feel free to report any issues you encounter.




Happy rendering
Your OTOY team

Thanks for the update. Will test it with a few new scene along with some old one to confirm that are still viable.
Thanks for clarifying that this version is still for Daz Studio 4.x.

Tugpsx wrote: Wed Jul 15, 2026 2:28 am Thanks for the update. Will test it with a few new scene along with some old one to confirm that are still viable.
Thanks for clarifying that this version is still for Daz Studio 4.x.

Thank you Tugpsx,
Sure, it would help a lot.
Btw, could you also help test if enabling the `Line tessellation` on Strand-based Hair can render with OctaneRender for Daz?


cheers

Awesome, thank you. The tab in Studio says this is BETA. Will the final for this be coming soon?

Bugger, materials are not being transferred to the figure. All textures render white. I hope I've still got the previous version.

RGUS wrote: Wed Jul 15, 2026 4:08 am Awesome, thank you. The tab in Studio says this is BETA. Will the final for this be coming soon?

Ah thank you RGUS,
This is stable build.. We will change it in the next build..

cheers

BK wrote: Wed Jul 15, 2026 3:52 am Btw, could you also help test if enabling the `Line tessellation` on Strand-based Hair can render with OctaneRender for Daz?

Hi BK,

Thanks for the update! Great to finally be on the latest Octane release.

For rendering strand-based hair, what you stated here has always worked. If you increase the line tessellation to a value of 2 or higher the hair will show up in the Octane viewport (0 = curve, 1 = polyline, 2+ starts to generate polygons per strand). However, this method (IMO) has two big problems -

1) Since this generates a polygonal surface and not a curve, it doesn't work well with the Octane Hair Material, making shading very challenging <- this is the biggest disadvantage vs Iray currently

2) Although Octane handles the geometry fine, performance of the Daz viewport gets pretty bad when tessellating denser hair styles. Combine this with a lot of people using HD morphs on characters and the geometry count can be very challenging for users wth lower RAM/VRAM setups. When strand-based hair is kept as curves (0 line tessellation) there is very little performance impact on the Daz viewport.

Ideally we can have some way to get the curves into the Octane viewport for better shading and performance reasons (or something similar to how we can import alembic hair into octane standalone and have the options for setting strand width, etc).

BK wrote: Wed Jul 15, 2026 3:52 am

Tugpsx wrote: Wed Jul 15, 2026 2:28 am Thanks for the update. Will test it with a few new scene along with some old one to confirm that are still viable.
Thanks for clarifying that this version is still for Daz Studio 4.x.

Thank you Tugpsx,
Sure, it would help a lot.
Btw, could you also help test if enabling the `Line tessellation` on Strand-based Hair can render with OctaneRender for Daz?


cheers

When Viewport Line Tessellation is set to 2, This updo strand-base hair was visible in the Octane Viewport.
Since octane is not using the Render Line Tessellation, there is no need to change the value from 1.
https://www.daz3d.com/dforce-strand-based-fe-layered-updo-hair-for-genesis-98-and-81

huakiami wrote: Wed Jul 15, 2026 4:33 am

BK wrote: Wed Jul 15, 2026 3:52 am Btw, could you also help test if enabling the `Line tessellation` on Strand-based Hair can render with OctaneRender for Daz?

Hi BK,

Thanks for the update! Great to finally be on the latest Octane release.

For rendering strand-based hair, what you stated here has always worked. If you increase the line tessellation to a value of 2 or higher the hair will show up in the Octane viewport (0 = curve, 1 = polyline, 2+ starts to generate polygons per strand). However, this method (IMO) has two big problems -

1) Since this generates a polygonal surface and not a curve, it doesn't work well with the Octane Hair Material, making shading very challenging <- this is the biggest disadvantage vs Iray currently

2) Although Octane handles the geometry fine, performance of the Daz viewport gets pretty bad when tessellating denser hair styles. Combine this with a lot of people using HD morphs on characters and the geometry count can be very challenging for users wth lower RAM/VRAM setups. When strand-based hair is kept as curves (0 line tessellation) there is very little performance impact on the Daz viewport.

Ideally we can have some way to get the curves into the Octane viewport for better shading and performance reasons (or something similar to how we can import alembic hair into octane standalone and have the options for setting strand width, etc).

Thanks for the write-up. Daz Octane was designed to pull the geometry from the viewport and as stated when the strand based hair (SBH) is visible in the Daz viewport, it is made visible in the Octane Viewport. Loading an Alembic hair like Octane standalone would present several problems including higher VRAM requirements.

Alembic hair is baked hair, the simulation has already been completed. Most strand based hair is dforce hair for simulation, once simulated in DS it could be frozen, but that presents another problem for animations where a dynamic movement is desired. Adding a Tessellation option to the Octane controls was something that was discussed, but it is an after geometry capture problem. The old octane plugin was designed to capture obj geometry from the viewport, later an Alembic style capture was implemented (allows for animation). This has been a difficult process for animated SBH.

One of the interesting things is that most iRay users can’t see the iRay STB in viewport, but have come to expect it in Octane viewport. We can investigate an option to show the hair once a pose or motion frame has completed simulation. More for discussion.

Hi Tugpsx,

Thanks for your reply, but I don't understand some of your statements:

Tugpsx wrote: Wed Jul 15, 2026 11:51 am ...Daz Octane was designed to pull the geometry from the viewport and as stated when the strand based hair (SBH) is visible in the Daz viewport, it is made visible in the Octane Viewport...

...One of the interesting things is that most iRay users can’t see the iRay STB in viewport, but have come to expect it in Octane viewport...

In the latest version of DazStudio supported by the Octane plugin (4.24), you can see strand-based hair in the Daz/Iray viewports regardless of tessellation level. If it's set it to 0 you see the curves, 1 you see the polylines, 2+ you'll see the polygons. So I don't understand your statement that "most users" can't see it in Iray but are expecting to see it in Octane. Ever since Daz added support for curve rendering (4.20.1.20 I think) we pretty much always see the hair in the Daz/Iray viewports, so the opposite of what you're saying is actually true.

Also I understand that the simulation component adds additional challenge, but I think just being able to render strand-based hair as curves (supporting Octane Hair Material) - even if in a static state - would be an improvement for many plugin users. A lot of Daz vendors release strand-based hair products with bones even though it's designed to be simulated - so you would still have some posing / art direction ability and it would be a good first step.

Back when Toby Allsopp was working for OTOY on the Daz plugin he built an experimental version that allowed you to edit the Octane node tree directly. While it was relatively unstable and had issues, it allowed us to render VDBs in the plugin years before the recent support for them was added and you could also load an alembic hair. I'm not saying that's the exact solution we need but it was at least a theoretical proof of what's possible.