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

[rajib]

I have updated the installer at the top of this thread with:

3.4.5.29
- Compiled with Octane 3.04.5
- Fixed crash that was occurring for some users when they clicked the "..." button to open the Image Browser

Paul

Thanks Paul . Confirmed the image browser opens correctly without issue in the 3.4.5.29. Now if the scattering node issue and the switching between scenes issue can be resolved in the next release that would be great !

[face_off]

One more issue. If you keep switch between scenes using the "File->Open / Open Recent" menu, sooner or later the Octane Viewport will stop loading and reload / rebuild does not help. If the scene had an daylight environment with a sky map, only the sky map will load but nothing else. In the System tab it shows:

02:48:01.518: +++++ Plugin running.
02:48:53.039: Node type 20 is either unknown, a linker or incompatible to dynamic pin '_2' (type PT_OBJECTLAYER) of node 'sphere' (NT_GEO_MESH, 000000007696D5E0)
02:48:53.361: Node type 20 is either unknown, a linker or incompatible to dynamic pin '_2' (type PT_OBJECTLAYER) of node 'sphere' (NT_GEO_MESH, 000000007696D5E0)

I was just testing with 2 scenes files. One had Cube instances (the one I attached for the instances problem) and another had just one sphere. I load one of them and then clicked the open menu item to load the other. The octane viewport had the running orange bar and nothing loaded. Sometimes it would happen the first time. Somethings it took a couple of switching between the scenes to recreate the issue. But each time it had a similar error in the log.

I could not reproduce this error. Can you pls send me two simple scenes which will give you this error, and also provide a screenshot of the Preferences tab of your plugin.

Thanks

Paul

[rajib]

I could not reproduce this error. Can you pls send me two simple scenes which will give you this error, and also provide a screenshot of the Preferences tab of your plugin.

Hi Paul,

My preferences tab settings are :

Preferences Tab

Attached is the zip file containing the 2 scenes files that I can sue to recreate the issue. Steps to recreate :
1. Open Daz Studio and load the cubeinstancestest.duf.
2. Open the Octane Viewport (This is important). All looks okay (Ignore the instances not showing up - Haven't yet updated to the experimental plugin yet)

Open CubeInstancesTest.duf

3. Once it is loaded click File->Open and open the CircleTest.duf. You can say 'No' to save changes for the cubeinstancestest.duf.
4. Immediately you should see the error in the Systems Tab and the Octane Viewport will have the running orange bar.

Open CircleTest.duf

Error shown in the Octane System Tab

5. If I click rebuild scene, it shows 'Waiting...' on the Octane Viewport

Waiting... After clicking Rebuild Scene

Interestingly this only happens if the Octane Viewport is open when the File->Open / Open Reset is used to open a new scene. If I close the Octane Viewport before opening the new scene file, the error does not appear and then if I open the Octane Viewport it will open properly and render. So looks like when switching between scenes while the Octane Viewport is open causes some kind of initialization error in the plugin.

Regards,
Rajib

[ertrax]

"3.4.5.29 (27-Nov-2016)
- Compiled with Octane 3.04.5
- Fixed crash that was occurring for some users when they clicked the "..." button to open the Image Browser"

Thanks !!!

[face_off]

Interestingly this only happens if the Octane Viewport is open when the File->Open / Open Reset is used to open a new scene. If I close the Octane Viewport before opening the new scene file, the error does not appear and then if I open the Octane Viewport it will open properly and render. So looks like when switching between scenes while the Octane Viewport is open causes some kind of initialization error in the plugin.

Thank you for the detailed info you have given. I have tracked the error down, but not yet able to find a solution. In summary, DAZStudio will tell the plugin the following:

1) when it is loading a .duf scene file (in which case the plugin needs to be ready to load the Octane info from the .duf file), AND

2) when it is clearing the DAZStudio scene (in which case the plugin needs to clear the Octane scene).

HOWEVER.....when you have a scene already loaded, and you load a new .duf scene, DAZStudio sends the "scene clearing" event AFTER the "scene loading" event. IMO this is the wrong way around, since the scene will always be cleared prior to loading a new .duf. There is a lot of code in the plugin to try to get around this issue, and I think there is a bug in that code causing the problem.

