OctaneRender™ 3.0 for LightWave™ -Production build 3.08.0.10 Tweet

[juanjgon]

Thanks, this helped, but we don't have Specular Map in the node edit panel and this one is important to mix between diffuse/glossy appearance.

You have an input to link a texture. This parameter only works with a texture type linked nodes.

Thanks,
-Juanjo

[BorisGoreta]

Yes but it could be a float value, otherwise there is no way to add diffuse component to the material. A kind of a balance between diffuse and specular. If needed the texture can be plugged in but float value in the node edit panel would be useful.

[BorisGoreta]

Transmission value of a specular material is affecting OpenGL transparency. Since this value is often 100% these objects are invisible in the viewport.

[stoecklem]

Hi

I am trying to use Octane in 2018 but it is not letting me install the plugin. I've got 2015 redis installed. I've uninstalled it and Lightwave numerous times, restarted,etc.
I've included a screen shot of the bad image popup. Does anyone have any ideas?

Thanks
Mike

[juanjgon]

Hi

I am trying to use Octane in 2018 but it is not letting me install the plugin. I've got 2015 redis installed. I've uninstalled it and Lightwave numerous times, restarted,etc.
I've included a screen shot of the bad image popup. Does anyone have any ideas?

Thanks
Mike

Hi,

So do you say that you have LW2015 on this same computer and Octane works fine on it? It is weird ... this problem can be related to the lack of the Visual C++ 2015 redistributable package, but this should affect also to the 2015 plugin.

Thanks,
-Juanjo

[stoecklem]

It can't be added to the 2015 version either. It gives a different error popup.

Mike

[juanjgon]

Hmm, how are you installing the plugin? It seems that you could have mixed Octane.dll/.dat files and plugin .p files that are not from the same version.

Currently, you don't need to copy anything to the LightWave/bin folder. I fact you should remove any Octane.dll or Octane.dat files that you could have in LightWave/bin folder. All the Octane files are now located in the same directory used by the plugin .p file, and you don't need to copy them to another place.

Thanks,
-Juanjo

[stoecklem]

I'm just putting the 2018win64 octane folder in my plugins folder and installing the plugin.p file. There aren't any Octane.dll or Octane.dat files in the bin folder..I'm pretty sure I'm doing everything right.

I think this might be related to the fact I stupidly installed Visual Studio 2017 and it messed up something. I've uninstalled that and even run the total uninstaller tool. And tried everything I can find on google. Unfortunately I might have to roll back to a year old back up before I did that.

[stoecklem]

I figured out the problem.

I needed an update for windows sp1 to support a newer file signature.

https://knowledge.symantec.com/support/ ... id=SO26221

all is working now. Thanks.

[juanjgon]

Ah, yes, sorry, I had not thought about the windows signature issue. I'm glad that you have found it.

Thanks,
-Juanjo