Edit: I tried it with GSX, and indeed choosing "Gate 10" in GSX leads me to B5, not C7.
First, is not clear which airport you are referring to, and if you are using the SU10 Navdata API option in GSX so, let's try some general rules:
If you are not using the SU10 Navdata API in GSXNormally, GSX will read the gate names from the airport .BGL that comes with the scenery. The only thing you need to check here, if GSX has loaded the correct file ( checking the GSX airport customization page ).
- If the correct .BGL has been loaded, you can be sure GSX will show the gate names as they are in the scenery so, if they don't match real world, it's something the scenery developer must fix.
- If the wrong .BGL has been loaded, if the scenery has been bought on the Marketplace ( or it's part a default Premium airport ), its .BGL cannot be loaded because it's encrypted, so GSX would use the default airport data, unless you enable the SU10 Navdata API option.
- If the wrong .BGL has been loaded, but the scenery is not encrypted, the scenery might have been rejected because it's too big, and there's a way to change the maximum search threshold by changing the airportCacheMaxBGLSizeBytes setting as explained here:
https://www.fsdreamteam.com/forum/index.php/topic,17221.msg121243.html#msg121243If you are using the SU10 Navdata API- Nothing related to loading the right .BGL applies here. GSX will just make a Simconnect call to ask a list of the parking spots to the simulator, which will reply with data, no matter where its coming from.
- If you have conflicting sceneries, GSX will get everything from Navdata, conflicts included.
Be sure you had Disabled all 3rd party add-ons in the GSX Config panel, to prevent them to have their jetways replaced by GSX because, while when using the Navdata, GSX is smart enough to skip its own jetway replacement .BGLs to be added to its airport cache, when using the Navdata, there's no way to prevent them to cause a conflict if you don't Disable 3rd party airports as you should.
The disabling of 3rd party airports from GSX is made automatically:
1) when first installing GSX
2) when updating GSX
3) when you click on the "Exclude 3rd party" button in the GSX Config panel.
This means, if you install a NEW 3rd party scenery AFTER you install GSX, you MUST run the FSDT Installer again and click the "Exclude 3rd party" button again, to add the newly installed airport to the list of airports Disabled from GSX jetway replacement.
Or you can add its ICAO, which is also what you are supposed to do, in case the airport package doesn't conform to the official naming standard of
developer-airport-ICAO-airportname, so it won't be automatically recognized for exclusion.
I think this covers all possible cases of gate mismatching between GSX and a SCENERY, with "scenery" meaning "the data provided by the scenery".
Under no circumstances GSX will show the same parking names as in real world, UNLESS they have been set like that by the scenery developer, assuming all the issues of getting the right data has been solved.