OTOY Forums

Pls read http://poserphysics.blogspot.com.au/2016/03/before-you-submit-octane-support.html prior to posting support issues.

NOTE 1: For users who experience a DAZStudio crash - deleting C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb may resolve the issue.

NOTE 2: For users having an issue where the Save button is disabled if 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.

NOTE 3: For users having an issue where rendering an animation fails after 11 frames - make sure the DAZStudio viewport is visible when you render the animation.

NOTE 4: 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 1 above.

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

DAZ Studio Version
DAZ Studio 4.8 or later on Window Vista, 7, 8 or 10 64bit

Nvidia Driver Version
Nvidia drivers 392.x or later

Network Rendering
For Network Rendering, you must use the Octane slave release from the Octane Standalone installer which matches the exact Octane version of the plugin you are using.

If you have a support issue, pls provide the following information:
- Operating System (ie. Win XP, Vista, 7, 8)
- Amount of RAM
- Graphics Card(s) - model (ie. GTX 580, 3GB)
- Nvidia driver version
- DAZ Studio version
- OctaneRender for DAZ Studio version (ie. 2.24.2.1)

- The most important part of resolving a problem is me being able to re-produce 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.

Download Links

Latest TEST build (Octane 4.00 RC6)
- Regular - OctaneRender for DAZ Studio 4.00.0.40 (64 bit) UPDATED
- Subscription - Not yet available

Release Notes

4.00.0.40 (23-Oct-2018)
- Compiled with Octane 4.00 RC6
- Removed the GPU Throttling option
- Removed the Restart Driver option
- Added Open Device Settings button to the System tab
- Added Denoiser pins to the Imager Settings. Enabling Denoising then enabled the viewing of the De Main render pass (once the denoising pass has commenced)0
- Kernel->Light ID's are not working correctly
- Added additional Octane 4.00 render passes
- Added Kernel AI Light options

Paul

Yo thanks! Cant wait to try this when I get home.

Just saw this Paul. Thanks

! Will give it a try. I need to get my 2080TI to be recognized by the plugin.

Hi Paul,

Just tried it. My 2080 TI was recognized !

Noticed something in Render Window : it is rendering, but the top area has the running yellow bar and the status shows Waiting...

Will update if I see something else.

Regards,
Rajib

rajib wrote:Hi Paul,

Just tried it. My 2080 TI was recognized !

Noticed something in Render Window : it is rendering, but the top area has the running yellow bar and the status shows Waiting...

Will update if I see something else.

Regards,
Rajib

Yes, same here, no way of knowing when the render has finished unless you leave it as long as an iRay render would take... like... for-eve-ver.

rajib wrote:Hi Paul,

Just tried it. My 2080 TI was recognized !

Noticed something in Render Window : it is rendering, but the top area has the running yellow bar and the status shows Waiting...

Same here.




- - -

Can the Planetary Environment be supported in the DAZ Studio plugin?
Or will it fall under the same limitations as the not available Visible Environment options like backplate, reflections and refractions?

Noticed something in Render Window : it is rendering, but the top area has the running yellow bar and the status shows Waiting...

Thanks for reporting this. You are right - this is an issue. This will be quite difficult to fix, so will take some time to resolve.

Can the Planetary Environment be supported in the DAZ Studio plugin?
Or will it fall under the same limitations as the not available Visible Environment options like backplate, reflections and refractions?

Yes, in the short term it will be unsupported as per the Visible Environment, but it is on the long-term list for implementation.

Paul

Hi Paul,

Got the following error while basically switching between Octane tab and the Daz Viewport. Btw. Every time I switched from the Octane Pane to the Daz Viewport, the Octane render window would hang for a few seconds and then continue rendering. This happened a couple of times and then it stop rendering and I saw the following in the System Tab. I was also editing the Materials in the NGE on and off.

10:18:35.123: +++++ Plugin running.
11:01:06.956: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:06.958: -> failed to download symbol(stats data)
11:01:06.960: device 0: path tracing kernel failed
11:01:07.016: CUDA error 700 on device 1: an illegal memory access was encountered
11:01:07.016: -> failed to wait for event
11:01:07.016: device 1: path tracing kernel failed
11:01:07.016: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.016: -> failed to set texture format(__data24__)
11:01:07.016: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.017: -> failed to set texture format(__data26__)
11:01:07.017: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.017: -> failed to set texture format(__data29__)
11:01:07.017: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.017: -> failed to set texture format(__data30__)
11:01:07.017: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.017: -> failed to set texture format(__data27__)
11:01:07.018: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.018: -> failed to deallocate device memory
11:01:07.018: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.018: -> could not get memory info
11:01:07.019: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.019: -> failed to deallocate device memory
11:01:07.019: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.019: -> could not get memory info
11:01:07.019: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.019: -> failed to deallocate device memory
11:01:07.019: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.020: -> could not get memory info
11:01:07.020: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.020: -> failed to deallocate device memory
11:01:07.020: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.020: -> could not get memory info
11:01:07.021: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.021: -> failed to deallocate device memory
11:01:07.021: CUDA error 700 on device 0: an illegal memory access was encountered
11:01:07.021: -> could not get memory info
11:01:07.021: Render engine failure occured! (WARNING)
11:01:07.022: CUDA error 700 on device 2: an illegal memory access was encountered
11:01:07.066: -> failed to wait for event
11:01:07.066: device 2: path tracing kernel failed
11:01:11.157: Render engine failure occured! (WARNING)
11:01:14.156: Render engine failure occured! (WARNING)



Regards,
Rajib

Hi Paul,

I can report, the Octane Viewport does hang for a few seconds when one moves around the NGE / Other Octane Tabs and the Daz Viewport like I had report in my earlier post. I saw the same effect as I was testing today. I think a few of these finally crashes the graphics driver. So continuations editing with the Live button enabled, basically leads to errors.

Regards,
Rajib