Hi, just wondering if there were any updates on this? Having the exact same problem, and although workaround exist, none of them are ideal. One could for instance use IPR for final render, but what if you want to render a sequence?

I'm on Octane 4 and LW 2019.1.4.

Many thanks
Johan

Indeed. Had not yet installed the LW2018.0.3 build. Issue resolved. (he says blushingly; ALWAYS unstall the latest version before reporting issues :)).

Love the new LW integration by the way! Curious to experiment with the available BRDF models, the new render kernel(s) and also like the modeler ...

Update:

Still using Octane Standalone 3.08 RC2, and have tried LW2015 with the 3.08.0.9 build for LW2015.

Issue does not occur with LW2015

Hi,

Running Win10 pro x64, LW 2018.0.1 Octane Standalone 3.08 RC2 and LW plugin 3.08.0.8.

Having a problem trying to use Octane Texture Image in the LW node editor (both for regular surfaces as for the Render Target editor).

Double-click the node in the navigation panel, and nothing happens ...

Actually, I have 2013 on my laptop as well, where everything worked fine. Odd.

Anyhows, I reinstalled everything, and copied over my .newtek and plugins folders and Octane is now up and running! Can't wait for the 2018Ti to render my scenes!

Odd.

I had that one installed! (came with LW2015.3). I had 2008/2010/2013/2015. The problem only went away when I added 2012.

Perhaps it's the 2013 that gets in the way and forces the plugin loader to use the wrong version ,as you suggested a bit higher up in this thread.

But thanks for the swift ...

Same problem here!

Installing the Visual C++ 2012 Redistributable did the trick. Great that I found this post, and super that Juanjgon cracked it! Still works after more than 4 years :).

Concidentally, went from an i7, NVidia GTX 670MX laptop to a newly built !9-16 core, 1080Ti desktop, to make ...