When Use F-stop is disabled and aperture slider is used both render views are the same.
Use F-stop issue in 28.1x
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)
When Use-F-stop is enabled in Octane camera settings the render preview and final render has different levels of lens blur. Preview has less while final render has more blur.
When Use F-stop is disabled and aperture slider is used both render views are the same.
When Use F-stop is disabled and aperture slider is used both render views are the same.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
-
linograndiotoy
- Posts: 1354
- Joined: Thu Feb 01, 2018 7:10 pm
I can't reproduce the issue on a scene I made.
Can you please share a very simple scene showing it? Thanks.
Can you please share a very simple scene showing it? Thanks.
Here is the file with the issue.
- Attachments
-
- fstop issue.blend
- (1.15 MiB) Downloaded 36 times
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
Still not fixed in 28.13
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
-
linograndiotoy
- Posts: 1354
- Joined: Thu Feb 01, 2018 7:10 pm
From the developer:
"This "f-stop" difference is a limitation.
Why the "f-stop" produces different blur effect?
Basically, in Octane, the final "dof" blur effect is determined by the "Aperture" value. So the preview and final render produce the same results when using the "Aperture".
When the "f-stop" is used, Octane calculates the "Aperture" based on the focal length and f-stop. The f-stop is exactly the same. But the focal length has to be modified between preview and final render, which results in a different "Aperture" and "dof" blur effect.
Why the focal length has to be changed?
Briefly, it's caused by the change of the FOV. In Octane, the focal length and FOV are synced. When we change the FOV, the focal length is changed too.
And the FOV is different between preview and final render as the resolution is different. The preview resolution is determined by the viewport while the final render is determined by the "Resolution" property.
So the focal length in Octane is different in Octane. All of those leads to a different "Aperture" and blur effect.
I can implement a f-stop to aperture converter in the code. No matter whether users enable "use f-stop", we will convert them to "aperture" in all cases. (it seems to be how Cycles does it).
But this way breaks backward compatibility. So I can provide a new option for users to decide whether they want to use the new mode."
We'll go for the new option.
"This "f-stop" difference is a limitation.
Why the "f-stop" produces different blur effect?
Basically, in Octane, the final "dof" blur effect is determined by the "Aperture" value. So the preview and final render produce the same results when using the "Aperture".
When the "f-stop" is used, Octane calculates the "Aperture" based on the focal length and f-stop. The f-stop is exactly the same. But the focal length has to be modified between preview and final render, which results in a different "Aperture" and "dof" blur effect.
Why the focal length has to be changed?
Briefly, it's caused by the change of the FOV. In Octane, the focal length and FOV are synced. When we change the FOV, the focal length is changed too.
And the FOV is different between preview and final render as the resolution is different. The preview resolution is determined by the viewport while the final render is determined by the "Resolution" property.
So the focal length in Octane is different in Octane. All of those leads to a different "Aperture" and blur effect.
I can implement a f-stop to aperture converter in the code. No matter whether users enable "use f-stop", we will convert them to "aperture" in all cases. (it seems to be how Cycles does it).
But this way breaks backward compatibility. So I can provide a new option for users to decide whether they want to use the new mode."
We'll go for the new option.
Thanks for the information!
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group