Evaporating and then recreating sea level with new shorelines does not lead to clean shoreslines

Reproduction Steps

  1. Open up a new place
  2. Upgrade to new shorelines
  3. Generate terrain water using “sealevel” terrain tool
  4. Clear it
  5. Regenerate it

Expected Behavior

Expected result: Terrain is smooth

image

Actual Behavior

The terrain isn’t smooth. Instead, it exhibits old terrain behavior, which is unfortunate. Also, there’s no way to upgrade again, which is annoying.

Issue Area: Studio
Issue Type: Other
Impact: Moderate
Frequency: Often
Date First Experienced: 2023-02-15 00:02:00 (-08:00)

7 Likes

Maybe they fixed this? I tested your procedure several times and kept getting the ‘new’ shoreline look.

I am having issues with the conversion lowering the sea level though. And it also seems to erode away the land if its too thin at the sea level (if the land ends just barely below the sea level i get weird results)

It creates a weird looking undercut, here I have evaporated the water again to show the strange erosion it created:

So instead of a nice shoreline i get this undercut:

If I move the sea level up enough, it will generate nice shoreline as expected without changing the land at all.

1 Like

I think that you can fix that problem adding a part and using the function Terrain:FillBlock() with the part CFrame and size

I was able to work around this strange ‘undercut’ issue by removing all water(I had some other levels of water that weren’t removed when trying this before). After removing all traces of water then putting it back the water level worked properly without eroding the land areas.

Yes, the original issue in this thread was fixed since March 21st.

Regarding the erosion - the conversion is not touching the solid values at all. It just adds some extra water at the shallow shores.

But it is likely that the old shape (before the upgrade) was already eroded. It is just that in the old algorithm, water was actually morphing the vertices of the solid where they touched. You can check this by doing evaporate in the old version (before upgrade) to see what it actually looks like.

This way or another, the conversion can’t be perfect. It only handles the most simple most common cases. The expectation is that for complex specific cases (like that one probably is) - the authors will adjust the results accordingly after the conversion. I would be concerned only if you can’t get the look that you need by editing it after the upgrade. (And yes, some tools still have bugs with that that we are aware of - should be fixed by next week.)