Multitexture map with VrayDisplacementMod

[Vizioen]

Dear Chaosgroup,

do you think it's possible to make the multitexture plugin work with the 2D (landscape) displacement mode of the displacement mod? Right now it only works with 3D displacement. Actually it "works" with 2D displacement but for some weird reason it takes on a different mapping than the one of the original material. Like it's not following the same randomization seed.

[Svetlozar Draganov]

2D displacement needs information in advance, I'm note sure whether MultiTexture map is calculated before or after the Displacement.
Can you share what would be the benefits for you to switch to 2D Displacement over 3D one?

[BBB3]

I speak only for myself here, but I never use 3D displacement. 2D is more RAM-friendly, calculates faster, looks better most of the time and with a little tweaking, can be applied to any types of models (not just landscapes).

[Drawehn]

Hi Betrand,
so how do you apply 2D displacement to brick walls when you need 'Edge continuity'? When we use 2D displacement we get gaps on all the edges...

We currently have a project with brick walls and 3D displacement takes forever so if there is a solution with 2D displacement, that would be great .

[BBB3]

Hi Stefanie. I use a negative shift value to close these gaps. You just need to eyeball the amount. It works fine in most circumstances although if you put your camera very close to the edge, you may see some interpenetration.

[Vizioen]

I speak only for myself here, but I never use 3D displacement. 2D is more RAM-friendly, calculates faster, looks better most of the time and with a little tweaking, can be applied to any types of models (not just landscapes).

Well I remember your tutorial with the old mighty tiles plugin, AFAIK this is also procedural, thus only available with 3D displacement. Or do you bake a very large map and then use it as a simple 2D displacement?

[BBB3]

If memory serves, Mighty Tiles created a seamless bitmap on the fly with a user-defined resolution, so it was useable for 2D displacement. To be honest, I have rarely used 3D displacement because of the time it takes to compute and the larger amount of RAM it requires. And it generally looks a lot blobbier than 2D.

[Drawehn]

Thanks Bertrand!

Yup, the 3D displacement takes a crazy amount of time and RAM.

[thablanch]

In all of my tests and production work, I was never able to get as precise displacement with 3d mapping. So using 2d gives better memory management and way better results in most situations.