Reading BGL files from the GSX MSFS folder even with the Navdata API enabled?

[kakugo]

Would it make sense to allow GSX to process any BGL file in the %APPDATA%\Virtuali\GSX\MSFS folder also when the SU10 Navdata option is enabled? This would allow to have the best of both worlds, while now the user has to choose between an option that gives the best results for the Premium and Marketplace airports and an option that gives the best results for the non-Marketplace airports, but not at the same time.

[virtuali]

Being able to read encrypted files is not the only one benefit of using the SU10 Navdata.

Another major benefit is not having to deal with an airport cache, and possibly have to keep up with future changes to the .BGL format that, if not followed in the software, might easily cause crashes when trying to read an undocumented file format that might have changed.

Using both methods at the same time, seems to be the worse of two worlds instead, because you would add all the added complexity from having to deal with an airport cache, together with the usage of the SU10 Navdata.

Also, considering the SU12 SDK will update the Navdata API to give us informations we couldn't get before, not even when reading the airport .BGL, like not having any way to know which door a jetway docked to, or if it docked partially, or if the jetway has a non-standard structure, it's not really worth spending any time on reading .BGL, since after SU12 ( assuming the updated API will work as expected ), we plan to make the Navdata API the default.