Vray Enmesh not working properly.

V-Ray V-Ray for 3ds Max Issues
1

Hi everyone, I need some help with Vray Enmesh modifier.

I am using it to recreate a wicker effect on the doors of some furniture. It is a really powerful tool and it works well, I have succeded into using it and the effect it’s really dope BUT sometimes it disappears completely in the rendering.
For instance I’ve noticed that it disappears if you “hide” the tile source object under the floor level BUT sometimes it disappears without any understandable reason.

It’s making me really crazy, I need to do a video so I absolutely need to understand why it disappears, I can’t afford to risk it :frowning:
Am I the only one having trouble with it?

I can’t post much because is kinda “top-secret work” but here you are some screenshots, a closeup of the wicker, one with the properly effect and the other one with the enmesh not working ( therefore the plane with the enmesh modifier becomes invisible and you can literally see whats behind it, in this situation you see just a flat surface)

I am using 3DSMAX 2021 and Vray 6 1.2 ( 6.10.08 build 00000 )

Thanks in advance,
(Sorry for my bad english)
Mattia

.jpg.jpg
.jpg.jpg384×373 57.6 KB

.jpg.jpg
.jpg.jpg300×295 20.9 KB

.jpg.jpg
.jpg.jpg300×295 15 KB

2

Hello,

Thank you for posting. Please make sure that the enmesh gizmo is fit in object space, otherwise it might crop the source object or be completely out of its bounding box which would produce incorrect results.

Best,
Philip

3

I´m pretty sure that´s how it´s supposed to work, but I also struggle with it.
It has great potential to mess up your scene if you move or delete the object by accident and I hardly see any advantage.

In my opinion it would be better if it “follows” the object.
It would be even better if it would keep a copy the object in the modifier (like the sweep modifer or RailClone) if you delete the object, but not sure if this is possible.

4

The enmesh gizmo should automatically move with the source object and it seems that the behavior has changed . We already have that registered in our internal bug-tracker under VMAX-13060 for further investigation. Thanks for pointing that out and sorry for the inconvenience.

Best,
Philip