Landscape occlusion problem: changing x/y bounds?

Dear [fill in your name here],

I’m currently having a problem where my landscape components get rendered just a tiny bit too late when moving the camera around a mesh on the x/y axes. It results in ugly flickering triangles of sky around the edges of the mesh when I move, which is something I’d like to avoid. My suspicion was that the bounds for the landscape components are set too narrow on the x and y axes, which I’ve checked with the r.VisualizeOccludedPrimitives command and indeed seems to be the case (they are set exactly to the size of the component, so it’s rendered only at the moment that it comes into view).

I’ve searched high and low, but it appears that setting bounds on the x and y axes is not possible for landscape components for some reason. Changing the negative and positive z bounds of the components did not change anything, as would be expected since the z axis is not the issue. Is there any way in which I could solve this problem, other than not using landscapes?

Yours sincerely,
Bartender