FTX works seamlessly with GEX. Essentially, Anthony's product simply overwrites the default FSX textures of your installation into the Scenery\World\Texture folder. We don't do that.
One of the most important design criterea for FTX was that it would be a complete unintrusive installation, i.e. we don't overwrite any default files at all, and FTX lives outside the base FSX texture folders, in its own ORBX folder. So far, we're been able to achieve 90% of that goal and hopefully 99.9% by release time. We are working with ACES to overcome some minor annoyances to achieve that goal.
Why are we so anal about ensuring FTX is a clean install and does not trample on default? Simple. We are using a regional approach, and when you cross into FTX regions you'll see FTX, and when you depart them you'll see default. We call this a "user friendly experience". There's no need to fiddle with switchers and manage the FTX installation. Just install and then go fly in the region you've purchased. In the long term, our users will love Orbx for the simplicity and zero maintenance approach we've taken.
What this means, in a nutshell, is that because we built FTX the right way, using 100% SDK functionality, FTX does not "clobber" any default or replacement textures and when you load our Pacific NorthWest region next year for instance, you'll see FTX inside the PNW region, and the moment you leave the region boundary you'll see default FSX textures (or GEX if you've installed that).
Bottom line: the two *will* work seamlessly together - giving you GEX as a base pack and FTX for the immersive experience on a regional basis.
There you go guys, best of both worlds, have your cake and eat it etc. Mind you, with GEX it will replace the textures, but the main problem with FSX is the landclass. I want to see a default FSX area with good landclass... maybe default textures would look good enough as a 'base' for flying over while waiting for the FTX region pack you want.
Cheers
Krigl
