SimpleHydrology VS sprator

This was generated using an erosion simulation (source-code: https://github.com/weigert/SimpleHydrology).

You can find the code here: https://github.com/weigert/SimpleHydrology

SimpleHydrology now supports infinitely large maps. This was solved by making a memory pool for all map properties, requesitioning buckets for individual map-nodes and rewriting the erosion code to run on these chunks. The limit is really your memory now (and patience).

Full, updated and cleaned code now available here.

The full code is available here. Written in C++ with TinyEngine.

I have been playing with my SimpleHydrology system [Github Link] over the holidays and decided to implement momentum conservation for the particle-based erosion system. This, together with some minor parameter tweaks, lets me get nice meandering river behavior.

This is a simulation of wind flow over procedural terrain using my own GPU accelerated implementation of the lattice boltzmann method. All implemented and visualized in TinyEngine (by me). Terrain generated using SimpleHydrology (also by me). The source for this is not released (yet!). This scene is 100% procedural.

With a better visualization of the streamlines, some performance optimization and nicer procedural terrain (generated using SimpleHydrology) this looks really nice!

Sure, full source here.

Sure, I can outline some basics. You can also read this thread for a small discussion.

I also realise Sprator (deservedly) got a fair bit of attention on here when it was released, and I'd like to avoid any perception of plagiarism; I have been working with these grid symmetry algorithms for some time (as have many before me), and the implementation we use for Discomon is significantly more extensive than what I have employed here.