Power, the viewport is updated nearly in realtime or within a few seconds only. Depending on the complexity of a scene and the available GPU Geometries, lighting and materials in a scene are sent immediately to the render engine. Unlike common renderers or rendering plugins, all changes to cameras,

OctaneRender for DAZ Studio is especially made to work interactively on a scene. Made available to the Standalone will usually appear in an updated Plugin version after a short period of time. OctaneRender™ for DAZ Studio™ supports almost all features of the Standalone, including graph-based Node editing. Only for SledgeHammer's New Gens for G8 I found a workaround ('Reload scene'), but the morphs are not comparable to Meipe's gens (and furthermore I've setup a bunch of default models with GP.), see SledgeHammer_Octane.png before and SledgeHammer_Octane_Reload_Scene.png after applying the workaround.This release requires DAZ Studio 4.5.0.114 and up, 32 or 64bit, on Windows XP, Vista, 7 and 8. New Genitalia for V8 seems to have a similar problem, see NG_V8_for_GF8_Octane.png.

GP8_Octane_Nodegraph_Editor.png shows the Nodegraph Editor setup for Octane in case somebody can spot at once a potential problem (even w/o knowing Octane):ī.t.w.

the problem is likely be caused by the shell. GP8_Octane_No_Shell.png shows GP with a hidden GoldenPalace_Shell, i.e. Copying material obviously doesn't help, as Octane converts the iRay material automatically. When using default Golden Palace (v2) with DAZ Studio (v.4.12b on Windows 10 Pro 64bit) and Octane Render (2019.1), the GoldenPalace_Shell material setup seems to make problems. Seems I'm struggling with the same problems as described in t=224016#post436777:

Daz3d octane render