OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.0

[juanjgon]

Ok. Forget it. I've found one problem in the code ....

-Juanjo

[juanjgon]

Yes, sorry. Unfortunately, there is a bug in the displacement node, that is saving corrupted GUI data. I've fixed it for the next build, that I'll release as soon as possible.

Thanks for reporting this issue!
-Juanjo

[Mastoy]

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) :

[abstrax]

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.

[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!

[juanjgon]

Ok. Thanks, I'll change the default value for the next build.

-Juanjo

[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 ?

[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

[juanjgon]

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

[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)

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