OctaneRender 2019.1 LightWave beta build 2019.1.0.4 RC5

Wed Sep 25, 2019 9:32 am

Hi,

This is a beta release of the OctaneRender™ 2019.1 for LightWave™ plugin version 2019.1.0.4, available for LightWave 11.6, 2015.3, 2018.0 and 2019.0/2019.1 Windows x64 and OSX. This build has been compiled using the Octane 2019.1 RC5 core.

To use Octane 2019.1, you need to have a Studio or Enterprise subscription license. We recommend that you upgrade your NVIDIA driver to version 419.17 or newer.

Release 2019.1.0.4 Enterprise subscription license
https://render.otoy.com/customerdownloa ... rprise.zip
https://render.otoy.com/customerdownloa ... rprise.zip

Release 2019.1.0.4 Studio subscription license
https://render.otoy.com/customerdownloa ... studio.zip
https://render.otoy.com/customerdownloa ... studio.zip

Standalone 2019.1 RC5 Enterprise subscription version for the network rendering nodes
viewtopic.php?t=72413

Happy rendering,
Your OTOY Team

Wed Sep 25, 2019 10:07 am

This new vertex displacement thing. What is it really ? As I see it it is just subdividing the mesh and displacing it, the same way we can do in LW using higher subdivision levels. Also I've noticed it is way slower than textured displacement node in preprocessing stage.

I realize vertex displacement does not produce artifacts as texture displacement sometimes does and it can do an ear out of a plane.

But how is this better than native LW displacement ? It just pumps millions of triangles into the engine.

Wed Sep 25, 2019 10:31 am

Yes, I suppose that the new displacement is a conventional subdivision-based displacement, not a render time shading effect. The main advantage over the LW displacement is that it is done at the pre-processing time, on the Octane core side, so the scene extraction of the master low-poly objects should be a lot faster.

Thanks,
-Juanjo

Wed Sep 25, 2019 10:40 am

On the bright side, with vertex displacement we can control the density of displacement with subdividing the mesh more where we need it.

Wed Sep 25, 2019 12:22 pm

Same bug with this release and network rendering

Wed Sep 25, 2019 12:23 pm

Did you run the correct slave daemon ?

Wed Sep 25, 2019 12:36 pm

BorisGoreta wrote:Did you run the correct slave daemon ?

I guess ...
I reinstalled everything from the links given here

Wed Sep 25, 2019 12:39 pm

Well, if you have the same problem with the network rendering with this build, I'm afraid that nothing can be done until we get a new Octane 2019.1 core with this problem fixed. The only solution is to revert back to Octane 2018.1 ...

But please, check if you have updated the plugin and the Octane standalone in the network nodes to the right builds. In the plugin, you should check that the version is 2019.1.0.4 in the about window.

Thanks,
-Juanjo

Wed Sep 25, 2019 12:46 pm

juanjgon wrote:Well, if you have the same problem with the network rendering with this build, I'm afraid that nothing can be done until we get a new Octane 2019.1 core with this problem fixed. The only solution is to revert back to Octane 2018.1 ...

But please, check if you have updated the plugin and the Octane standalone in the network nodes to the right builds. In the plugin, you should check that the version is 2019.1.0.4 in the about window.

Thanks,
-Juanjo

That's what I've got on the master :

And on the slave :

Is it ok ?

Wed Sep 25, 2019 1:00 pm

Yep, if it doesn't work I'm afraid that the network rendering bug was also in the RC5 core build, although I had not seen any report about it. In any case, I hope that we could have soon a new Octane 2019.1 build with all these problems fixed.

Thanks,
-Juanjo