Here’s a quick example of terrain produced with FS Earth Tiles. This is at fairly low level, and with 1 m/pixel resolution (resolution setting 1 in FSET). It took a while (I set it and went to bed), and the scenery is about 7 gb for the area from Mildenhall all the way to the coast.
You can see in the background where the default terrain kicks in. Dealing with the coastline and where the FSX water picks up is a bit of a pain, drawing the water mask etc. It’s certainly not hard, just something you have to mess with.
So if you have the disk space and time, you can have very nice hi res scenery for free, and without much more work then using google maps.
Alright, with a 2 m/pixel resolution, we’re sitting at 2.5 hours to render. For reference it has about 1/4 the number of tiles, so for 1 m/pixel resolution figure about 9 hours (overnight basically). Scenery size is right around 2.25 gb.
It looks pretty good! Even at 1400 baro altitude it looked great.
And finally 4 m/pixel. So total rendering time of ~35 mins, and total file size of about 590 mb.
How does it look you ask?
So in summary:
1 m/pixel, it looks great from 500’ AGL and above. It however takes a while to generate, and takes some HD space. If you’re flying real low, it might be worth it.
2 m/pixel, looks great from about 1000’ AGL, maybe 1500’ if you’re picky. More reasonable, both in time and space. The scenery still looks great, and very highly detailed. If you wanted the maximum detail for VFR flying this would probably be what I’d use.
4 m/pixel, it’s pretty pixelated below about 1500-2000’ AGL, but starts to look pretty decent as you near 4000’ AGL and higher. Generation time was pretty quick, and space usage was minimal. Realistically this is probably what I’ll use, unless I need super high-res scenery for some reason.