Displacement wrong placement - any ideas why? Tweet

[ThomasVandenAbeele]

Hi!

I have a displacement behaving weirdly, and I can't seem to figure out why... The attached screenshot shows a circular mapping, with the letter N in the middle. The image is placed correctly in the diffuse channel, but the same texture hooked up to displacement is placed and scaled wrongly.

Does anyone know why it behaves this way?

Thanks!
Thomas

[promity]

Just check if your model have UV texture coordinates.

[ThomasVandenAbeele]

Is that the same Promity from the Kray forum? If so, hi Promity! Nice to meet you here as well

The model has UV texture coordinates - as is visible from the mapping of the texture on the diffuse channel. Or did you mean something else?

[juanjgon]

Hi,

Do you have any kind of transformation in the UV map parameters in the texture sampler node? This could explain this behavior, but if you want to share the scene I could take a look at it.

Thanks,
-Juanjo

[ThomasVandenAbeele]

Hi Juan,

No transformation in the UV map parameters. However, I discovered the error today: the displacement keeps using UV map 1, even though you specify UV map 2 in the texture sampler node.

This causes the wrong mapping, and the disconnect between diffuse mapping and displacement mapping: the texture sampler is set to use UV map 2, and diffuse uses this correctly, but displacement incorrectly still uses UV map 1.

Is this a known issue? Is there a workaround for this?

[promity]

Is that the same Promity from the Kray forum? If so, hi Promity! Nice to meet you here as well

Yep, hello )

[juanjgon]

Hi Juan,

No transformation in the UV map parameters. However, I discovered the error today: the displacement keeps using UV map 1, even though you specify UV map 2 in the texture sampler node.

This causes the wrong mapping, and the disconnect between diffuse mapping and displacement mapping: the texture sampler is set to use UV map 2, and diffuse uses this correctly, but displacement incorrectly still uses UV map 1.

Is this a known issue? Is there a workaround for this?

What Octane version are you using? I think that this issue was fixed in the Octane 2018.1, or at least in the latest just released Octane 2018.1.1 ...

Thanks,
-Juanjo

[ThomasVandenAbeele]

I'm still using version 3, so that explains why the bug is still in there!

But as I understand it, putting the UV for displacement in slot 1 is a perfectly good workaround, right?

[juanjgon]

Yes, I suppose that the displacement from the first UV map should always work fine.

Thanks,
-Juanjo