Hi! This is the latest production build of the OctaneRender™ 3.0 for LightWave™ plugin, available for Lightwave 10.1, 11.6 and 2015.3 Windows x64 and OSX.
Release 3.03.2.0
https://render.otoy.com/customerdownloa ... indows.zip
https://render.otoy.com/customerdownloa ... .0_OSX.zip
Standalone version for the network rendering nodes
https://render.otoy.com/customerdownloa ... 2b_win.exe
https://render.otoy.com/customerdownloa ... _macos.dmg
CUDA requirements
Due to a CUDA compiler bug we had to switch to CUDA 7.5, which means on Windows and Linux you may need to update your NVIDIA graphics driver to a current version which supports at least CUDA 7.5. On Mac OSX you may have to update the CUDA driver for Mac to a current version supporting at least CUDA 7.5.
How to install the plugin
- (Only for Windows) Remove all the old Octane plugin files (octane.dll, octane.dat and the .p plugin file)
- (Only for Windows) Copy the octane.dll, tbb.dll and octane.dat files into you install Lightwave/bin directory. You must overwrite the LightWave tbb.dll file.
- Add the plugin to the Lightwave Layout.
- Install the custom menu bar to get access to the Octane features.
New features
A list of all the new features is provided here: viewtopic.php?f=33&t=51679
The plugin manual is going to be updated in the next weeks to cover most of the changes. https://docs.otoy.com/manuals/products/lightwave-3d/v3/
=============================================
RELEASE 3.03.2.0
=============================================
* NEW OCTANE FEATURES:
- Experimental Pascal GPU support. We haven't done any specific Pascal tweaks/optimizations yet and the performance isn't where we would expect it to be.
- Added far clip plane to thin-lens/panoramic camera nodes.
- Added option to the thin-lens/panoramic camera nodes to swap eyes when stereo rendering is used. This option is used during tone-mapping, i.e. doesn't restart rendering, with the exception of anaglyphic stereo rendering which requires a render restart.
- Only one Octane process can now authenticate with the SSO server at the same time. Other processes will wait until the authentication is finished.
- Empty volume nodes are allowed now. This should help with aligning VDB sequences with the rest of an animation. Empty volumes will be excluded from the compiled scene geometry.
- Daemon scan networks are now identified via sub-net address and adapter address, which allows us to distinguish between multiple adapters connected to the same sub-net.
- Added volume step length to the absorption and scattering medium nodes. This parameter will only be used by volume nodes.
- Fixed degradation of direct light calculation of transparent light sources.
- Fixed the diffuse render pass which wasn't rendered correctly for glossy materials.
- Various other small tweaks to the rendering.
* PLUGIN BUGS FIXED:
- Copy/paste missing parameters in the Texture environment node. Fixed.
* OCTANE BUGS FIXED:
- Fixed bug causing the baking camera to render regions of the output with a lower number of samples when network rendering is being used.
- Fixed incorrect rendering of sphere primitives.
- Fixed artifacts when an emitter is rendered inside a mesh with a medium (which was the root cause for viewtopic.php?f=30&t=54763 ).
- Fixed incorrect rendering of absorption medium used in the environment.
- Fixed incorrect rendering of media with a black absorption channel and with enabled "invert absorption".
- Fixed shadow passes for volumes.
- Fixed crash when baking the 2nd or 3rd UV channel amd it contains invalid numbers (NaNs).
- Fixed "invert absorption" option of the scattering and volume medium nodes.
- Fixed baking camera if a negative scale is used for a baked instance.
- Fixed version number display in daemon list of the net render configuration dialog.
Thanks,
-Juanjo
OctaneRender™ 3.0 for LightWave™ - Production build 3.03
Moderator: juanjgon
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
Thanks for the update. Was hoping for the come back of the limited region ...
19 x NVIDIA GTX http://www.borisgoreta.com
Thanks for update Juan 
Is there any more info what exactly this feature is:
"- Added far clip plane to thin-lens/panoramic camera nodes."
cheers

Is there any more info what exactly this feature is:
"- Added far clip plane to thin-lens/panoramic camera nodes."
cheers
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Opps, sorry. This feature is not exposed in the cameras due to a bug in the nodes code. It will be fixed for the next build. If anybody needs this feature, please let me know to send a custom build of the plugin with the problem fixed.Lewis wrote: Is there any more info what exactly this feature is:
"- Added far clip plane to thin-lens/panoramic camera nodes."
Thanks,
-Juanjo
Last edited by juanjgon on Tue Jul 19, 2016 1:40 pm, edited 1 time in total.
You can use the limited region in the final render window, like before ... but I am now working in new features in the plugin side for the next build. The limited region in the IPR window is in the top of the listBorisGoreta wrote:Thanks for the update. Was hoping for the come back of the limited region ...

