ive not really used enmesh very much, but ive found a good use case.. ive got a pine tree in the foreground of an image, the leaves are opacity mapped planes with a sprig of pine needles on each… the client isnt happy with how it looks, so im testing enmesh to replace the texture on each plane with an actual model of some pine needles. it looks quite promising, HOWEVER, if i though densely layered opacity mapped leaves were slow, enmesh is WAY slower. is this normally the case? any way to speed things up? scene is illuminated with a hdri on a domelight, and a direct light with vrayshadows.
i though densely layered opacity mapped leaves were slow, enmesh is WAY slower. is this normally the case?
Enmesh is generating geometry, if this is high poly one it is expected to be very heavy for rendering. It will be best if you could avoid showing that much detailed greenery in the foreground.
I recently tried to use Enmesh for the speaker grill in a headphone. It was very promising when doing IPR + Denoising but in production rendering the area got so painfully slow that I ended up changing it to a simple normal + opacity map which rendered super fast. Not sure what was the issue as everything else was rendering fast as well. I used one of the preset geometry from the Cosmos library. I had the feeling it had to do with the Enmesh itself but didn’t have much time to investigate further…
Hi, I can’t say much without a scene. You could send it for review and we will continue from there. Also I can test the Cosmos preset you mention. Which one is it?
If you have the memory can forcing static rather than dynamic geometry for the enmesh help?