Cinema 4D version 2019.1.3 (Stable) 03.11.2019

[frankmci]

Does displacement mixer work?

As for me, it either doesn't work, or crashes the moment I use it.

FYI, I'm getting instant crashes, too, C4D R21, Octane 2019.1.3. New scene, make Octane material, make Displacement Mixer node, connect Mixer Node to Displacement Pin>crash.

I haven't had the time to trouble shoot it yet, but know that it's not just you. I'll try to document it properly over the weekend.

(edit)
Preliminary test seems to show that a bare Displacement Mixer node will cause an instant crash when hooked up to a Material, as will a Displacement Mixer node with only one incoming Displacement node. A Displacement Mixer node with two incoming Displacement nodes works fine.

So my guess is that something is expecting a particular kind of input, and then is very unhappy when it doesn't get what it expects. Give the Mixer two inputs, and everybody is happy when you link the Mixer to the Material. Depending on the order of operations you follow, you might never see this. I'll do more testing and generate proper crash logs tomorrow.

[FullHPetroL]

displacement Mixer is rock solid here with 2019.1.3, maybe you have an issue with Nvidia driver.
To make it works in your scene you need to change the Displacement type to Vector Displacement, and change the Map type to Height.

CAD88B9E-DD80-4C8A-80BD-9E121AFD2325.jpeg

ciao Beppe

So, displacement mixer doesn't work in the texture mode, only vertex?

[AaronWestwood]

Not sure if this is a known thing, but on a large enough object, in this case a box, with an index on 1 we get some severe artifacts. Ray Epsilon doesnt help here either. Ive just jumped from 2018 release, and this didn't happen there (I use this big box workflow + medium shaders on pretty much all my projects for years).

Has anything changed in 2019?

AW

[MyDearestHao]

Not sure if this is a known thing, but on a large enough object, in this case a box, with an index on 1 we get some severe artifacts. Ray Epsilon doesnt help here either. Ive just jumped from 2018 release, and this didn't happen there (I use this big box workflow + medium shaders on pretty much all my projects for years).

Has anything changed in 2019?

AW

I have also encountered this problem, please set the index to 1.01 or smaller.

[aoktar]

Not sure if this is a known thing, but on a large enough object, in this case a box, with an index on 1 we get some severe artifacts. Ray Epsilon doesnt help here either. Ive just jumped from 2018 release, and this didn't happen there (I use this big box workflow + medium shaders on pretty much all my projects for years).

Has anything changed in 2019?

AW

Always put a sample scene to help the case. So we can check it with a less effort.

[aoktar]

Does displacement mixer work?

As for me, it either doesn't work, or crashes the moment I use it.

FYI, I'm getting instant crashes, too, C4D R21, Octane 2019.1.3. New scene, make Octane material, make Displacement Mixer node, connect Mixer Node to Displacement Pin>crash.

I haven't had the time to trouble shoot it yet, but know that it's not just you. I'll try to document it properly over the weekend.

(edit)
Preliminary test seems to show that a bare Displacement Mixer node will cause an instant crash when hooked up to a Material, as will a Displacement Mixer node with only one incoming Displacement node. A Displacement Mixer node with two incoming Displacement nodes works fine.

So my guess is that something is expecting a particular kind of input, and then is very unhappy when it doesn't get what it expects. Give the Mixer two inputs, and everybody is happy when you link the Mixer to the Material. Depending on the order of operations you follow, you might never see this. I'll do more testing and generate proper crash logs tomorrow.

Provide us some sample scene and more data. Because I don't encounter the issue yet! And always write driver version because some drivers are really bugging us.

[AaronWestwood]

Not sure if this is a known thing, but on a large enough object, in this case a box, with an index on 1 we get some severe artifacts. Ray Epsilon doesnt help here either. Ive just jumped from 2018 release, and this didn't happen there (I use this big box workflow + medium shaders on pretty much all my projects for years).

Has anything changed in 2019?

AW

Always put a sample scene to help the case. So we can check it with a less effort.

Here we go:

https://www.dropbox.com/s/s8yj658wo60il ... E.c4d?dl=0

Everything default, just a 500m x 500m x 500m cube, spec shader, index at 1 Do you also see the artifacting?

[aoktar]

Everything default, just a 500m x 500m x 500m cube, spec shader, index at 1 Do you also see the artifacting?

Yes! Same result with standalone too

[AaronWestwood]

Everything default, just a 500m x 500m x 500m cube, spec shader, index at 1 Do you also see the artifacting?

Yes! Same result with standalone too

Oooooo funky funky. Hopefully an easy fix?

[aoktar]

Oooooo funky funky. Hopefully an easy fix?

Don't know because it's a core issue not plugin. Best to report it to Otoy team