An interesting read for sure- Thanks for the link.
From my/Vector Land Class perspective, we do have some advantage of hindsight- Reading the various problems that both developers and end-users have had in trying to manage changes to the core-scenery system in FSX meant that I made the decision fairly early on in the piece that that wasn't a path that I wanted to pursue.
The 'problem' with Orbx and UTX is that they rely on changes to the scenery.cfg and terrain.cfg.....it does allow them to do some really cool stuff, but it makes it really hard to manage from their point of view. If there was only one addon developer in the world, there would be no problem, but as soon as you have a few developers each trying to tweak the config files on users computers, problems are bound to occur. Those files are simply something that have not been set up in a way that allows easy tweaking.
VLC makes no changes to these files- It is much more traditional in its approach as an 'addon scenery'. All our data will be contained in its own folders so installation/uninstallation should simply be a case of removing that folder or turning it off in the scenery library. It has meant that some cool features which I would have liked to do have had to be removed from the scope of the project but having stuff that works is better than stuff that doesn't.
We are fairly lucky in NZ I think because, due to our small size, we are fairly tight knit bunch of developers covering small number of airports and a small number of addon packages. This makes it easier to get things right.....but FSX is still a very complex beast. All part of the fun
