Thanks for the fast answer
Octane plugin does not install in LW-11.5 or 11.6
Moderator: juanjgon
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 the most out of the Octane plugin.
Originally, I had copied over my .newtek and plugins folders from my laptop. I then got an error upin starting LW that said there was a failure to load the Octane Master plugin.
I uninstalled, reinstalled everything cleanly, and tried adding the plugin manually, and then got the error that led me here.
I have LW2018, but still have to use 2015 for Octane, so I am eagerly awaiting the LW2018 Octane plugin!!!
Cheers
Johan
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 the most out of the Octane plugin.
Originally, I had copied over my .newtek and plugins folders from my laptop. I then got an error upin starting LW that said there was a failure to load the Octane Master plugin.
I uninstalled, reinstalled everything cleanly, and tried adding the plugin manually, and then got the error that led me here.
I have LW2018, but still have to use 2015 for Octane, so I am eagerly awaiting the LW2018 Octane plugin!!!
Cheers
Johan
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 reply!
Johan
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 reply!
Johan

