{"id":728,"date":"2019-07-17T07:52:48","date_gmt":"2019-07-17T07:52:48","guid":{"rendered":"http:\/\/www.world-machine.com\/blog\/?p=728"},"modified":"2019-07-17T07:58:25","modified_gmt":"2019-07-17T07:58:25","slug":"3026-erosion-improvements","status":"publish","type":"post","link":"https:\/\/www.world-machine.com\/blog\/2019\/07\/3026-erosion-improvements\/","title":{"rendered":"3026 Erosion Improvements"},"content":{"rendered":"\n

The Erosion device has been upgraded in build 3026. As World Machine’s most popular device, all changes to erosion have to be a bit cautious; but I think you’ll enjoy what’s to come \ud83d\ude42 <\/p>\n\n\n\n

Eroding into river channels<\/h2>\n\n\n\n

The ability to erode into river channels has been around for a while, but it really hasn’t worked the way you want, especially when “Geologic time enhancement” is enabled. This became increasingly obvious with the new automatic rivers in 3025; doing any kind of strong erosion would either sink the river deep underground or leave it hanging out over the terrain like in the first image below.<\/p>\n\n\n\n

It took much longer than I expected to hit upon a good solution to this problem. But the default behavior is now way better:<\/p>\n\n\n\n

\"\"<\/a>
No more hanging rivers \ud83d\ude42<\/figcaption><\/figure>\n\n\n\n

Light years better! The river now feels fully integrated into the terrain, without the odd “buried or hanging” effect in first first image.<\/p>\n\n\n\n

However, in some cases.. when we do massive erosion after placing rivers… it’s still not enough. This made me think more about what we’re actually trying to achieve when eroding a world that already has rivers placed.<\/p>\n\n\n\n

Achieving Equilibrium<\/h3>\n\n\n\n

For example, here’s an example world based that has had extreme erosion performed after placing rivers. At first glance it looks fine. But look closer…<\/p>\n\n\n\n

A great amount of rock has been worn away. 3026 ensures that the terrain around the river is roughly preserved, and it is.. but that means that the river ends up running down the ridges<\/strong> of the terrain!This would be.. unusual <\/em>in real life \ud83d\ude42<\/p>\n\n\n\n

\"\"<\/a>
One usually doesn’t see rivers running down a ridgeline (left side)…<\/figcaption><\/figure>\n\n\n\n

Let’s back up. What’s causing this problem? <\/p>\n\n\n\n

Our desire to fix the river paths to their existing location is what causes us this trouble. In reality of course, the water channels are the primary agent of terrain change, and down-wear in concert with the rest of the terrain. What we’re trying here with a fixed river location is not physically plausible. <\/p>\n\n\n\n

The solution is : uplift.<\/p>\n\n\n\n

Uplift<\/h4>\n\n\n\n
\"\"<\/a>
The terrain around the river has slowly uplifted during erosion, maintaining the river’s location at the bottom of local valleys<\/figcaption><\/figure>\n\n\n\n

You now have the option of slowly having the earth raise beneath the terrain undergoing erosion. This provides the forcing function we need to keep the rivers in their proper place at the valley floor.<\/p>\n\n\n\n

I think you’ll find this to be quite useful!<\/p>\n\n\n\n

Preserve Edges<\/h4>\n\n\n\n

Build 3026 also makes sure the “Preserve Edges” option is A) no longer broken \ud83d\ude09 <\/strong> and B) interacts well with uplift. <\/p>\n\n\n\n

When enabled, map edges are effectively sediment sinks (just like if you specified a river\/sink mask), and play well with uplift. This lets you carve into the terrain automatically as uplift happens:<\/p>\n\n\n\n

\"\"<\/a>
Uplifted erosion without and with “Preserve Edges” set<\/figcaption><\/figure>\n\n\n\n

What’s happening in the comparison above is that the edges are being forced to their initial values in the bottom image. This creates the elevation differences that erosion needs to continue working; in the top image, erosion has essentially reached an end-state, where all large structures have been worn away.<\/p>\n\n\n\n

Mask Structure<\/h4>\n\n\n\n

Finally, a new useful control has been added to Erosion: Mask Structure. The wear\/sediment\/flow masks are incredibly useful for texturing, but getting a good look from them has been counter-intuitive in the past. This has been fixed, and you can now simply set the structure slider lets you control how detailed\/smooth you want the mask information to be.<\/p>\n\n\n\n

\"\"
Sliding the Mask Structure from 0..1<\/figcaption><\/figure>\n\n\n\n

Better Geological-time Enhancement<\/h2>\n\n\n\n

As a final short aside, this control has been made much more fluid\/controllable\/predictable in terms of results. Without going into all the details…. I think you’ll like it.<\/p>\n\n\n\n

About that compatibility…<\/h4>\n\n\n\n

With all these changes, it’s worth talking about compatibility. Erosion is now versioned, which lets us both preserve old behavior and also simplify things a bit.<\/p>\n\n\n\n

You’ve probably noticed that Erosion pre-3026 has a bunch of odd compatibility check-boxes. This is due to making small improvements over the years without the benefit of the device versioning system. In order to preserve the old behavior, there needed to be a checkbox. And then, sometimes there wasn’t <\/em>one, leading to changes when you didn’t want them…<\/p>\n\n\n\n

Now that versioning is in place, we can remove some of them:<\/p>\n\n\n\n

\"\"
Simplified Erosion dialog<\/figcaption><\/figure>\n\n\n\n

The compatibility options have been distilled down to some of the essential ones. If you load an older world, you’ll see more of the old options appear.<\/p>\n\n\n\n

\n\n\n\n

That’s it for now! 3026 should be coming out very shortly for you to play with the changes; after a short bugfix interval it will then drop to release channel as well.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Erosion device has been upgraded in build 3026. As World Machine’s most popular device, all changes to erosion have to be a bit cautious; but I think you’ll enjoy what’s to come \ud83d\ude42 Eroding into river channels The ability to erode into river channels has been around for a while, but it really hasn’t […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"publish_to_discourse":"","publish_post_category":"","wpdc_auto_publish_overridden":"","wpdc_topic_tags":"","wpdc_pin_topic":"","wpdc_pin_until":"","discourse_post_id":"","discourse_permalink":"","wpdc_publishing_response":"","wpdc_publishing_error":"","footnotes":""},"categories":[2],"tags":[],"class_list":["post-728","post","type-post","status-publish","format-standard","hentry","category-world-machine-development-news"],"_links":{"self":[{"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/posts\/728","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/comments?post=728"}],"version-history":[{"count":11,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/posts\/728\/revisions"}],"predecessor-version":[{"id":748,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/posts\/728\/revisions\/748"}],"wp:attachment":[{"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/media?parent=728"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/categories?post=728"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.world-machine.com\/blog\/wp-json\/wp\/v2\/tags?post=728"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}