OctaneRender™ 2019.1 XB1

Forums: OctaneRender™ 2019.1 XB1
A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.

Re: OctaneRender™ 2019.1 XB1

Postby vijay_thirukonda » Sun Mar 24, 2019 9:54 pm

vijay_thirukonda Sun Mar 24, 2019 9:54 pm
Notiusweb wrote: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.
vijay_thirukonda
OctaneRender Team
OctaneRender Team
 
Posts: 134
Joined: Sun Jul 24, 2016 8:42 pm

Re: OctaneRender™ 2019.1 XB1

Postby wallace » Sun Mar 24, 2019 9:56 pm

wallace Sun Mar 24, 2019 9:56 pm
Notiusweb wrote: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?
User avatar
wallace
OctaneRender Team
OctaneRender Team
 
Posts: 89
Joined: Sun Dec 18, 2016 10:38 pm

Re: OctaneRender™ 2019.1 XB1

Postby Notiusweb » Mon Mar 25, 2019 1:10 am

Notiusweb Mon Mar 25, 2019 1:10 am
linograndiotoy wrote:
Notiusweb wrote:
Yeah, but I want it fixed NOW :twisted:



Ahahaha....oh, me too! :D


LOL...What can I say, I can't wait for the full feature set, looks amazing! ;)
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan Xp, 1 Titan X Pascal
External: 6 Titan X Pascal - 1600W EVGA T2
Plugs: 3DSMax, C4D, Daz, Houdini, Lightwave, Sketchup
User avatar
Notiusweb
Licensed Customer
Licensed Customer
 
Posts: 1156
Joined: Mon Nov 10, 2014 4:51 am

Re: OctaneRender™ 2019.1 XB1

Postby Notiusweb » Mon Mar 25, 2019 2:47 am

Notiusweb Mon Mar 25, 2019 2:47 am
wallace wrote:
Notiusweb wrote: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.
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan Xp, 1 Titan X Pascal
External: 6 Titan X Pascal - 1600W EVGA T2
Plugs: 3DSMax, C4D, Daz, Houdini, Lightwave, Sketchup
User avatar
Notiusweb
Licensed Customer
Licensed Customer
 
Posts: 1156
Joined: Mon Nov 10, 2014 4:51 am

Re: OctaneRender™ 2019.1 XB1

Postby milanm » Mon Mar 25, 2019 8:33 am

milanm Mon Mar 25, 2019 8:33 am
linograndiotoy wrote: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.

ImageImage

normals not normal 116.zip
(223.21 KiB) Downloaded 19 times

NormalMapTest orbx.zip
(652.26 KiB) Downloaded 19 times


Regards
Milan
Colorist / VFX artist / Motion Designer
macOS - Windows 7 - Cinema 4D R19.068 - GTX1070TI - GTX780
milanm
Licensed Customer
Licensed Customer
 
Posts: 261
Joined: Tue Apr 30, 2013 7:23 pm

Re: OctaneRender™ 2019.1 XB1

Postby milanm » Mon Mar 25, 2019 8:59 am

milanm Mon Mar 25, 2019 8:59 am
And I should probably also say that OctaneRender 2019.1 is an amazing release!

Cheers
Milan
Colorist / VFX artist / Motion Designer
macOS - Windows 7 - Cinema 4D R19.068 - GTX1070TI - GTX780
milanm
Licensed Customer
Licensed Customer
 
Posts: 261
Joined: Tue Apr 30, 2013 7:23 pm

Re: OctaneRender™ 2019.1 XB1

Postby Jolbertoquini » Mon Mar 25, 2019 10:55 am

Jolbertoquini Mon Mar 25, 2019 10:55 am
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
Octane Render for Maya.
https://vimeo.com/jocg/videos
https://www.linkedin.com/in/jocgtd
http://www.hmxmedia.com/
--------------------
Join MAYA OCTANE USERS Skype discussion here :
https://join.skype.com/LXEQaqqfN15w
User avatar
Jolbertoquini
Licensed Customer
Licensed Customer
 
Posts: 961
Joined: Sun Aug 31, 2014 7:08 am
Location: London

Re: OctaneRender™ 2019.1 XB1

Postby funk » Mon Mar 25, 2019 10:59 am

funk Mon Mar 25, 2019 10:59 am
wallace wrote: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.


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


Thanks!
Win10 Pro 64 / Core i7-975 3.33GHz / 12GB RAM / GTX 1080 Ti + GTX 670 / 2x1920x1200 / MODO 13
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
User avatar
funk
Licensed Customer
Licensed Customer
 
Posts: 785
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

Re: OctaneRender™ 2019.1 XB1

Postby vijay_thirukonda » Mon Mar 25, 2019 9:32 pm

vijay_thirukonda Mon Mar 25, 2019 9:32 pm
Jolbertoquini wrote: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!
vijay_thirukonda
OctaneRender Team
OctaneRender Team
 
Posts: 134
Joined: Sun Jul 24, 2016 8:42 pm

Re: OctaneRender™ 2019.1 XB1

Postby mr_d_wilks » Mon Mar 25, 2019 11:29 pm

mr_d_wilks Mon Mar 25, 2019 11:29 pm
mr_d_wilks wrote: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.
mr_d_wilks
Licensed Customer
Licensed Customer
 
Posts: 8
Joined: Sat Nov 24, 2018 4:50 am
PreviousNext

Return to Development Build Releases


Who is online

Users browsing this forum: No registered users and 0 guests

Tue Nov 12, 2019 10:19 am [ UTC ]