It's incredibly good news. Obviously, it's going to take some time to get everything in place (including a new development team) but I hope this announcement means the Octane plugin for Lightwave will continue to be developed (and improves!)

One of the problems might be that the C4D integration of Octane uses its own custom node editor, for which there's no third-party API to access (I assume). If the Octane integration switched to C4D's native nodal system, it might make it a bit easier to write a conversion utility/script (eg. in ...

Thanks for the update Juan. It's not exactly surprising, but it's still incredibly sad to see the demise of Lightwave. Sure, LW was a creaky beast in some areas, but there's still so many unique features and workflows that exist in it that don't exist in other 3D apps (or not as well).

I wish there ...

I seem to have hit on a strange bug - rendering with the PMC kernal freezes the render when it tries to denoise. But if I switch to Pathtracing - it works.
I've got a single 3090, running latest studio drivers on Windows 10.

Edit: It doesn't work in the Live Viewer either - I just get a black ...

Thanks Juanjo, good to know it's not just my machine! Hope you manage to find a solution (and that there's still any developers left working on Lightwave who can fix issues with the SDK!)

Hi, in Lightwave 2020.0.02, using Octane 2020.1.4.0. I'm doing a project at the moment that involves bringing in some OBJ files. They're textured using the standard (old) texture channels - so textures in the Color, Specular, Luminosity and Normal slots. When I click on "Mat. Conversion", the ...

Thanks for getting back to me Juanjo - It would be amazing if this might make its way into a future update. Maybe as an option in the actual Lightwave volume object setup itself (rather than as a separate list).

Many thanks

I'm doing some experiments with animated volumetric ground fog at the moment, and in order to actually render this correctly in Octane (in Lightwave) and have the animated procedural textures for density update on every frame, I have to enable the "Update Volumes" option in the render target. This ...

I've got it to work, but at a cost. There's a "update Volumetrics" tickbox in the Render Target. However, this appears to force Octane to re-initialise ALL volumetrics on every frame, and as I've got a couple of large (static) VDBs in my scene, it's bringing render times to a crawl.
Is there any way ...

Here's the node setup for the volume object (the item info is getting position of a moving null I've put in the scene)