Landscape rendering Bug

NailGUNNERX · September 9, 2016, 1:17pm

Hi,

after upgrading to Unreal 4.13, I encountered a serious rendering bug in Unreal. If I change LODBias of a selected section in a landscape, section become invisible. You can see the bug in the picture below.

I always make distant sections higher lod, but it is not possible in current version. For instance, in another map, distant not playable sections used to render only 25k triangle, but now its 900k, because I could not use the feature.

Best,
Nail

PS: Problem might be related to this new feature.
New: Added a scalability CVar for landscape LOD biasing (r.LandscapeLODBias), which can have a huge impact on triangle count and help low-end vertex bound GPUs.

anonymous_user_b9532c9a · September 9, 2016, 5:44pm

Hi NailGUNNERX,

I believe this is expected behavior. You are setting LODBias to 3, but ForceLOD is set to -1, if you set this to a higher value it should render correctly.

NailGUNNERX · September 9, 2016, 6:32pm

Hi ,

thanks for quick response, this used to work in previous versions. In version 4.13, it renders those parts correctly in other view modes such as wireframe, unlit, detail lighting, etc… But it does not work with Lit View Mode.

If I do following operations, landscape become visible again but temporarily. After changing Landscape Mode to Place Mode from the left Modes panel then, I select Landscape from World Outliner. Then lanscape renders correctly as long as landscape is selected.

Moreover those properties do different things, Forced LOD enforces LOD to target number. For instance, if I set Forced Lod to 3, its always 3, regardless of the distance to the camera However, if I set LODBias to 3, it starts with 3rd LOD and when camera go far, it changes LOD to 4, 5 ,6 respectively.

Consequenly, this feature used to work in previous versions. Currently, it only does not work with lit lighting.

Best,
Nail

NailGUNNERX · September 9, 2016, 10:02pm

I thought post will automatically reply yours, but it doesn’t. In case my answer do not give you any notification, my post can be seen below.

anonymous_user_b9532c9a · September 12, 2016, 4:59pm

I have entered a bug report, which can be viewed here. You can track the report’s status as the issue is reviewed by our development staff.

NailGUNNERX · September 13, 2016, 4:33am

Thanks

robyrom · June 26, 2024, 9:57am

Hi @NailGUNNERX and @anonymous_user_b953c9a ,

I’m facing a very similar and frustrating issue: movie render queue is not properly rendering my landscape when I “zoom out” the camera actor.

For example if I set the Z-axis of the camera at 1000meters the movie render large balck areas instead of landscape:

If I set Z-axis of camera actor on 200m, for example, then movie render exports properly as you can see here:

What kind of variables I have to edit?

Maybe LODs or Culling distances or texture wrapping in landscape material? Or maybe Movie Render options?

Maybe RVTs are not working properly?

… Or maybe is a UE bug and it forgot the source input masks and texture of landscape (such as opacity masks in landscape layers, textures, etc…) ?

Any advice is really appreciated! Kind regards.
Roberto