OctaneRender™ for LightWave™ build 1.13.1 released

Newtek Lightwave 3D (exporter developed by holocube, Integrated Plugin developed by juanjgon)

Moderator: juanjgon

gordonrobb
Licensed Customer
Posts: 1247
Joined: Sat Mar 16, 2013 9:08 am

yep, use the output form the dirt node to mix another texture. Good thing is you can also reverse normals, so it can be used for edge effects too.
Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |
marchermitte
Licensed Customer
Posts: 283
Joined: Sat May 29, 2010 9:25 pm
Location: Geneva
Contact:

Oh, right! We have It in Octane-Lightwave!!! I thouth It was only in Octane stand alone... sorry!
Everything perfect then!

:-)
Marc Hermitte
Intel I7 4.5 Ghz, 24 gig ram, 2x Nvidia GTX 480, win 764bits
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

I have another bug to report.

If you have 2 imager:camera nodes and edit settings in the one that is not plugged into the render target, the IPR still changes as if it were plugged in.

You can also unlpug all of them, but when you make changes in the unplugged imagers, the IPR shows the changes
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

funk wrote:I have another bug to report.

If you have 2 imager:camera nodes and edit settings in the one that is not plugged into the render target, the IPR still changes as if it were plugged in.

You can also unlpug all of them, but when you make changes in the unplugged imagers, the IPR shows the changes
Yes, I remember that from the begining I have a problem to process events when user unplug a node in the render target node editor: plugin doesn't detect that a node is unpluged without reload scene and process it anyway. I am going to see if this bug can be fixed, but I remember a problem with LW SDK and this issue.

-Juanjo
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

I've discovered another bug. The "shadow catcher" method from the standalone doesnt work in the LW plugin.

On pg 117 of the octane 1.10 manual it tells you how to set it up. In the standalone, we can see the shadow catcher working in real time. In the IPR we just see BLACK where the matte materials are.
Once you save an EXR from the standalone, you can see the shadows in the ALPHA channel. If you do the same in the LW plugin, the alpha channel is saved without shadows

Is there a different method to get this working in lw?
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"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
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

Here is a quick test scene in LW and standalone using a shadow catcher. The LW version saves no shadows in the alpha
Attachments
shadow_catcher_test.zip
(31.61 KiB) Downloaded 318 times
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

funk wrote:Here is a quick test scene in LW and standalone using a shadow catcher. The LW version saves no shadows in the alpha
Thanks for the scene. You are right, there is a problem with the plugin and the fact that Standalone doesn't add a default transmission node to the diffuse shader. Plugin by default add a float value to the transmission input, and set it to 0%.

I am not sure why, but if you have this value to 0%, shadow catcher (using the Matte switch) doesn't work. Workaround is to set the transmission to something greater than 0% (0.01% is fine), and with this value plugin works like standalone.

I am going to see if is possible fix it.

Thanks again for the report ;)

BTW: I have found that the Alpha switch in the IPR window doesn't work in the 1.13.1 release. Is this switch working for you?

-Juanjo
Attachments
image-000174.jpg
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

Thanks for the workaround Juanjo. The alpha button on IPR is working fine here
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

funk wrote:Thanks for the workaround Juanjo. The alpha button on IPR is working fine here
I fix this bug for the next release. Now with "Matte" enabled, default "Transmission" is disabled (no node is added to the shader input). Anyway you can plug any texture in the transmission input if you need transmission+matte for something.

-Juanjo
Attachments
image-000175.jpg
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

funk wrote:I have another bug to report.

If you have 2 imager:camera nodes and edit settings in the one that is not plugged into the render target, the IPR still changes as if it were plugged in.

You can also unlpug all of them, but when you make changes in the unplugged imagers, the IPR shows the changes
I am testing this issue and it is true that if you change any parameter in a unplugged node inside the render target node editor, IPR refresh the render, but no values are changed. The problem is that if you unplug a render target node without plug a new one, plugin is going to "remember" the last settings, but you can't modify them without plug a new node in this input (or reload scene, to set this input with the default settings)

Anyway this is something really hard to fix because I have some problems with LW SDK and the plug/unplug node events.

-Juanjo
Post Reply

Return to “Lightwave 3D”