Developer's Backdoor > GSX Backdoor
Issues with GSX Level 2
gilsonc:
In my case, I purchased Level 2 already and am very happy with the software. But for some reason, I cannot create any "Exclude.bgl" file, and although I read all the manual and this part (creating Exclude.bgl) maybe three times. Tried on three airports Heathrow, Sydney and Amsterdam Aerosoft, and the removed jetways are still there...
I think I used FSDT GSX Control Panel correctly, Everything worked as showed in the video and the manual, except the ols jetways are still there :-[
Where exactly should these files be located ?
Please help
virtuali:
--- Quote from: gilsonc on September 08, 2018, 10:09:38 pm ---Where exactly should these files be located ?
--- End quote ---
Addon Manager\Fsdreamteam\Exclude\Scenery
But the GSX Control Panel should clearly indicate if it was able (or not) to create the Exclude file so, there's no real need to check it manually.
--- Quote ---Tried on three airports Heathrow, Sydney and Amsterdam Aerosoft, and the removed jetways are still there...
--- End quote ---
Are you trying to remove static or animated jetways ? Not all statics can be removed, they must be modeled separately from the terminal building.
Speedbird ATC:
--- Quote from: virtuali on September 08, 2018, 09:36:43 pm ---
--- Quote from: Speedbird ATC on September 08, 2018, 09:09:22 pm ---As you can clearly see in the screenshot, I did customize the entire airport with exclusion zones. As you can also see, NONE of the new SODE jetways are in the right position!
--- End quote ---
GSX obviously reads the jetway position from the AFCAD so, they cannot be "wrong". OF COURSE, if you started customizing the airport with an AFCAD conflict, it's entirely normal nothing will match.
So, before doing any customization, first check if the right AFCAD is in use by GSX, and if it's not, understand why and fix the conflict before customizing.
--- End quote ---
Deleted the ORBX AFCADS. Unfortunately bridges still appear where they shouldn't. Is GSX unable to detect where they should and shouldn't be? It's a small issue that I can fix myself I guess, but I would like to know if I am doing this right https://i.imgur.com/Ub0isTy.jpg
virtuali:
--- Quote from: Speedbird ATC on September 09, 2018, 12:04:37 am ---Unfortunately bridges still appear where they shouldn't.
--- End quote ---
That's not a bug, it exactly how it's supposed to be.
The jetway that apppears "by default", is one that has the same specs as the original DEFAULT jetway, which already comes with a bridge and ground markings, so this is the model you are supposed to use to replace the default jetways in the default scenery. It's designed to be as similar as the original one as possible, just much better looking, and using SODE.
It might still be useful in case you have a non-default scenery, which incidentally happen to have its original jetways placed at a distance that's compatible with the default jetway bridge size.
But normally, when customizing a non-default airport, you are supposed to choose another model, one that doesn't come with a bridge, but allow you to select one from multiple variations AND allows you to select/unselect ground markings, for example.
--- Quote ---Is GSX unable to detect where they should and shouldn't be?
--- End quote ---
It obviously isn't. How could GSX possibly know how the rest of the scenery is made which kind of bridge (if any) should be chosen ? How do you expect it to interpret a bunch of polygons (this how a scenery raw data looks like) and understand which one is the terminal wall ? Even assuming we *tried* something as complex and still useless as trying to read the whole scenery, polygon by polygon...
mroschk:
No, i report just that is is not possible to change a high amount of gates at a airport just with one lick.
Yes, you can create the Exclude file for all Gates with one click, but the set up of the new Sode Gates after that takes a long time,
because we have to do it for every gate
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version