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!
Version 4.0-RC7-R4 (obsolete release candidate) 10.11.2018
Moderators: ChrisHekman, aoktar
Possibly! Please disable monitoring gpu for render and try again.Hatsize7 wrote: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!
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
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.
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.
6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068
In next release after stabile V4. Thanks for the interest.VVG wrote:Ahmet, when we see new orbx loader? ))
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
It can handle as you have VRAM+RAM. I have gone more than 60m polygons.Cheiser wrote:Octane cant handle 32m triangles. Will be stable verision handle this amount of polygons?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I have 1070+1080 (both 8gb vram).aoktar wrote:It can handle as you have VRAM+RAM. I have gone more than 60m polygons.Cheiser wrote:Octane cant handle 32m triangles. Will be stable verision handle this amount of polygons?
And 40gb RAM
Octane crashed
Cant share my scene
I just testing octane polycount capability
- Attachments
-
- photo_2018-11-22_13-43-11.jpg (11.81 KiB) Viewed 7717 times
Hi,
it seems that you have only ~4.5GB of VRAM available, so at least you can load less than ~20M polys, try to use Out-of-core geometry, if you have enough RAM.
ciao Beppe
it seems that you have only ~4.5GB of VRAM available, so at least you can load less than ~20M polys, try to use Out-of-core geometry, if you have enough RAM.
ciao Beppe