Thanks,
-Juanjo
Thanks for quick answerjuanjgon wrote:Opps, sorry. This feature is not exposed in the cameras due to a bug in the nodes code. It will be fixed for the next build. If anybody needs this feature, please let me know to send a custom build of the plugin with the problem fixed.Lewis wrote: Is there any more info what exactly this feature is:
"- Added far clip plane to thin-lens/panoramic camera nodes."
Thanks,
-Juanjo

First of all I'd like to know what does that feature actually do, is it what i think it is (way to clipping plane so you can render room section through walls....= ??
--
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
Lewis
http://www.ram-studio.hr
Skype - lewis3d
ICQ - 7128177
WS AMD TRPro 3955WX, 256GB RAM, Win10, 2 * RTX 4090, 1 * RTX 3090
RS1 i7 9800X, 64GB RAM, Win10, 3 * RTX 3090
RS2 i7 6850K, 64GB RAM, Win10, 2 * RTX 4090
- electric_eric
- Posts: 144
- Joined: Wed Apr 10, 2013 1:41 pm
- Location: Nottingham, UK
- Contact:
Hi,
Since I upgraded to the latest version of the plugin I ocassionally get a 'Render Failed' message with both IPR and F9 renders, even on a blank scene. Sometimes restarting LW fixes it, other times not.
I initially thought it was a graphics card issue but now its started happening on both my work and home PC's, so I tried installing an earlier version of the plugin and the error doesn't happen anymore.
I posted on the Lightwiki facebook page and other users are experiencing the same thing.
Thanks,
Simon
Since I upgraded to the latest version of the plugin I ocassionally get a 'Render Failed' message with both IPR and F9 renders, even on a blank scene. Sometimes restarting LW fixes it, other times not.
I initially thought it was a graphics card issue but now its started happening on both my work and home PC's, so I tried installing an earlier version of the plugin and the error doesn't happen anymore.
I posted on the Lightwiki facebook page and other users are experiencing the same thing.
Thanks,
Simon
Intel i7 6700k - 64gb Ram - 6 x 980ti
So you have this problem only with this latest build, right? Can be a bug in the latest Octane build.electric_eric wrote:Since I upgraded to the latest version of the plugin I ocassionally get a 'Render Failed' message with both IPR and F9 renders, even on a blank scene. Sometimes restarting LW fixes it, other times not.
I initially thought it was a graphics card issue but now its started happening on both my work and home PC's, so I tried installing an earlier version of the plugin and the error doesn't happen anymore.
The main question is if it also happens in the Standalone (or in other plugins). This is the key to know if the problem is in Octane, or can be something related to the plugin. Here I can't reproduce this problem, so I am not sure. Anybody can reproduce this problem in Standalone, or perhaps in other plugin?
-Juanjo
- electric_eric
- Posts: 144
- Joined: Wed Apr 10, 2013 1:41 pm
- Location: Nottingham, UK
- Contact:
I'll look into it this evening.
Thanks
Thanks
Intel i7 6700k - 64gb Ram - 6 x 980ti
- ristoraven
- Posts: 390
- Joined: Wed Jan 08, 2014 5:47 am
Hi,
I have a scene where I made LW displacement terrain and added Octane displacement also to it. It renders well in IPR. IPR says there's well below million polygons in the scene. When I set Octane to render 18k cubemap, Octane says there's 30 million+ polygons and the machine freezes.. Had to reboot. I made an ORBX file and tested the scene in standalone and it works well there in 18k resolution. I also tried in LW 3840x1920 "stereo over-under" setting and the machine tilted for a while and then crashed and I got a dump file generated.
Tested with the latest 3.03 plugin.
I have a scene where I made LW displacement terrain and added Octane displacement also to it. It renders well in IPR. IPR says there's well below million polygons in the scene. When I set Octane to render 18k cubemap, Octane says there's 30 million+ polygons and the machine freezes.. Had to reboot. I made an ORBX file and tested the scene in standalone and it works well there in 18k resolution. I also tried in LW 3840x1920 "stereo over-under" setting and the machine tilted for a while and then crashed and I got a dump file generated.
Tested with the latest 3.03 plugin.