Hello,
I have a recurring problem with Vray displacement (a problem that is not specific to VRAY GPU from what I could quickly test by switching on CPU)
As soon as Displacement is set to “View dependent” and the maps used for displacement have a lot of small detail, the displacement shows subdivision “stages” that are very, very apparent in the rendering.
On the attached example, the effect is already relatively attenuated by the presence of SSS in the shader, but the reflection of the material shows the different degrees of subdivision very well.
There’s also a sense of direction in the displacement subdivision, with a “raking” effect that is, of course, not present in the displacement map (and seems not to follow any polygons flow).
I’ve tried all sorts of things to try and compensate for this kind of artect in the rendering, but nothing seems to work.
The edge lenth is of course a major parameter in this problem, but changing this value only more or less pushes the problem elsewhere without ever solving it.
I’ve also tested other types of displacement mapping, and changed my VrayBitmap settings, but nothing corrects the issue.
I thought this was linked to the view-dependent sudvision mode, but it turns out that this isn’t necessarily the answer.
Even when unchecking View-dependent (which is almost impossible to do for us in production) rendering artifacts persist in other places.
The two maps concerned by de displacement are very classic Quixel images in 8K mapped to UVW map planar combined with two or three other procedural maps (mainly distance texture).
These artifacts issue are mostly visible arround the middle of the screen, it seems to occure more near the border of the frame, rarely in the middle
My screen shot show a small part of the render. The bottom left corner of a bigger image (~1K screenshot on a 5K square final image)
Can’t saddly share the scene at all
No issue about Vram available, RAM or anything else (technically speaking).
3DSMAX 2025.3
VRAY 7.10.00
NVIDIA 572.16
Thanks for your time,
Nicolas
Hard to say exactly what’s going on without the scene, but there have been similar reports with displacement and close-ups. One thing that may be causing it is elongated polygons on the source mesh; another is general visibility of subdivisions, which is nearly unavoidable with close-ups unless blurring the texture or playing around with the filtering and Edge Length parameters. Also, in GPU, Cache Normals is always on, which sometimes yields unexpected results. What results are you getting with the CPU? And lastly, can you reproduce the issue on a simple scene and attach it?
@hermit.crab
Thanks for the fast answer,
I’ll try to provide you a cleaner and smaller version of the issue.
I’ve noted all the hypotheses raised and I’m looking into how to answer them as soon as possible.
Here is a quick screengrab of my polygons flow (I was aware of the issue with elongated polygons or polygons with too less subdivision, so I’ve “over” subdivided the scene already)
Displace “raking” issue is matching the polygons flow 100%
But the different subdivision level staging issue seems not to match any flow there.
I’ll do more test asap.
Thanks
Nicolas
@hermit.crab
Cache normals seems to be the ideal culprit at the moment.
I started, as suggested, with a CPU test without cache normals checked. Maybe still some raking (the SSS is much stronger so I’m not sure about this analysis), but the level of stage subdivision has disappeared (for some reason Tyflow sim does not want to apply SSS).
So I tested in GPU without “normal cache”, even if it seemed impossible on paper (I always check “normal cache” in GPU even if it’s supposed to be locked) and surprise, there’s a difference between GPU rendering with normal cache checked (my usual pipeline) and GPU rendering without normal cache checked (well, the raking is still there).
More to follow,
Thanks for your time,
Nicolas
Actually, unticking the View-Dependent option might help, since the issue “raking” may be due to closer objects getting more subdivisions than those further away from the camera (in this case, I suppose it’s pronounced because it is a close-up). Disabling “View-Dependent” should subdivide all objects equally (in world units). You need to play around to see what value gives the best results/performance.
Regarding the “Cache Normals” differences, it usually behaves like that when there are not enough subdivisions.
@hermit.crab
Correcting the “raking” effect by unticking the view-Dependent is definitely an option here for the closest objects (combined with the normal cache solution, I’m starting to fix all my rendering artifact worries).
That said, not using the View dependent on my entire set is a bit of a headache in terms of optimizing different manual subdivision levels on different parts of the set.
You can’t have the best of both worlds, you always have to spend a bit of time on it 
Thanks again for your time and expertise, thanks to these two solutions combined, I’ll be able to adjust my rendering.