Procedural terrain

Some older threads say that procedural landscape generation is impossible, hard, or not supported in the case where developers want to generate the landscape at runtime. The reason cited is that the editor creates collision data and LODs for landscapes, and no such step automatically happens at runtime.

However, since the code exists for creating landscapes in the editor, it pretty much implies the possibility of doing the same thing at runtime. That is, as long as you don’t mind writing the functionality yourself, duplicating editor code in a plugin, or including certain editor files in your distribution. Does that sound about right? Just looking at the source briefly, I’m pretty sure I can see where the addition of collision information is happening, at least.

If anyone has gone down a similar path, I would be interested to know about problems you ran into or concerns you would have doing it again. And any suggestions about specific source files to look into would be appreciated, but if not think I will find them just by poking around.