LibTessDotNet VS Interactive Data Display for WPF

here's a lib that unity itself uses AFAIK: https://github.com/speps/LibTessDotNet

I do the shrinking multiple times and every time I move the curve a little more forward. This gives me a strip (the area between the two curves). I then turn this into a mesh using triangulation. I formerly used LibTessDotNet (https://github.com/speps/LibTessDotNet) but then switched to Poly2Tri (http://github.com/MaulingMonkey/poly2tri-cs). Poly2Tri gave me better results and support for custom points within the mesh (Steiner Points). I needed that because all my lighting is vertex based. In the end I combine all those meshes into one static mesh. Finally I optimize and compress it and save it in the scene. It's a little hard to explain without pictures so I made one here: https://kamgam.com/reddit/2.5d-terrain-generation.jpg

A short story / cautionary tale of the last time I had to add a chart to an old application: I had a project that needed to make use of Microsoft's Interactive Data Display [formerly Dynamic Data Display or 'D3']. I don't recall what feature it was that was specifically being asked for, but D3 did it and was the only real option outside of springing for one of those massive/pricey component libraries. If you want to talk about how silly it is to create an entire separate process to wedge a WPF control into a WinForms app as a MDI child, that communicated via pipes, I've got notes. In short: the tech may be dated, but I always welcome more WinForms controls.