TEST releases contain new features or substantial changes that, while expected to work, have not yet been proven stable.
PLEASE do NOT use them for important work and DO report any issues or suggestions as a reply to this post.
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
To use this version, you need a GPU of compute model 3.5 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 456.38 or higher.
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+ 2022.1.1 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. 2022.1.1_212) and subscription type (Studio+/Prime)
- 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.
Changes since 2022.1.1 - 212
- Redesigned material node value animation
This version includes a complete redesign of the way material properties can be animated. In previous versions, there was a way to define animations for material nodes in the node editor, but this did not work properly and has been removed.
The new way of animating material nodes is through the ability to create DAZ Studio properties linked to the nodes and to use the DAZ Studio timeline to create the animation.
In order to create animatable properties that show up in the Timeline pane, we need a DAZ Studio node in the scene to attach the properties to. For this reason, the plugin now creates a node in the scene for each Octane material. These are grouped under an "Octane Materials" group node and can be ignored most of the time. Be aware, though, that deleting these nodes will delete the corresponding Octane material as well.
To illustrate this, let's use a simple scene consisting of a sphere primitive. After creating the sphere, these are the DAZ Studio nodes in the scene:- scene_nodes.png (18.73 KiB) Viewed 3286 times
If you want to animate the value of a material node, that is to be able to have its value change as the scene time is changed, you first need to create a linked animatable property.
Only the following types of nodes can have a linked property:- Bool value
- Int value
- Float value
- Grayscale color
- RGB color
You can create a linked property by right-clicking the node in the node graph editor or the node background in the node editor.
Note that only expanded nodes can have linked properties. An expanded node is one that has its own box in the node graph editor. Nodes with linked properties are shown with a blue background in the node graph editor.
When a linked property is created, it is shown in the Parameters pane and can be found in the Timeline tab.
Once a linked property exists for a node, any changes made to the node's value are reflected in the property and vice versa. This means that editing the node's value using the Octane node editor will create an animation key at the current scene time. These automatically-created animation keys can be edited using the DAZ Studio Timeline pane.
To illustrate this, lets make our sphere change color over time. We have already created a property linked to the diffuse color node in the sphere's material, so all we have to do is to set different colors at a couple of different times and DAZ Studio will interpolate the color at intermediate times.
First, we set the color to red in frame 0:
Then, we set the color to green in frame 5:
This results in two animation keys being created for the linked property, at frames 0 and 5. Selecting a frame in between those frames will cause DAZ Studio to interpolate the color:
Please try this out and report any issues or suggestions.
Download Links
- For users with a Studio+ subscription license
For users with a Prime/Free Tier license
Please feel free to report any issues you encounter.
Happy rendering
Your OTOY team
