On a machine with 2 monitors connected, set your primary monitor to 125% windows scaling and the other monitor to 100% window scaling.
Open c4d on the main 125% screen
open octane live view on the second screen
Open any project
start the live view render
Select a region to render in the live view
In the c4d render settings, under the octane page, enable render region and click the button to copy the current region
Render to picture viewer
Bug: The region rendered to the final image will not match the live view. As a bonus, if you move the live view from the 100% monitor to the 125% monitor, the render region will jump to the correct location as the window passes to the other screen
octane 2025.2.0 b1.5
c4d 2025.3.3
4090
driver 576.02
Dual screen render regions incorrect
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.
Hi,
Do you mind to try with latest 2025.3-v1.7.1 and report back?
https://render.otoy.com/customerdownloads/plugins/0d/d0/9b/28/OctaneRender_Studio%2B_2025.3_for_Cinema4D_v1.7.1.exe
ciao,
Beppe
Do you mind to try with latest 2025.3-v1.7.1 and report back?
https://render.otoy.com/customerdownloads/plugins/0d/d0/9b/28/OctaneRender_Studio%2B_2025.3_for_Cinema4D_v1.7.1.exe
ciao,
Beppe