Changing focal length wrecks DOF on all octane 2024 scenes

Sub forum for bug reports

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.
Post Reply
boxfx
Licensed Customer
Posts: 275
Joined: Fri Apr 27, 2012 9:13 am

Project attached

Adjusting the focal length of any camera created in octane 2024, using octane 2025, causes the Aperture value in the octane camera tag to change. This breaks all DOF settings on any project older than a few weeks.

Specifically the bug is that any older scene which had the fstop set to INF, and therefore the aperture set to 0, will instead load in with the fstop set to 2.8 and the aperture set to 0. An invalid combination. As soon as the user changes the focal length of the camera, the aperture jumps into action and starts changing, introducing DOF when the original scene file had no DOF at all.

octane 2025.1.0 0104
c4d 2025.2.1
win 11
Attachments
old octane cam scene.zip
(65.71 KiB) Downloaded 8 times
DinoMuhic
OctaneRender Team
Posts: 191
Joined: Wed Mar 25, 2015 10:24 pm

boxfx wrote: Thu May 08, 2025 3:01 pm Project attached

Adjusting the focal length of any camera created in octane 2024, using octane 2025, causes the Aperture value in the octane camera tag to change. This breaks all DOF settings on any project older than a few weeks.

Specifically the bug is that any older scene which had the fstop set to INF, and therefore the aperture set to 0, will instead load in with the fstop set to 2.8 and the aperture set to 0. An invalid combination. As soon as the user changes the focal length of the camera, the aperture jumps into action and starts changing, introducing DOF when the original scene file had no DOF at all.

octane 2025.1.0 0104
c4d 2025.2.1
win 11
Hi can you check if this is still happening for you in the latest v1.5 build?
boxfx
Licensed Customer
Posts: 275
Joined: Fri Apr 27, 2012 9:13 am

Problem seems fixed in 2025.2, will update if it happens again
Post Reply

Return to “Bug Reports”