C4D viewport renders work perfectly fine, and so does the live viewer window. I am only rendering @720p with direct lighting (500 samples)
I am using depth of field if that makes a difference
here is what happens in picture viewer
Rendering Not Working (Octane VR for C4D)
Moderator: juanjgon
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
]So whenever I try to do a render in the picture viewer, all I get is a black image, and down below it says "updating.." until about 40 seconds later when it stops.
C4D viewport renders work perfectly fine, and so does the live viewer window. I am only rendering @720p with direct lighting (500 samples)
I am using depth of field if that makes a difference
here is what happens in picture viewer vs what happens in viewport render My octane version is OctaneVR 3.06.2 and c4d is R16 Studio
C4D viewport renders work perfectly fine, and so does the live viewer window. I am only rendering @720p with direct lighting (500 samples)
I am using depth of field if that makes a difference
here is what happens in picture viewer vs what happens in viewport render My octane version is OctaneVR 3.06.2 and c4d is R16 Studio
Windows 10 | GTX 980 Ti + GTX 1060 3GB | Xeon W5590 x2 | 32gb DDR3 1333mhz
Hi fedoragfx,
please, refer to the Maxon Cinema 4D section of the Otoy forum, when you have questions about c4doctane:
viewforum.php?f=30
Please, go to c4d menu Script/Console and post a screenshoot of the output log.
More likely you have different settings in Hyper Nurds objects between rendering preview, Live View, aand finalnrendering, Picture Viewer:
Performance Tricks and Pitfalls on Renderings
Decrease the subdivision to reduce the polygon count, your GPU has not to much VRAM to working with.
You can also decrease the Parallel Sampling to 1 in the kernel settings, to have a bit more of free VRAM, but the rendering speed is also reduced.
With more system RAM, you can also enable the Out-of-core option, in order to move all the textures in scene from VRAM to RAM, and have more space for geometry, but 8GB are not enough:
Out-of-core
And last, but not least, Win 10 has a known issue with available VRAM:
viewtopic.php?f=12&t=51992
ciao beppe
please, refer to the Maxon Cinema 4D section of the Otoy forum, when you have questions about c4doctane:
viewforum.php?f=30
Please, go to c4d menu Script/Console and post a screenshoot of the output log.
More likely you have different settings in Hyper Nurds objects between rendering preview, Live View, aand finalnrendering, Picture Viewer:
Performance Tricks and Pitfalls on Renderings
Decrease the subdivision to reduce the polygon count, your GPU has not to much VRAM to working with.
You can also decrease the Parallel Sampling to 1 in the kernel settings, to have a bit more of free VRAM, but the rendering speed is also reduced.
With more system RAM, you can also enable the Out-of-core option, in order to move all the textures in scene from VRAM to RAM, and have more space for geometry, but 8GB are not enough:
Out-of-core
And last, but not least, Win 10 has a known issue with available VRAM:
viewtopic.php?f=12&t=51992
ciao beppe