So that's a core problem. Maybe about environments.zamak wrote:At 16000 x 16000px for me
We'll look for that. Can you try a different way as clipping to small parts.
C4D crash to render 16000 x 16000px image
Moderators: ChrisHekman, aoktar
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
We'll look for that. Can you try a different way as clipping to small parts.
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
Yes i tested at different sizes. This is a core issue i suppose. Need to be reported to Otoy guys.zamak wrote:With c4d I can do a render at 11000px no problem, but from 12000px there is bug inside image or crash. Very strange....
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
As i can see you're using linear buffer so it has no vignetting. You can render it with a tiling script as 8k. I remember that was mentioned somewhere.zamak wrote:Do you mean render région? Because I have same bugs or crash for 16k rendering
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
Disable post-processing. Here it works, but post-processing takes a long time to calculate due to the image size and the large number of glare rays. At a resolution of 16K x 16K the post-buffers use 2.5GB on the device, and making the film buffer available on the device for tone mapping / post effects requires that 4x 1GB of memory are page-locked and mapped into device memory. All things together probably run into some limitation or time out.
In a nutshell: If you've got insane render sizes, don't use post-processing.
We are working on moving the whole tone mapping and post processing pipeline to the host (CPU), but until then the size for which you can apply post effects is limited.
In a nutshell: If you've got insane render sizes, don't use post-processing.
We are working on moving the whole tone mapping and post processing pipeline to the host (CPU), but until then the size for which you can apply post effects is limited.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
