Work continues on the Terrain Engine.
As I mentioned in previous updates, the terrain uses fewer polygons in flat areas and more in uneven areas. This is nice, but we can still do more. For example, Polygon density is the same all over the terrain. A better idea is to have it be more agressive in removing polygons in the distance. Stuff that is far away could be much simpler. Let’s see:

This time, the lower-left shows the normal optimization, and on the upper-right is the one where it removes more polygons in the distance. As you can see, close up they work the same, but in the distance I’m now using a lot less polygons. I’m all the way down to 65,195 polygons! That is a reduction of about 88% from our first terrain. We can see the difference at this point, but the differences are subtle and easily worth the massive savings.
I’ve added some code to look at the shape of the land and color it accordingly. The high grass is pale, the lowland grass is deep, lush green. Steep banks are dirt-colored. High banks are grey (rock) colored.
Note that all of this is simple vertex coloring, just to give an idea of how the terrain might look if used in a game of some sort. This is cheap and simple, and will be replaced later in the project by something more robust.

Now it’s starting to look like something. However, the surface is so smooth and the color changes are so gradual that the whole thing looks like dull plastic. That’s not what I want. Let’s give it a texture.

That makes a big difference! The texture I’m using is very simple: it’s just random greyscale noise, like a low-contrast version of television snow. Still, the small variations of brightness really brings the surface to life. All these screenshots so far have been from the same position for comparison, but there is a lot more to the terrain. Let’s look at it from another angle:

I want to point out that I am avoiding adding lots of fancy effects to the scene. I could make this look much more striking by using dramatic lighting (sunrise or sunset shading), adding a proper horizon (so this isn’t a square island floating in space), adding clouds, sun, lens flares or any number of other scene-enhancing effects. Without these, things may look bland, but it also means I won’t be propping up a lame system with a lot of makeup. The time to add that stuff is later.
The Mistakes DOOM Didn't Make
How did this game avoid all the usual stupidity that ruins remakes of classic titles?
id Software Coding Style
When the source code for Doom 3 was released, we got a look at some of the style conventions used by the developers. Here I analyze this style and explain what it all means.
Denuvo and the "Death" of Piracy
Denuvo videogame DRM didn't actually kill piracy, but it did stop it for several months. Here's what we learned from that.
Object-Oriented Debate
There are two major schools of thought about how you should write software. Here's what they are and why people argue about it.
The Death of Half-Life
Valve still hasn't admitted it, but the Half-Life franchise is dead. So what made these games so popular anyway?
T w e n t y S i d e d
This is really good! And really readable! You have a real gift for explaining complicated things without sounding patronising.
Agreed with Zagzag. I have absolutely no understanding of programming, but I’m still fascinated by this entire project.