OctaneRender™ 4 RC 5 Tweet

[abstrax]

Hi all,

This is another bug-fix release - hopefully the last one before we can call it a stable version 4.

Please note that this build will expire in 120 days, this is now shown on the bottom right of the Standalone release.

As before, some introductory material on V4 can be found here: first release post of V4.

Please make sure you have NVIDIA driver 387 or newer on Windows and Linux, and any CUDA driver for Mac that supports CUDA 9.1. Please also note that architecture improvements mean we can no longer support Fermi GPUs.


Changes since OctaneRender 4 RC4:

• Octane is now trying to prevent the computer to go to sleep while rendering.
• Made a change in the render pipeline that hopefully increases the refresh rate at the beginning of rendering.
• Octane prints now a warning in the log if the environment variable CUDA_VISIBLE_DEVICES or CUDA_LAUNCH_BLOCKING is set. The effect of these is that not all GPUs are visible, causing rendering to be slower.
• Added support for emitters with "surface brightness" disabled to hair geometry.
• Fixed bug causing hair geometry emission to not to work at all.
• Fixed a bug where denoised alpha causes artifacts in denoiser output (see viewtopic.php?p=345938#p345938).
• Fixed a crash of an OSX net render master when a slave connects with it.
• Fixed incorrect alpha weight of beauty passes causing noisy, aliased edges (see viewtopic.php?p=345594#p345594).
• Fixed incorrect transition of the shadow passes to the background and between active and inactive layers.
• Fixed crash while changing the import preferences of a geometry archive of which we use its camera for rendering.
• Fixed crash when reloading the same texture node while its compression is still ongoing.
• Fixed crash or incorrect normal import of subdivided, deformed meshes (see viewtopic.php?p=346199#p346199).
• Fixed crash of the net render master (on OSX) when a slave connects with it (see viewtopic.php?p=346347#p346347).
• Fixed incorrect values displayed in the not-enough-memory error message of the denoiser (see viewtopic.php?p=346310#p346310).
• OSL: Fixed detection of derivatives (Dx and Dy intrinsics) which are not supported.
• OSL: When you save an OSL node or scripted graph which currently refers to a file in an ORBX package, do not show an error dialog. Instead clear the file name attribute and save the code.

Downloads for users with a regular license
OctaneRender for Windows (installer)
OctaneRender for Windows (zip)
OctaneRender for Mac OS
OctaneRender for Linux

Downloads for users with a Studio subscription license
OctaneRender for Windows (installer)
OctaneRender for Windows (zip)
OctaneRender for Mac OS
OctaneRender for Linux


Happy rendering,
Your OTOY Team

[grimm]

Awesome, works great. The only issue, on the Linux side, is that the window controls are still missing. I can't minimize, close, move, or resize the Octane window. It appears to be missing the window header. Thanks,

Jason

[WIPEXPO]

Hi, first of all congrats with new octane release. Can we get a option to automatically on quit deactivate licence ?
Thx.

[milanm]

Thanks for this update, V4 is getting better and better!

I just noticed that there is a crash with animated objects when OSL camera shaders are used and motion blur is enabled.

OSLCamMblurCrash.orbx

(55.8 KiB) Downloaded 247 times

Is this OSL post processing and compositing node graph mentioned here going to be part of final V4?

Regards
Milan

[Notiusweb]

Fixed crash or incorrect normal import of subdivided, deformed meshes (see viewtopic.php?p=346199#p346199).

Hi, thanks for this fix very much. The FBX loads fine now with subdivision

I am curious why do you think when Octane brings in the FBX version of the mesh, that it was able to both (1) Subdivide and (2) Load Vertex Normals, but as Alembic it could only do one or the other.
If a mesh has different parts, does Octane sees the FBX as 1 mesh and then the Alembic as multiple meshes?

Thx!

[grimm]

I had a question as well, I noticed that the denoising time is not added to the final render time. Is this how it's supposed to work? Thanks,

Jason

[divasoft]

Hi. Octane 4 Cinema integration constantly crashes it is not possible to work. It works in LV, but when i start full render 9 tries of 10 it will be crash. Is the problem in the main application or in integration? With simple scene it works normal and v.3.08 do not produces crashes.
https://drive.google.com/open?id=1rBG13 ... ut-9qjrhN1

[abstrax]

Awesome, works great. The only issue, on the Linux side, is that the window controls are still missing. I can't minimize, close, move, or resize the Octane window. It appears to be missing the window header. Thanks,

Jason

That's an issue of the GUI toolkit we use which occurs on some Linux distributions but not on others. The only workaround we found is using the non-native window title bar. For that you would have to disable the option "use native window title bar" in the application preferences and then restart.

[abstrax]

Hi, first of all congrats with new octane release. Can we get a option to automatically on quit deactivate licence ?
Thx.

Your license is always disabled automatically when you close Octane.

[abstrax]

Fixed crash or incorrect normal import of subdivided, deformed meshes (see viewtopic.php?p=346199#p346199).

Hi, thanks for this fix very much. The FBX loads fine now with subdivision

I am curious why do you think when Octane brings in the FBX version of the mesh, that it was able to both (1) Subdivide and (2) Load Vertex Normals, but as Alembic it could only do one or the other.
If a mesh has different parts, does Octane sees the FBX as 1 mesh and then the Alembic as multiple meshes?

Thx!

It seems that the FBX export writes out the complete character as one mesh while the Alembic export split it into multiple meshes. Subdivision surfaces don't create a continuous smooth surface over multiple meshes.