Version 4.0-RC7-R4 (obsolete release candidate) 10.11.2018

[rclassenphoto]

Hi,
what happens with Timeout is that Windows system instantly disable the GPU drivers, if it does not receive a signal after some seconds.
By default the TdrDelay is set to 2s, i.e. if one kernel call takes more than 2s, Windows kills the driver.
If you install the Standalone via installer, we change some Windows registry to better work with GPU Rendering.
To change the timeout, either run the Standalone installer or manually set the TdrDelay key to something like 10s or so. See here:

https://msdn.microsoft.com/en-us/librar ... s.85).aspx

In the Standalone installer we set these values:

WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrLevel 3
WriteRegDWORD HKLM "SYSTEM\CurrentControlSet\Control\GraphicsDrivers" TdrDelay 10jh

Some users have set the TdrDelay at 60, to solve their stability issues with CUDA.
ciao Beppe

i change this in the regedit but it does not effect anything.... the errors are more...

[Hatsize7]

Hi there!

I have a render failure problem with out of memory. Weird thing is that it happens while Octane live viewer shows that there is still plenty of VRAM available. (see screenshot).
In addition, the out of core option is enabled in Octane settings (16GB, 512mb).
System is Win 7, C4D R16, 32GB Ram, 3x GTX 1080. The scene is interior architectural scene with quite a lot of objects, but for this test I turned visibility off for most of the stuff, also vegetation turned off (multicloner, tree instances, etc)
Is this a common issue? Why does it show I still have 3.7GB free VRAM when it crashes?
Any optimization tips?

Thank you!

EDIT: I followed GIOLETS' suggestion here: viewtopic.php?f=30&t=69304, changing the TDR parameters and the problem went away. Thanks GIOLETS!

[aoktar]

Hi there!

I have a render failure problem with out of memory. Weird thing is that it happens while Octane live viewer shows that there is still plenty of VRAM available. (see screenshot).
In addition, the out of core option is enabled in Octane settings (16GB, 512mb).
System is Win 7, C4D R16, 32GB Ram, 3x GTX 1080. The scene is interior architectural scene with quite a lot of objects, but for this test I turned visibility off for most of the stuff, also vegetation turned off (multicloner, tree instances, etc)
Is this a common issue? Why does it show I still have 3.7GB free VRAM when it crashes?
Any optimization tips?

Thank you!

Possibly! Please disable monitoring gpu for render and try again.

[KeeWe]

I don't know if its relevant to the latest release, but I discovered the following:

I've 2 monitors and everytime i switch between layouts, the octane node editor window docked to one palette gets closed. For example:

Layout 1 has the node editor attached to one palette
Layout 2 has the node editor attached to another palette.

As soon as I switch from Layout 1 to Layout 2 I can see the docked node editor for 2 secnonds and after the whole Layout 2 is loaded, it disapaears and I have to redock the window.

Saving the layout after redocking, even to a layout 3, doesn't solve the problem.

Can this be Octane related?

Edit: I removed the node editor from layout 1, now layout 2 just loads as it should.

[VVG]

Ahmet, when we see new orbx loader? ))

[aoktar]

Ahmet, when we see new orbx loader? ))

In next release after stabile V4. Thanks for the interest.

[aybekdes]

Did you notice? Viewport rendering is much faster than preview window, at least on OS X

[Cheiser]

Octane cant handle 32m triangles. Will be stable verision handle this amount of polygons?

[aoktar]

Octane cant handle 32m triangles. Will be stable verision handle this amount of polygons?

It can handle as you have VRAM+RAM. I have gone more than 60m polygons.

[Cheiser]

Octane cant handle 32m triangles. Will be stable verision handle this amount of polygons?

It can handle as you have VRAM+RAM. I have gone more than 60m polygons.

I have 1070+1080 (both 8gb vram).
And 40gb RAM
Octane crashed

Cant share my scene
I just testing octane polycount capability