Camera offset does not match
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.
When using camera offset the Editor view and LV do not match (LV often has too much offset compared to Cinema's editor)
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Sample scene please?
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
when I have time...
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
I had some time:
http://imgur.com/a/t4mnU
Here's a gallery (I made the borders bright green and turned the grid off, so it's more obvious.
I'm on the latest standalone (3.03) and as of writing, the most current c4d plugin (3.03.3 R1).
Cinema 4D R17 .48 (not the very latest patch).
I've attached the file.
To me as far as I was playing with the film offset in the camera settings produced this result.
This effect (from my limited testing) only occurs with the Film Offset on Y and is not present with horizontal (X) offset.
Using the lens shift doesn't produce this effects simply because the effect is completely ignored by the editor view.
Hope this helps.
http://imgur.com/a/t4mnU
Here's a gallery (I made the borders bright green and turned the grid off, so it's more obvious.
I'm on the latest standalone (3.03) and as of writing, the most current c4d plugin (3.03.3 R1).
Cinema 4D R17 .48 (not the very latest patch).
I've attached the file.
To me as far as I was playing with the film offset in the camera settings produced this result.
This effect (from my limited testing) only occurs with the Film Offset on Y and is not present with horizontal (X) offset.
Using the lens shift doesn't produce this effects simply because the effect is completely ignored by the editor view.
Hope this helps.
- Attachments
-
- CameraOffset.zip
- Camera offset demo.
- (91.11 KiB) Downloaded 266 times
Well. Understood why it's diffent. Actually it's not a wrong calculation because offset values are correct. But Y size of rendering is bigger than viewport. It requires a revision on LV with unlocked resolution.
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
Reviving this issue as its causing huge problems on our current print prodution and its still not addressed (thanks dotjack for posting the example!)
I don't understand the reply Ahmet. It doesn't match the LV nor the Picture viewer. It doesn't work properly using the offset in the Octane camera tag either. In fact in that case the LV looks right but the picture viewer is wrong!
Thing is using camera offset throws the render regions out as well.
I don't understand the reply Ahmet. It doesn't match the LV nor the Picture viewer. It doesn't work properly using the offset in the Octane camera tag either. In fact in that case the LV looks right but the picture viewer is wrong!
Thing is using camera offset throws the render regions out as well.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Sending picture will help always. Could you please figure it by images+scenes what we are talking about exactly as my picture?sdanaher wrote:Reviving this issue as its causing huge problems on our current print prodution and its still not addressed (thanks dotjack for posting the example!)
I don't understand the reply Ahmet. It doesn't match the LV nor the Picture viewer. It doesn't work properly using the offset in the Octane camera tag either. In fact in that case the LV looks right but the picture viewer is wrong!
Thing is using camera offset throws the render regions out as well.
- Attachments
-
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
the other guy already did, it showed the issue and the values used.
try offsetting vertically by at least 30%
try offsetting vertically by at least 30%
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Very cryptic... I have no idea what this pic is supposed to be.
Is this any clearer?
Is this any clearer?
- Attachments
-
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Sorry attached wrong picture. I'm answering a lot people at same time. Here's correct one.sdanaher wrote:Very cryptic... I have no idea what this pic is supposed to be.
Is this any clearer?
- Attachments
-
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