Hi everyone- As updated on my website, we've announced the pricing for the VLC package- $65 NZD
This includes all the VLC data on the website (roads, rail, freeways, shorelines, water polygons, population layer, water class, raster landclass, VLC landclass, streams, VLC config tool, replacement ground textures, replacement autogen textures) as well as a brand new 20m DTM made specially for VLC.
I decided to include the DTM for a number of reasons- The new method of FSX water polygons ties it them to the DTM so it makes sense to include it (otherwise lakes etc may be at the wrong elevation when placed on a default DTM), overseas users or those that are new to FSX mightn't have a good quality DTM already and placing VLC on top of a default mesh would detract from the beauty of NZ (especially with the errors around Milford Sound and Mount Cook)
I did some testing of loading times between default, Red Baron and VLC DTM mesh and there is no difference in loading times (sometimes faster, sometimes slower but all within around a second of each other on my machine) so it is one of the few cases where more accurate data doesn't impact too much on performance!
Cheers
This includes all the VLC data on the website (roads, rail, freeways, shorelines, water polygons, population layer, water class, raster landclass, VLC landclass, streams, VLC config tool, replacement ground textures, replacement autogen textures) as well as a brand new 20m DTM made specially for VLC.
I decided to include the DTM for a number of reasons- The new method of FSX water polygons ties it them to the DTM so it makes sense to include it (otherwise lakes etc may be at the wrong elevation when placed on a default DTM), overseas users or those that are new to FSX mightn't have a good quality DTM already and placing VLC on top of a default mesh would detract from the beauty of NZ (especially with the errors around Milford Sound and Mount Cook)
I did some testing of loading times between default, Red Baron and VLC DTM mesh and there is no difference in loading times (sometimes faster, sometimes slower but all within around a second of each other on my machine) so it is one of the few cases where more accurate data doesn't impact too much on performance!
Cheers