Not sure what exactly is going on here but at some point I started to expand my landscape for more room. As I did this, it started to ruin some of the other layers, most notably the Water layer for Lakes and Rivers.
Took me a bit to figure all this out but as you add to the landscape at some point it goes “out of bounds” and corrupts the water layer data. Likely some sort of landscape resolution mix-match issue.
I ended up expanding my landscape as much as I could to form a square without it corrupting the other layers.
I tried to import heightmaps to fix but they would never take properly.
Normal / Working:
Adding one more square in either direction, heightmap gets all messed up:
The problem is you - and epic.
You because you dare to use landscape in the first place. That’s a big issue in itself but maybe you can’t help it, so I can give you a pass on it…
You again, because you dared to “expand" a landscape. This one you don’t get a pass for… It’s a “no no” that is well documented.
And lastly epic, because they suck.
It’s been over 4 years and they still haven’t fixed the fact that the water stuff for their sub-par landscape system completely fails when the landscape isn’t exactly square…
So, well, with that in mind you can probably fix things yourself….
If you insist on using the landscape system remeber that:
Heightmaps are not artistic files, but Data.
The size of a landscape directly impacts the poor performance of a project.
The number of landscapes is always at least 4 concurrent when dealing with multiples (in world composition)
Landscape LODs of components is size-on-screen based, making fine tuning near impossible if not on an ad-hock case basis. So you can’t change sizes and expect scene load to be OK.
And last but not least. Try looking up how to use Houdini as a DCC for creating/managing landscapes if you really must make use of it long term…
Otherwise, consider just making meshes in any DCC of choice. Then your project will just work and perform a lot better too…
