Purchased airports from MS MarketPlace

[moonbst1]

I have been waiting for GSX for the last 2 years since MSFS released.
For the convenience of managing all the airports in one spot, I purchased all my airports from MP (MarketPlace)
Now I am so screwed !!

I Hope FSDT has some plan to work with MS MarketPlace. 
Hey MS !! You should work with FSDT !!  Open the DRM encrypted files and folders which is so unnecessary.

[virtuali]

With SU10, there will be a new API in the SDK we can call to get the data we need about an airport, without having to open its .BGL file directly, and this will solve the problem of Marketplace airports.

The API is still in Beta, we are already working on integrating it with GSX, is still not complete ( it miss data about jetways, jetway links and runway starts ), so there's no telling exactly when it will be usable by GSX, but you can be sure we'll use it as soon is ready to use and has all the data we need.

[Dervakon]

Hi,

I hope so all airport will work because this is the answer from LVFR

http://www.latinvfr.org/forum/viewtopic.php?p=7107#p7107

Thanks

[virtuali]

I hope so all airport will work because this is the answer from LVFR

Every developer is free to reply to his customers the way they see fit, and it's their own business decision whether they want or not offer customers of the Marketplace version of their product to not feel they have purchased a more limited version.

Marketplace airports can't be read by Little Nav Map too, and there might be other products I'm not aware of that might need the airport data for any reason, likely something related to improve AI traffic flow, for example so it's not as if we "created a problem", the problem has been there since MSFS came out, it's nothing "new" or "caused" by GSX.

But again, this will all go away when new Facilities data from SU10 will be out of Beta, so sceneries bought on the Marketplace will be as compatible with any program that need to read airport data for any reason.

[moonbst1]

But again, this will all go away when new Facilities data from SU10 will be out of Beta, so sceneries bought on the Marketplace will be as compatible with any program that need to read airport data for any reason.

Really appreciate this rapid response. Can't wait to use GSX pro near soon.

[DaBeLG]

With SU10, there will be a new API in the SDK we can call to get the data we need about an airport, without having to open its .BGL file directly, and this will solve the problem of Marketplace airports.

The API is still in Beta, we are already working on integrating it with GSX, is still not complete ( it miss data about jetways, jetway links and runway starts ), so there's no telling exactly when it will be usable by GSX, but you can be sure we'll use it as soon is ready to use and has all the data we need.

Hi are you speaking with asobo on this or are you guessing they will include jetway data(knowing asobo and sdk  ) i allready own 25 marketplace airports so thinking to refund gsx pro !!!

[virtuali]

Hi are you speaking with asobo on this or are you guessing they will include jetway data

Of course we have asking Asobo for this feature, several times but, of course, we cannot possibly know when they'll add it, if ever. They just confirmed the missing Runway Start will be added, so at least they don't seem to be opposed adding the missing features.

[DaBeLG]

Hi are you speaking with asobo on this or are you guessing they will include jetway data

Of course we have asking Asobo for this feature, several times but, of course, we cannot possibly know when they'll add it, if ever. They just confirmed the missing Runway Start will be added, so at least they don't seem to be opposed adding the missing features.

thnx for the quick responce maybe make feature request so gsx pro customers can vote just an idea

[virtuali]

thnx for the quick responce maybe make feature request so gsx pro customers can vote just an idea

The Asobo Devs forum is open to registrations, so everybody can sign up and Vote the Idea:

https://devsupport.flightsimulator.com/users/register.html

This is the link to vote for it:

https://devsupport.flightsimulator.com/idea/10563/simconnect-addtofacilitydefinition-missing-definit.html

[Copper]

I hope so all airport will work because this is the answer from LVFR

Every developer is free to reply to his customers the way they see fit, and it's their own business decision whether they want or not offer customers of the Marketplace version of their product to not feel they have purchased a more limited version.

The guys from LatinVFR tried to contact you but didn't (yet) get a response since they were looking for a way to distribute the BGL files the same way you do it for the FSDT airports if the user bought them via Marketplace.

Apart from that they are now trying to find a way to provide their customers with the needed BGL files for their airports, so at least the workaround will work for LVFR.

The creators for LHBP seem to have provided their BGL directly to the creator of the INI so it's included in the ZIP. I hope this approach gets more and more common since it is easy for the devs and users get the files they need to install them into the same folder.

[Cygnific]

How does GSX handle duplicate airport.bgl names like; objects.bgl? Does a rename to ksan-objects.bgl and lebl-objects.bgl work?

[Dervakon]

How does GSX handle duplicate airport.bgl names like; objects.bgl?

Just change the name of the object by the name of the airport

Ex CYYZ

object.BGL by CYYZ_AP.BGL

and drop it here %APPDATA%\Virtuali\GSX\MSFS

[Cygnific]

How does GSX handle duplicate airport.bgl names like; objects.bgl?

Just change the name of the object by the name of the airport

Ex CYYZ

object.BGL by CYYZ_AP.BGL

and drop it here %APPDATA%\Virtuali\GSX\MSFS

Nice, thanks!

[virtuali]

How does GSX handle duplicate airport.bgl names like; objects.bgl? Does a rename to ksan-objects.bgl and lebl-objects.bgl work?

There's no need to rename anything, a .BGL it's always related to an ICAO internally ( regardless how it's called ), so GSX won't use an .INI file for an airport you are not currently in, so this case you made an example of, is already sorted.

The only case in you need to rename a .BGL, is if you need to place both files in the GSX profiles folder (because BOTH are encrypted, so you have unencrypted versions of both), and they happen to also have the same exact name, so one must be renamed, because you can't have two files with the same name in the same folder.

[Copper]

The only case in you need to rename a .BGL, is if you need to place both files in the GSX profiles folder (because BOTH are encrypted, so you have unencrypted versions of both), and they happen to also have the same exact name, so one must be renamed, because you can't have two files with the same name in the same folder.

But in that case you'd need to rename it in the corresponding INI file as well. Otherwise GSX won't match them.