OctaneRender™ 2020.2.5 [current 2020.2]

by **mojave** » Mon Aug 09, 2021 12:40 am

Hi all,

This is a new maintenance release to sort out some problems found in 2020.2.4.

You can find an overview of the changes between 2020.1.5 and 2020.2 in the release notes of 2020.2.

Make sure to use a NVIDIA Studio driver with version at least 456.38 on Windows or 455.23 on Linux to use this version. No driver updates are required for macOS 10.13 (CUDA).

This version supports the NVIDIA Ampere architecture (compute model 8.x) on Windows and Linux. As a consequence, Kepler GPUs with a compute model lower than 3.5 are only supported on macOS (which does not have Ampere support) and needed to be discontinued on Windows and Linux.

Changes since OctaneRender 2020.2.4:

Bugfixes:

Fixed issue causing some textures to be interpreted differently when using out-of-core.
Fixed application crash during startup.
Fixed SSS pass which was causing a difference between the main pass and the denoiser output passes.
Fixed issue with scenes with render layers and alpha channel enabled causing incorrect denoiser output.
Fixed universal camera diopter rotation to be interpreted as degrees instead of 0-1. (viewtopic.php?f=24&t=77888&p=402830#p402830)
Fixed broken rotation for 2D transforms.
Fixed an issue causing a freeze when disabling RTX while tone-mapping was happening.

by **Kalua** » Sun Aug 15, 2021 2:12 pm

Thanks, team!
Regrds,

by **PolderAnimation** » Tue Aug 31, 2021 2:10 pm

When I adjust the focal length my aperture changes also. Why is that?

by **elsksa** » Tue Aug 31, 2021 3:04 pm

PolderAnimation wrote:When I adjust the focal length my aperture changes also. Why is that?

Simply said, the "longer" the focal length, the shallower the background "depth" will appear, while the aperture remains to the same value - reciprocally, the wider the focal length, the less "lens compression" of the background, thus the "lens blur" will appear more subtle.

arri_signature_prime_lenses.jpg

Could it be related to this "normal behavior" or are you suggesting an actual bug? A screenshot/video (uploaded to a website such as https://streamable.com) would help understand better and technically, the issue you are facing.

by **PolderAnimation** » Wed Sep 01, 2021 8:08 am

elsksa wrote:
PolderAnimation wrote:When I adjust the focal length my aperture changes also. Why is that?

Simply said, the "longer" the focal length, the shallower the background "depth" will appear, while the aperture remains to the same value - reciprocally, the wider the focal length, the less "lens compression" of the background, thus the "lens blur" will appear more subtle.

arri_signature_prime_lenses.jpg

Could it be related to this "normal behavior" or are you suggesting an actual bug? A screenshot/video (uploaded to a website such as https://streamable.com) would help understand better and technically, the issue you are facing.

Yeah I understand but not everything you want to create is 100% accurate. To have control over the aperture nice to have. I think it is a bug because you can adjust the aperture separately, but when you save your file and re-open it the file it is set to a different value. (I don't think that is suppose to happen).

Attached a file.

by **funk** » Wed Sep 01, 2021 10:15 am

PolderAnimation wrote:Yeah I understand but not everything you want to create is 100% accurate. To have control over the aperture nice to have. I think it is a bug because you can adjust the aperture separately, but when you save your file and re-open it the file it is set to a different value. (I don't think that is suppose to happen).

This looks like a design choice rather than a "bug".

You can see that when Focal Length is changed, Octane is trying to keep F-Stop consistent. The only way to do this is to change Aperture to balance the formula.

Formula (thanks to google):

Code: Select all: F-Stop = Lens Focal Length (mm) / Aperture Diameter (mm)

If you want to keep a constant Aperture, Octane allows you to adjust the "Field of View" instead. This will change your Focal Length and F-Stop, rather than Aperture.

NOTE: They could probably provide an option to have Focal Length adjust F-Stop instead, and Field of View to adjust Aperture, but they may have felt it wasn't needed.

EDIT: Fixed typos...

by **elsksa** » Wed Sep 01, 2021 3:30 pm

I do not think changing the current behavior would be needed.
In Octane, the field of view (measured in degrees) changes the F-stop value accordingly.

In real-world, a set of cinema prime lenses often have 3/4 of the lenses from the set with matching T-stop (T because it, simply said, relates to light transmission which is important to match in terms of exposure-consistency).

The current behavior (changing the "Focal length" in Octane) is similar to changing a prime lens on-set with an other lens from the same prime lenses set ("pack"), with the same T-Stop, e.g T3.0 (roughly equivalent of F/2.8).

As funk mentioned, it is rather a design-choice, which makes sense. Either way, it is possible to have the necessary controls to "break" the expected "real world" behavior, so to speak.

by **roeland** » Wed Sep 01, 2021 11:22 pm

The inputs on the camera work as two groups:

If you update the physical camera parameters (Sensor width, Focal length, F-stop) then Octane will update the other related inputs.

If you update Aperture, Field of view, or Scale of view then Octane will take these 3 values and update the physical camera parameters to match these.

This update happens interactively, so you should not see different values after you save and load a scene.

by **PolderAnimation** » Thu Sep 02, 2021 7:38 am

Ok I see the problem then. This is what is not very handy about this solution.

I find it extremely useful to have control over my camera options in octane (for example aperture). But we usually get and camera from a 3D package, so when we have and ABC file, we do not have any options for the camera. To have a work around we use a camera node that gets the parameters (like focal length, focal depth, position, target and up vector) (see screenshot). This gives us the opportunity to tweak setting directly in octane (standalone). But if I set an aperture to 10 for example and save my file and reload it, it is set to 7.231239 (because every time we open the file, the focal length is set and so the aperture is set).

by **MindofImpact** » Mon Sep 13, 2021 6:27 pm

Hello, I found an issue with Octane 2020 and was redirected here by bepeg4d.

The clay mode in Octane 2020 seems to be ignoring the opacity data of all materials. This used to work perfectly fine in Octane v4 and I've now been told that something was changed after Octane 2018.1 and it's surprising that it hasn't been reported yet.

Example below, a plane with a red material and triangle in the opacity texture.

Screenshot_8050.png

Clay mode, opacity not registered.

Screenshot_8051.png

OctaneRender™ 2020.2.5 [current 2020.2]

Tweet

OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Re: OctaneRender™ 2020.2.5 [current 2020.2]

Who is online