Page 2 of 4
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Thu Mar 09, 2017 3:10 pm
by Mastoy
juanjgon wrote:Sorry, I am not aware off changes in the passes gamma or tone mapping. Do you have this problem with all the passes (beauty, info, etc)?
Thanks,
-Juanjo
The beauty pass is not affected, but as far as I know, the MaterialID, ObjectID and ambient occlusion are
Here are some examples of the same scene rendered in 3.05 (left) and 3.06 (right) :

Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Thu Mar 09, 2017 9:45 pm
by abstrax
Mastoy wrote:juanjgon wrote:Sorry, I am not aware off changes in the passes gamma or tone mapping. Do you have this problem with all the passes (beauty, info, etc)?
Thanks,
-Juanjo
The beauty pass is not affected, but as far as I know, the MaterialID, ObjectID and ambient occlusion are
Here are some examples of the same scene rendered in 3.05 (left) and 3.06 (right) :

Yes, there was a bug in the tone mapping of some info passes, which we fixed in 3.06:
We were applying the gamma value of the imager settings for various info passes (like the ID passes, wireframe or AO). The problem with that is that the gamma in the imager settings is applied
on top of the gamma of the camera response curves, i.e. it's usually set to a gamma of around 1. But when you choose the response curve "
Linear/off", you usually have to set the gamma to 2.2 or something similar to compensate the gamma of the display (or to bring it into sRGB colour space).
In other words, depending on the camera response curve, info passes would be tone mapped differently, which of course shouldn't be the case, because the camera response curve isn't applied to info passes. To fix this problem we now
always apply a gamma of 2.2 for the affected info passes and ignore the gamma setting in the imager.
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Fri Mar 10, 2017 10:44 pm
by FrankPooleFloating
Hey Juanjo, not a big thang, but I noticed that you have AS Noise Threshold default at 1%, when Marcus says default is 2% in the 3.0.6 Features thread. I've been doing more testing of AS and just happened upon this discrepancy just now.
Noise threshold: Specifies the smallest relative noise level. When the noise estimate of a pixel becomes less than this value, sampling will be switched off for this pixel. Good values are in the range of 0.01 - 0.03. The default is 0.02, which is pretty clean.
Thanx again J!
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Sat Mar 11, 2017 10:55 am
by juanjgon
Ok. Thanks, I'll change the default value for the next build.
-Juanjo
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Sat Mar 18, 2017 12:08 pm
by Lewis
Hi Juan!
Here is one small bug report for 3.06 version
When i activate Region rendering in the IPR and move it by MMB it clears/reset previously rendered areas and only renders new position.
with CTRL+Drag it Works fine but MMB moving is not correct shouldn't it keep previously rendered areas also ?
3.06.0.0 funny bug
Posted: Sun Mar 19, 2017 12:35 pm
by LightwaveGuru
hi juanjo,
i have a funny bug for you! (V 3.06) from time to time switch the cables (all connectors) to yellow and than you can render no more instances.(octane see the lw instances than no more) also the "Node Menu" is grey and you can not more use any default set up under the node menu.
if you de-install the plug and install it new is the bug gone...i can not identificate in what case it comes and go...LOL

p.s. ( i have the same in a early version 3.04 and also in 2.2 but i can not reproduce it or say in what case it comes and go...its a ghost! LOL

...p.s.s.(in 3.05 i have never seen it)
in the surface editor it look ijn that way...
snip lwguru
Re: 3.06.0.0 funny bug
Posted: Mon Mar 20, 2017 8:52 am
by juanjgon
LightwaveGuru wrote:hi juanjo,
i have a funny bug for you! (V 3.06) from time to time switch the cables (all connectors) to yellow and than you can render no more instances.(octane see the lw instances than no more) also the "Node Menu" is grey and you can not more use any default set up under the node menu.
if you de-install the plug and install it new is the bug gone...i can not identificate in what case it comes and go...LOL

p.s. ( i have the same in a early version 3.04 and also in 2.2 but i can not reproduce it or say in what case it comes and go...its a ghost! LOL

...p.s.s.(in 3.05 i have never seen it)
This is not a bug, you are using the LightWave 10 plugin version inside LW11 or LW2015

... it works, but LW10 had a lot of limitations in the node editor, this is why all the connections are yellow, and of course it didn't have instances.
Thanks,
-Juanjo
Re: 3.06.0.0 funny bug
Posted: Mon Mar 20, 2017 1:24 pm
by LightwaveGuru
juanjgon wrote:LightwaveGuru wrote:hi juanjo,
i have a funny bug for you! (V 3.06) from time to time switch the cables (all connectors) to yellow and than you can render no more instances.(octane see the lw instances than no more) also the "Node Menu" is grey and you can not more use any default set up under the node menu.
if you de-install the plug and install it new is the bug gone...i can not identificate in what case it comes and go...LOL

p.s. ( i have the same in a early version 3.04 and also in 2.2 but i can not reproduce it or say in what case it comes and go...its a ghost! LOL

...p.s.s.(in 3.05 i have never seen it)
This is not a bug, you are using the LightWave 10 plugin version inside LW11 or LW2015

... it works, but LW10 had a lot of limitations in the node editor, this is why all the connections are yellow, and of course it didn't have instances.
Thanks,
-Juanjo
hi juanjo,
trust me. i use lw 2015.3 (64bit) and the plug in version for lw 2015.3 (64bit). and it is not every time! it comes and go like a ghost!
(for example in V 3.05 or V3.xx i never have seen it) ----if i install 3.05 is this "ghost" gone...LOL
snip lwguru
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Mon Mar 20, 2017 1:44 pm
by LightwaveGuru
juanjgon wrote:BorisGoreta wrote:Yes, I just select it and it crashes, but if I hide the parameters part of the node editor window on the right then id doesn't crash so it must be something with displaying the parameters of the displacement node.
Hmm, weird. Here it works fine, and I can't see in the code something that could crash the node GUI. Are you sure that you have not mixed two version of the plugin or something like that? Perhaps you should re-install the plugin in your Layout. This version has some new nodes and perhaps there is a problem if it is not re-added.
Anyway, anybody else has this problem?
Thanks,
-Juanjo
"Are you sure that you have not mixed two version of the plugin or something like that?"
yes i am realy shure juanjo

here ...if i switch back to V 3.05.3 its all fine
snip lwguru
Re: OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0
Posted: Mon Mar 20, 2017 1:51 pm
by LightwaveGuru
juanjo here a little bit explanation,
if i install the V 3.06 beta the first time also is all fine. the cables are green and blue etc.pp...i can add from the node menu default set ups etc.pp...also the instance renderings would work. but if i close the layouter and start him new all cables are yellow,the node menu is grey and octane would not render longer any instances. all other functions work. spooky

its a ghost in the machine! LOL
snip lwguru