Broken rivers when landscape size is too large

[Feedlest]

Summary

When I add a river to my landscape, the river has a strange shape. It doesn’t ‘smooth’ properly with the landscape to achieve a nice shape, and then pieces of terrain are automatically generated on one side of the river. I would like to keep the ‘Affect Landscape’ ON as it already is.

These pieces of terrain shift as soon as I move the river or add splines.

My landscape is a default landscape (when an island is created), and I’ve added tiles (17x17 tiles) and it contains three layers: Water, Splines, and Layer.
I’ll provide more information if needed! Thank you.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

World Building

Steps to Reproduce

Create a project with an existing landscape and add several tiles.
Add a river and see what happens.

Expected Result

The river is supposed to fit properly into the landscape and have a nice shape without generating strange pieces around it.

Observed Result

The river has a strange shape. It doesn’t ‘smooth’ properly with the landscape to achieve a nice shape, and then pieces of terrain are automatically generated on one side of the river.

Platform(s)

PC

Upload an image

[Hardcawcanary]

Yes it gets so anomalous, I don’t use affects landscape and being able to get a river to work on a large terrain is really finicky.. I think that’s the right word.

The way the river uses the surrounding terrain to do its water thing, is fairly good on a terrain with small triangles, but does become problematic when you go creek or tributary size because of the ratio of river width needed to the terrain triangle size.

Because it seams to take into account a set range of vertices either side of the spline, in a large terrain, those vertices are too far out and not part of the river bed and messes up the river bed calculations or something

what works is using a hydro tool to make the cross section of the river shaped like a bell curve. this essentially ends up looking like an affects landscape river and puts a limit on the amount of detail that can go into the rivers look and the river cannot be too narrow without trouble.

The river depth and width settings at each node changes the scope of what landscape its detecting and becomes cumbersome and a bit unintuitive (not even a word spell checker ??, I guess it’s relative to my own intuition needs, but great for others)

I dunno, I dread making rivers, love making river beds, but filling them with water, even though the mesh is all nice and washed down with the hydro tool can become a pain.

With everything though the trial and error defines the thing, 3 months of making rivers on high poly terrain, you start to get it happening… but with low poly terrain its been like 12 months and I’m still not getting it, I expect just to be able to shape it right, but still randomly trying to find the sweet spot with all the vertices where the river works can take hours.

The landscape mesh visualiser overlay is very good and you can raise and lower individual landscape nodes with a small sculpt tool, very handy…

Sorry for raving on, a current sore spot

[Bug-Reporter]

FORT-965013 has been added to our ‘To Do’ list. Someone’s been assigned this task.

[Jared.Ritchie]

Hi @Feedlest ! Can you please verify that your landscape is exactly square (17x17 landscape components)? I’ve found a similar repro on a rectangle landscape (18x17) but have not been able to repro with a square configuration. Thanks for your patience!

[Feedlest]

Hi @jared.Ritchie ! It seems I made a mistake in my first post. I can also confirm I had no issue with a square landscape; however, my project was 15x17 components in size. The river therefore does indeed have a problem and disrupts the landscape in this configuration. I’m not sure how else I can help more precisely, so I’m attaching all the information related to my landscape and the river device. Thank you for your time.

message (11).txt (20,1 Ko)

these settings are the same for all the proxy

message (10).txt (6,5 Ko)