Hey guys,
just wanted to check because I can not find anything in the docs: 2D Displacement does not support UDIM, right?
It should work on both 2D/3D displacement. Is that not the case on your end? Do you see it if the tex is set as diffuse?
Not the case on my end. Lele already got the scene file.
It does work when displacement is set to 3D, with 2D only the first UV tile is read.
Any news on this? The quality of 2D displacement is magnitudes higher in this case, because I am running out of RAM with 3D before getting comparable detail.
Well, actually not running out of RAM, but straight crashing to desktop.
I have been told UDIMs are supported for 2d displacemetn with standalone, not in Max.
So, you may get lucky that way.
Sadly not, as our whole workflow is centered around 3dsMax and V-Ray 6.
Is this something that can be improved in the coming releases? I mean, if it is working in standalone, it proves that it can be done technically.
I assume you tried disabling Tight Bounds and Cache Normals? Tight Bounds is on by default I believe.
(in order to deal with the memory/crash issue, not the bug you are encountering)
Not for the number of shots I have to deliver and automatically stack for Photoshop. The workflow is centered around Pulze scene and render manager.
What are the limitations that prevent using 2D displacement with UDIM in Max?
If that’s the case then buying enough ram to fit the 3d displacement is likely your only timely option.
Well, I do not know if RAM is the issue. We got 128gb on our machines. In the preparation phase RAM amount raises to around 50gb, and then V-Ray either prints an Embree-related warning or just plain crashes to desktop.
I told you the working render of one such tyre with 3d displacement needed close to 64 GB.
You tried to render four of those in 128, without raising edge lenght, the math falls haf the size short.
Here, clearer:
As mentioned in mail, you’ll need to raise edge lenght if you plan on sticking it into the ram you have.
That is true.
Raising the edge length though results in a visible loss of detail.
So yeah, if 2D displacement can be made to work with UDIM in 3dsMax, that would be great!
It hasn’t happened in a decade, it’s unlikely to happen in a timeframe that will aid you.
You have been given workarounds, more than that we can’t promise, sadly.
I know, but it would be great to have that feature in the future. 
Had a chance to test this today. Disabling tight bounds made no difference, V-Ray still prints an embree-related error message during scene preparation.
I can get the scene to render by disabling the pre-tesselated checkbox, but then the render itself is unbearably slow.
Darn. Yeah, disabling pre-tesselated is always sooo slow, but it doesn’t need much memory (try using Brute Force /Brute Force and Bucket rendering with pre-tesselated off, otherwise most of the geo gets loaded anyway-- but I don’t think that is much faster).
I have had some scenes where tight bounds saves a ton of time (not sure if it uses less memory, maybe a little).
You saw the thread about longer lenses and displacement? It seems that can be an issue with memory as well.
Yes, I saw that thread and already replied to it. It might play a role in the scenes I tried to render, too.
In the sample i have screenshot above the lens is a 42mm. Hardly qualifiable as “long”.
Your issue is that you’re trying to render a 30MPx image covered in displacement 1px in edge length, within 128 GB of ram.
That won’t fit, period.