OctaneRender™ 2019.1 XB1 Tweet

[vijay]

Hey Otoy - if you are in fact tweaking the Denoising, and it causes some differences between 2018 and 2019, maybe this reveals a greater opportunity.
Understand that you have it as an all-in-one solution, perhaps there will be use-case limitations for certain situations where it looks worse in 2019 vs 2018, and then other situations where it looks better in 2019 vs 2018.

So - maybe introduce, like the Old/New/Nishita Daylight models, variant models of Denoising to suit different rendering scenarios (ie different specular, transmission, lighting scenarios)

"AI" in itself will ultimately function on an if-then command subset at the most basic level, and it, in fact, can "get it wrong" in trying to do so.
In Biology, for example, "Instinct", which is a rehearsed biological command subset for given situations, will yes reveal errors/glitches under certain situations.
Thus, we see different species exploiting or failing from varying success rates on the instinct command subset they possess.

Denoising Blend is a great tool, it is awesome. But it is only working with one model of denoising. So, maybe give us a couple different models to choose from, will make the product more versatile.

I can try to give the option to select between 2018 and 2019 models. I'll add it in the todo list.

[wallace]

This is a more generic glitch I am finding:
Scenes loaded or copied into 2019 XB1 that were created 2018 sometimes will not have loaded Specular, Roughness, or Metallic materials loaded in.
I say sometimes because sometimes it does work and they are loaded in, other times not. Have not identified a pattern so far. For example I can load a scene and it will not have the roughness texture, values, and settings loaded in.
Then I will immediately open again as a new scene and it will have them.

I'll save these scenes as a new version inside of 2019, and then report back if the same thing still happens.

I am assuming this is universal material?

Do the texture nodes get loaded at all? Are they there in the node graph or are they nowhere to be found in the nodegraph?

Can you perhaps show me some screenshots of what's loaded and what's not, or an example of the scene saved in 2018 that has problem importing in 2019?

[Notiusweb]

Yeah, but I want it fixed NOW

Ahahaha....oh, me too!

LOL...What can I say, I can't wait for the full feature set, looks amazing!

[Notiusweb]

This is a more generic glitch I am finding:
Scenes loaded or copied into 2019 XB1 that were created 2018 sometimes will not have loaded Specular, Roughness, or Metallic materials loaded in.
I say sometimes because sometimes it does work and they are loaded in, other times not. Have not identified a pattern so far. For example I can load a scene and it will not have the roughness texture, values, and settings loaded in.
Then I will immediately open again as a new scene and it will have them.

I'll save these scenes as a new version inside of 2019, and then report back if the same thing still happens.

I am assuming this is universal material?

Do the texture nodes get loaded at all? Are they there in the node graph or are they nowhere to be found in the nodegraph?

Can you perhaps show me some screenshots of what's loaded and what's not, or an example of the scene saved in 2018 that has problem importing in 2019?

Hi, thx... Yes, it did involve Universal materials.
I am now saving my 2018 scenes in 2019, and now I am not coming across the issue upon closing and reopening the scene in 2019.
I am also not seeing the issue when copying from 2018, so it just is not occurring...which is a good thing.
Weird, maybe it was a caching thing on my system, or maybe when I was using 2018 while 2019 was opened caching got weird or something.

But I'll just note when it would happen, the node was just not in scene at all, when copied from 2018 to 2019.
..IE - Roughness would have a texture and values in 2018, but when the scene was saved in 2018 and then opened or copied into 2019, Roughness node was empty/not present

I'll keep my eye out for it and then screenshot it, but seems saving the scene in 2019 might be preventing whatever it was.

[milanm]

I think it's probably to early to report issues. 2019 XB1 still needs a lot of work. It's good for exploring the new features but we can expect several issues, crashes and limitations that will be solved in future builds.

Well I have mixed feelings about that. Over the years I've seen way too many bugs slip through just because I thought "they'll probably fix that".

Here's one example:
6 years ago there was an issue with glossy material and normal maps in V1.16. Instead of fixing the shading, they degraded the way normal maps render in 1.17 and called it an improvement! I was new here so I thought "it's an improvement so it's probably correct" & "they'll probably fix that".

I think glimpse was the only one to complain at the time about normals looking flat. At least publicly. I guess he also thought "they'll probably fix that" like me.
(I'll find that url later, that man has thousands of posts)


They never changed the way normal maps render. (relatively serious emoticon with one eye twitching)

So I was having A TON of issues recently with some OSL shaders and I spent weeks trying to find out what was going on. And now here I am, trying to implement my own normal mapping by changing the N parameter because I never reported this. Because I thought "they'll probably fix that".

Here is the issue:
The influence of the blue channel (Z axis) is limited. Practically, that removes 50% of the data from the normal map and limits the influence to only 90 degrees instead of 180. All this because of high specular in the glossy material. Back in V1.16, If we reduce specular, there was almost no issue in the glossy. Diffuse material was never even affected by this. Today, everything is affected by this "improvement" and we have different kinds of issues with specular reflections.

There must be a better way to fix the shading issue today (if it still exists). Or, at least, we should have an option to render normal maps correctly and deal with any issues ourselves. All apps capable of making normal maps assume that normal maps will be rendered correctly. All 3D assets available online are made with an assumption that normal maps will be rendered correctly.

normals not normal 116.zip

(223.21 KiB) Downloaded 186 times

NormalMapTest orbx.zip

(652.26 KiB) Downloaded 185 times

Regards
Milan

[milanm]

And I should probably also say that OctaneRender 2019.1 is an amazing release!

Cheers
Milan

[Jolbertoquini]

Hi Guys,

Can somebody reply to my question from the Dev team please? Basically do you have any plans to make work displacement with Motion Blur is working but crashing randomly, I post the scene on a comment aswell I had any comment from you part?

Cheers,
JO

[funk]

Investigating this problem currently, I noticed it already while fixing it in 2018.1.
I'll let you know once I have found out what the issue is.

Thanks for the bug report. I'll look into it,

Thanks!

[vijay]

Hi Guys,

Can somebody reply to my question from the Dev team please? Basically do you have any plans to make work displacement with Motion Blur is working but crashing randomly, I post the scene on a comment aswell I had any comment from you part?

Cheers,
JO

Sorry for the late reply. I'm looking into that issue. Thanks!

[mr_d_wilks]

is it just me or is speed getting significantly worse for Maxwell generation?

I'm using the benchmark_data from the version 4.0 download page. Command run is "octane --benchmark". My setup is three GTX 980 Ti.

ver 4.0.2_1 : 490
ver 2018.1 : 456
ver 2019.1_xb1 : 397

Ok i ran some tests at work:
2x 2080 - nvlink off

4.02.1 : 461
2018.1 : 444
2019.1 : 382

...it seems like the slow down above isn't specific to maxwell but is just in general. Is this something to be concerned about? according to this it looks like octane is getting slower, not faster.