Nasty Vraydisplacementmod bug 3dsmax

[rita_sobral]

Hi,
I have come across a nasty bug, if I use an unsupported map in Vraydisplacementmod, I get a warning in Vantage

 [Wrn] Unsupported displacement type (1) for mesh 'mesh_displaced_2'

Fair enough, but then when I switch it for a supported map, it continuses to throw the error, even upon restarting max and restarting Vantage...

Even when deleting the Vraydisplacementmod on the mesh and adding a new, it still throws the error.

Even when creating a new mesh and a new Vraydisplacementmod it continues to throw errors and vray displacement does not work at all.

It completely breaks my file and in terms of using vray displacement...

Only on a new 3ds max file will it work again.

Is there some caching going on that I need to clear?

Vantage 2.5.1

[vladimir_krastev]

Hi, thanks for posting.
Are you using Live Link or not? If you are opening a VRayScene in Vantage make sure there is nothing left in it that is unsupported. Do you mind sending a test scene so we could see for ourselves?

2D Displacement mapping is not supported in Vantage. If you need to use 2D mapping instead of 3D mapping (this is the mode of your VRayDisplacementMod) then enable the "emulate 2D Displacement" checker:

[rita_sobral]

Live link, yes.

Not using 2D displacement.

I can reproduce this every time.

- Do a new scene in Max
- Add a plane
- Add the displacement modifier
- Start Live Link
- Add an unsupported map to the modifier, PhoenixFDOceanTex or Waves etc
- You will see warning in Vantage
- Switch the map to supported map, Noise etc
- Error continues to throw in Vantage,
- Restart Live Link, does not help
- Delete modifer add a new one, does not help
- Copy plane and add a new modifer does not help

[npg]

Displacement type "1" is Tangent vector displacement. We only support the Object vector displacement. I don't know why this is always selected by default, but if you switch to object or non-vector displacement it should work.