OctaneRender™ 2019.1 RC2

[funk]

Glossy material bug

Sheen isnt working on the glossy material

[divasoft]

Glossy material bug

Sheen isnt working on the glossy material

You need to demand from developers a salary for the beta tester job)

[funk]

Metallic material bug

Specular map input no longer works as expected.

Drag it from 1 to 0. There is no gradual fade from full metallic to diffuse. It only becomes diffuse at specular map = 0

[Notiusweb]

Glossy material bug

Sheen isnt working on the glossy material

You need to demand from developers a salary for the beta tester job)

Yeah, Funk....You are on FIRE!
Bring on the HEAT!!!!

[linograndiotoy]

Edge color is ignored for the Toon Material, it always renders black or dark gray.

Also, the Toon material only works on the first object in the scene, renders totally black for any other object.

Thanks!

OutlineColor.ocs

(75.94 KiB) Downloaded 186 times

BlackToon.ocs

(80.54 KiB) Downloaded 201 times

[funk]

Vertex displacement bug? (See later edit. May be a "Merge unwelded vertices" bug)

Vertex displacement seems to be broken in this scene

1. Select the rendertarget
2. Select the "mat1" nodegraph. You can see this is currently using a vector displacement which looks wrong
3. Connect the texture displacement to the material to see the expected result


EDIT: This orbx was exported from modo. After looking at the ABC, I can see not all vertices are connected, so this must be causing problems for the new displacement.
I tried enabling the geometry.abc node import settings for "Merge unwelded vertices" but that doesnt seem to be working

[funk]

Vertex displacement crash to desktop

While trying some tests with modo's orbx exports, I've run into a file that crashes standalone (crash to desktop).

Sometimes it crashes when you start rendering, other times it crashes if you use the vertex displacement height slider

1. Load this orbx and select the render target (sometimes it crashes here)
2. Select the mat1 node and slide the vertex displacement height from 0 to 1 and back (other times it crashes here)

[Notiusweb]

Vertex displacement crash to desktop

While trying some tests with modo's orbx exports, I've run into a file that crashes standalone (crash to desktop).

Sometimes it crashes when you start rendering, other times it crashes if you use the vertex displacement height slider

1. Load this orbx and select the render target (sometimes it crashes here)
2. Select the mat1 node and slide the vertex displacement height from 0 to 1 and back (other times it crashes here)

Confirmed. Scene loaded but moving the height slider indeed crashed RC2.

[haze]

Otoy team,

When we enable the denoiser, viewport interactivity slows down. Is it possible to look into this?

Someone posted an example video (in modo) here: viewtopic.php?p=365499#p365499
video: https://www.mediafire.com/file/kbag4c1t ... g.mp4/file

I have attached the exported ORBX to this post

1. Load IPR Speed Test_house.orbx and click the render target
2. Quickly pan the view with right mouse. It feels smooth and interactive.
3. Select the camera imager and enable the denoiser
4. Pan the view with right mouse. It now feels much slower.



You can also test it with a simpler scene:

1. Grab "Fun_With_Vectron (4).orbx" from this post: viewtopic.php?p=357928#p357928
2. Click "Vetcron Shadertoy Primitives" and pan the view with right mouse. It feels smooth and interactive.
3. Select the camera imager and enable the denoiser (you'll need to add the bool)
4. Pan the view with right mouse. It now feels much slower.

While the denoiser is not actively denoising, it is actually doing a *lot* of work in the background in order to gather enough information to run it. That is what makes it less interactive at that point. I'm not sure there is much we can do about it, but we can investigate.

[haze]

I have an old orbx which is rendering darker mediums in 2019.1 compared to 2018 and 4.

medium_darker.png

Currently I believe this is due to a fix for GGX/Beckmann etc. We will have to investigate.