I will try to find a solution.

Paul

[rajib]

HOWEVER.....when you have a scene already loaded, and you load a new .duf scene, DAZStudio sends the "scene clearing" event AFTER the "scene loading" event. IMO this is the wrong way around, since the scene will always be cleared prior to loading a new .duf. There is a lot of code in the plugin to try to get around this issue, and I think there is a bug in that code causing the problem.

I will try to find a solution.

Thanks Paul. Will wait for it. In the meantime I will ensure I close the Octane Viewport before loading the new scene.

[face_off]

Attached is a highly experimental release which tries to fix the problem reported above by Rajib. I found it worked well when loading new scenes, but I got mixed results when Merging scenes.

3.5.0.30
- Compiled with Octane 3.05
- Added support for Instances Groups - so UltraScatter and Voxelizer scenes should now work
- Fixed issue where loading or merging a scene whilst the current scene is rendering would cause the Octane Viewport to step rendering in some situations - requiring a DAZStudio restart

LINK REMOVED

Paul

[rajib]

Attached is a highly experimental release which tries to fix the problem reported above by Rajib. I found it worked well when loading new scenes, but I got mixed results when Merging scenes.

3.5.0.30
- Compiled with Octane 3.05
- Added support for Instances Groups - so UltraScatter and Voxelizer scenes should now work
- Fixed issue where loading or merging a scene whilst the current scene is rendering would cause the Octane Viewport to step rendering in some situations - requiring a DAZStudio restart

Paul

Thanks Paul . Just downloaded it. Will run through my test scenes to see if I encounter any problems.

[rajib]

Attached is a highly experimental release which tries to fix the problem reported above by Rajib. I found it worked well when loading new scenes, but I got mixed results when Merging scenes.

3.5.0.30
- Compiled with Octane 3.05
- Added support for Instances Groups - so UltraScatter and Voxelizer scenes should now work
- Fixed issue where loading or merging a scene whilst the current scene is rendering would cause the Octane Viewport to step rendering in some situations - requiring a DAZStudio restart

Paul

Thanks Paul . Just downloaded it. Will run through my test scenes to see if I encounter any problems.

Hi Paul,

I have done multiple rounds of scene loading without closing the existing scene and it has worked so far without any issue. I tested with simple as well as complex scenes. In some instances it took a while to for the automatic closure of the Octane window (Complex scenes). But in all cases I was able to open the Octane Viewport for the new scene after it was automatically closed and the render continued for the new scene. I will do some testing with the merging of the scenes and report back on that tomorrow.

Regards,
Rajib

[rajib]

Hi Paul,

While testing the experiential release (3.5.0.30) I have found another issue that has been there before in all the release. It is something to do with the local or world transform I think.

Take a look at the below DAZ Viewport and Scene tab and the Octane Viewport. In DAZ I have enabled the Region Navigator tool so that the selected node is clearly visible in orange outline. It shows the ivy (mrIvy014) is selected and it is actually a child node of the mrTree04. In the Daz viewport you can see the ivy is attached to the tree (mrTree04) but in Octane they ivy is rendering separately from the tree and it is split in 2 parts. The Orange marker highlights the tree position and the red marker highlights the ivy position.

Daz Viewport - Ivy child of Tree

Octane Viewport - wrong ivy placement

If I turn of the visibility off the ivy (mrIvy014) in the Daz viewport, the 2 split ivy in the Octane viewport are also not rendered.

Daz Viewport - ivy hidden

Octane Viewport - ivy hidden

The ivy (mrIvy014) is a normal node and not an instance node. I think its local / world coordinates is being wrongly calculated by the octane plugin. I will send you the scene file through PM. Hopefully you will be able to track this one down too. Btw. I did render the scene in Iray too and found octane was showing a lot more spread of the plants than Iray. e.g. in Iray the center of the scene has no plants but in Octane it is filled with plants. So not sure if that is also related to the wrong coordinate calculations. Once you open the scene file and render in both Iray and Octane you will be able to see the difference.

Regards,
Rajib