This is the stable release of version 3.06, which brings a lot of new features. You can find more information about the main new features in this thread.

Yesterday we accidentally released an incorrect build of 3.06, which we had to remove again. If you already downloaded that version (3060004), please delete it and download the version below (3060005) again, which fixes 2 more problems. If you've got further questions about this please contact me via PM.

The next step is the release of OctaneBench based on 3.06 in the next 1-2 weeks.

Overhauled the shortcut manager of the Standalone. You can assign now shortcuts to all available commands.

"Expected exposure" of the adaptive sampling settings can now be set to 0, which disables the tweaking of the noise estimate, as described in the new features thread. This is also default now.

Fixed random CUDA crashes in scenes with high densities of overlapping instances.

Fixed the motion vector pass, which didn't do the viewport transformation correctly for perspective cameras. The values of the motion vector pass are now the motion vector in pixels and not the motion vector relative to the screen width. This allows you to use the output directly in Fusion, without having to guess the scale. You still have to set the vector blur scale to 2 for some reason, but with a scale factor of 2 you now always get (approximately) the same amount of motion in Fusion as you would get with rendered motion blur.

Fixed DOF in the thin-lens camera with distortion.

Fixed DOF in the cube map and cylindrical panoramic camera.

Fixed orientation of camera rays with high distortion in places where they deviate more than 180° from the camera axis.

Fixed auto-focus in stereo cameras (the left eye is always used for auto-focus picking).

Fixed incorrect material assignment if the geometry ends up being 1 simple mesh, but the scene graph consists of multiple instances/meshes.

Reverted default texture of the second input texture of the multiply texture to a float texture. This allows you to set a higher multiplication factor than 1.[*[ Fixed the triplanar map texture node which turns black when you change its inputs and it is connected via a linker node.

Fixed a couple of authentication issues.

Fixed crashes in some corner cases when UI components are refreshed due to related node system changes.

Fixed issue that the time slider disappears when you have a scene with a negative time interval start and switch to "Frames".

Fixed missing render update, when the start and end time of the animation settings changed.

Fixed incorrect behaviour which didn't allow users to re-enter their credentials if the SSO authentication expired.

Changed defaults of the cosine mix texture to match the regular mix texture.

A new version of the Photoshop plugin (1.0.5) has been made available, containing the following changes:

Added support for noise layer added in v3.06.

Added support for Photoshop 2017.

You can download and install the plugin either via the Adobe Exchange platform (the latest version still needs to be approved by Adobe, so it may take some time to show up) or you can download it from the link below and manually install it.

abstrax wrote:[*] Reverted default texture of the second input texture of the multiply texture to a float texture. This allows you to set a higher multiplication factor than 1.

Is there a reason why only multiply > scale (which is a greyscale color), can go over 1.0? I think we need to allow this for all greyscale color values (eg add, subtract etc)

It doesnt make sense to limit these nodes. If I can use an add to get 1.0+1.0 = 2.0, why limit the inputs?

EDIT: I just tested the comparison node and it also allows values over 1.0, so this seems inconsistent. Maybe you guys just missed fixing add and subtract texture nodes?

EDIT 2: Even the mix texture (and mix material) > amount allows values over 1.0 (it doesn't even make sense to allow it here)All this is a bit of a mess You need to go through all nodes and make sure values are only capped where it makes sense, or at least be consistent and have no cap on any greyscale values