I’m trying to render a heightmap to a render texture using an orthographic Scene Capture Component 2D placed above the scene. However, unless I crank up the render target resolution up to 4K (which requires 600+MB of VRAM for 32-bit floats), I get terrible artifacting for the Scene Depth.
Consider this 1K heightmap texture (scaled down to visible range):
It’s pretty clear to see the artifacts in the 1K version.
I really can’t think of any logical reason for this.
Further notes that could be helpful are that I’m using Forward Rendering, because this is a VR project, and the orthographic width is 100000. The Scene Capture Component 2D is 5000-15000 unit above the landscape surface.
The bright part is where the landscape clips through the capture component, but those aren’t important for my purposes.
That would make sense, and was my first thought as well, but the Scene Capture Component 2D does not have any LOD settings except “Detail Mode”, which has Low, Medium and High settings. None of those make a difference.
Well, I did just solve it. I went back and looked at the landscape actor itself and set the LODDistance Factor on it from my capture blueprint, took the capture, and then set it back to 1.0
That seems silly that a calculation made in the camera can’t be changed, and I have to override individual actors. If I had wanted to capture anything but the landscape, especially something dynamic, that would make it impossible or wildly impractical.
Nevermind, this is broken again for no known reason. The orthographic camera simply ignores all LODDistance Factor changes now, and in 4.19 LODDistance Factor was removed.
Update: Epic has totally removed the Landscape LODDistance Factor in 4.19 with the new landscape revamp, so there is no longer any way to set it, and the Scene Capture Component 2D ignores all other LOD settings it seems.
