See readme
Version 1.06 GSX Pro compatible with 2.2.7
- Adjusted de-icing stop positions and de-icing walls with the new editor
- Gate 326 / 328 / 330 are now dummy positions for de-icing purpose and radius adjusted for 326/328 (smaller aircraft)
Version 1.05 GSX Pro
- Adjusted the stop positions
Version 1.04 GSX Pro (make sure to have the latest GSX Pro version 2.2.3 > update)
- Remote de-icing pads according to real life added
- Remote de-icing
Remote de-icing can be performed on one of the following locations see AD 2.EBBR-GMC.07: - De-icing platform W:VHF frequency for de-icing platform coordinator, contact 129.805 (8.33 KHZ CH)
offers two de-icing stands for aircraft:W22 up to ICAO code C
W21 up to ICAO code E
pilot shall confirm ICAO aircraft code to the de-icing coordinator
in case TWY W21 is used by aircraft greater than ICAO code C, TWY W22 becomes unavailable until aircraft on TWY W21 has vacated TWY W21
simultaneous de-icing on TWY W21 and TWY W22 is possible for aircraft up to ICAO code C only
note that the two de-icing stands are not on the same level, pilots shall thus line up with the de-icing stop of their assigned de-icing pad and not line up with the aircraft on the adjacent pad
de-icing platform W cannot be used when RWY 01 or RWY 19 is in use
when de-icing platform W is active, TWY F4 is restricted to ICAO code C aircraft
De-icing platform M, on TWY M:VHF frequency for de-icing platform coordinator, contact 121.730 (8.33 KHZ CH)
offers one de-icing stand for aircraft up to ICAO code E
de-icing platform M is not available during arrival peaks
when instructed by ATC to proceed to de-icing hold position pilot shall make sure to position aircraft correctly on de-icing hold position
after de-icing pilots shall await further instructions from ATC before taxiing from the de-icing stop position
De-icing platform South:VHF frequency for de-icing platform coordinator, contact 129.805 (8.33 KHZ CH)
offers three de-icing stands for aircraft:stand 326 and 330 up to ICAO code C
stand 328 only ICAO code D and E
pilot shall confirm ICAO aircraft code to the de-icing coordinator
after de-icing, stands to be vacated via lead out lights in front of aircraft after contact with ATC
in case stand 328 is used, no aircraft allowed on stand 326 and 330
simultaneous de-icing on stand 326 and 330 is possible for aircraft up to ICAO code C only
ATC will provide taxi clearance up until the holding point to the remote de-icing platform. After which pilots will be requested to contact the platform coordinator on VHF FREQ indicated above according de-icing platform assigned or await instructions by manual hand signals from the de-icing platform coordinator. - Upon completion of de-icing, pilots will only contact the GND FREQ after having received the confirmation of the platform coordinator that the platform is clear.
Version 1.03 GSX Pro
- Edit bug at gate 161 and 162 push back not facing east
- Several of the L and R gates became available due to latest GSX update will add those too (will add the L and R gates which one is available via GSX)
- Unfortunately I can't add both...
Version 1.02 GSX Pro VDGS safedock@ T1S-42 system with Simbrief integration on all gates
- All gates GSX Pro VDGS safedock@ T1S-42 wall mount with Simbrief integration
- Minor tweaks
- Missing pax route added at terminal south 1
- Due to the scenery the follwing gates aren't available via GSX Pro 208 209 215 227 231 232
Version 1.01 still available with Aerosoft VDGS system.in place
Version 1.01 minor update:
- Changes apron 9 cargo handler to Swissport
- Minor tweaks
Ok version 1.0 is here close to the real world as possible, some small tweaks to do.
See chart for explanation what is available:
Green Areas close to real life possible:
- Custom airlines per gate (Shengen non Shengen)
- Custom pushback routes
- 3.2.2 Apron 1 North
- Standard procedure:
- All aircraft on stands 120-142 and 160-174 shall be pushed on TWY INN, nose facing East.
All aircraft on stands 144-158 shall be pushed on push line (white dotted line) without interference on TWY INN.
Traffic facing East, pull forward no further than stand 158.
Traffic facing West, pull forward no further than stand 144.
Aircraft shall join TWY INN from the push line via the shortest way.
No taxi along the push line is allowed.
3.2.3 Apron 1 South - Standard procedure:
- All aircraft shall be pushed back on TWY R4, nose facing East.
No simultaneous push-back from stands 145L and 204 allowed.
3.2.4 Apron 2 North - Standard procedure:
- All aircraft shall be pushed on TWY S, nose facing East.
- Special procedures:
- Stand 204: all aircraft shall be pushed on the push line and pulled forward until lined up on TWY S no further than stand 208.
No simultaneous push-back from stands 204 and 145L allowed.
3.2.5 Apron 2 South - Standard procedure:
- All aircraft shall be pushed on TWY T, nose facing East.
- Special procedures:
- Stand 205L: all aircraft shall be pushed on the push line, and pulled forward until lined up on TWY T no further than stand 209.
3.2.6 Apron 3 North - Standard procedure:
- All aircraft shall be pushed on TWY U, nose facing East.
- Special procedures:
- Aircraft ICAO code F shall be pushed onto TWY T.
Stand 312: all aircraft shall be pushed on TWY, nose facing West only.
3.2.7 Apron 3 South - Standard procedure:
- All aircraft shall be pushed on TWY INN 10, nose facing North.
3.2.8 Satellite (apron 3) - Standard procedure:
- All aircraft shall be pushed on TWY Z, nose facing East.
- Special procedures:
- Stand 354: all aircraft shall be pushed on TWY INN 10, nose facing North
Stand 305: when pushing on TWY Z, nose facing West, all aircraft shall be pushed via lead out line, and pulled forward abeam Strip 1.
3.2.9 Apron 51B - Standard procedure:
- All aircraft shall be pushed on TWY R2, nose facing East.
Remark: stand 510 power out only.
3.2.10 Apron 60 North - Standard procedure:
- All aircraft shall be pushed on TWY INN 2, nose facing East.
- Special procedures:
- Stand 680: all aircraft shall be pushed on TWY INN 2, nose facing West only.
3.2.11 Apron 60 South - Standard procedure:
- All aircraft shall be pushed on TWY R2, nose facing East.
3.2.12 Apron 9 - Standard procedure:
- All aircraft shall be pushed on TWY N1 ot TWY N2, nose facing East or West at ATC discretion.
- Special procedures:
- Stand 950: all aircraft shall be pushed on push line and pulled forward, until lined up on TWY N1.
Stand 951: all aircraft shall be pushed on TWY N2, nose facing West only (in case of A380 push-back only allowed under supervision of airside inspection).
Stand 959: when push-back nose facing East, pull forward until abeam stand 961.
Stand 969 and 970: when push-back nose facing West, all aircraft shall be pushed on push line and pulled forward abeam stand 969.
Stand 971: when push-back nose facing West, all aircraft shall be pushed on lead-in line stand 971, and pulled forward abeam stand 969
- Custom pax routes into the terminals or at the stands
- Custom placement of the groud vehicle routes to avoid conflicts and logical placement
- Stands 120 - 126 - 134 - 138 custom VDGS with simbrief integration
Red gates terminal South 2 not available
Red Areas:
- default GSX
Pull doesn't work so tried to make a work around here but this file is as close to real life possible.
Installation:
- Unzip and place/save the *.ini file in your directory (your drive):\Users\(your usr name)\AppData\Roaming\virtuali\GSX\MSFS
- (Not needed according the manual but sometimes GSX doesn't detect the BGL file so replace the path in the ini file with your local installation path in case of AFCAD problems.
[general]
afcad_path = \\?\Your local path\aerosoft-airport-ebbr-brussels\scenery\EBBR\scenery\EBBR_Placements.bgl)
Tip:
- Make sure to run GSX cfg (via FSDT installer) and run the exclude 3d party option to avoid double gates!
(do this anyway after each update of GSX)
Download the latest offline update installer for FSDT
http://www.fsdreamteam.com/forum/index.php/topic,26826.0.html
Tested also with SU11 latest 1.30.12.0 and Fenix A320 - PMDG737 -Inibuild A310
Remark:
There is a conflict/issue with Aerosoft EBBR with overlapping ICAOs - EBBR (civilian sector) and EBMB (military sector). With SU10 Navdata API enabled, GSX will only recognise EBMB it seems.
Easy solution is: to add the following to [GSX] section of the %APPDATA%\VIRTUALI\CouatlAddons.INI file
[GSX]
airport_visibility_EBMB = 0
For everyone, the file is on the official FSDT forum.
Products Support -> GSX Support MSFS -> GSX Pro - Airport profiles -> EBBR Aerosoft
1 years ago
Life Saver!
1 years ago
stevemartis
Gecko
Great GSX profile! pls reupload it/coninue it so others can enjoy it aswell
1 years ago
He deleted account
1 years ago
Rick2909
Rick2909
Re upload it
1 years ago
AdriaAirways19
Any chance to re-upload? 😊)
1 years ago
Framsen
Hello, could we download your file on another website maybe? Your work looks fantastic! Thanks!
1 years ago
simpaty
Hello,
As Flightsim.to withdraw their policy, do you consider re uploading the file ?
thx
1 years ago
basiledesquiens
Great work on such a big airport. Some stop positions are a bit to far forward. There was a GSX update a while back which moved unedited stop positions a bit. You might want to have a look at that 😀 other than that 10/10 though
1 years ago
done thanks for the tip Simon appreciated
1 years ago
Deleted Account
SimonTricks
Hi, I do not know, what is going wrong, when searching for the parking positions in GSX, I get gate 1 which is gate 240, gate 2 corresponding to gate 238 and so on. What did I wrong or what did I miss to set up? Many thanks in advance for some hints 😊
1 years ago
Which scenery do you have?
1 years ago
Deleted Account
peterzopes
Hi, would it work with Justsim scenery?
1 years ago
Is based on the Aerosoft scenery so unfortunately not.
1 years ago
Deleted Account
Josrash
Do you get the scenery also with the addon? Im new to GSX
1 years ago
No you have to purchase the scenery @ Aerosoft ;-)
1 years ago
Deleted Account
Oliin008
Today I flew into EBBR in the PMDG 737-800. After I landed and vacated the runway, I brought up the GSX Pro menu to find a suitable gate to park at. Ended up picking gate 206L. I also used the follow-me service and once I stopped at the gate, GSX told me the parking space was too small for my aircraft.
This doesn't make sense to me after I checked the maxwingspan parameter in the airport config ini file which I found was set to 36 meters. Where the wingspan of the 737-800 is 35.8 meters. So shouldn't have been a problem?
One other odd thing was how GSX Pro started deboarding by itself. Never seen this before. Also, this happened without any of the doors having been opened nor the jetway attached. So the result was how the passengers started deboarding the aircraft through a closed door and then carried on in the air where the jetway was supposed to be. In the same way, the bags were coming out of the aircraft on the baggage belt even when the cargo doors were not opened.
Not sure if all this was related to bugs in GSX or something not fully correct for this gate in this airport config file.
1 years ago
That should be a GSX bug...
1 years ago
Deleted Account
WebMaximus
Which Brussels is this for?
1 years ago
the one it says in the title
1 years ago
AwesomeBlack
Dash8Dave
Hi
Thank you for providing this - im getting the no parking at airport message. I have also added the path location as per the instructions and even then i get same message - would love some help
thanks
1 years ago
I have the same Problem Please Help .
1 years ago
luca568
donkey20048
It says `there are no parking spots in this airport` when I use this file. I placed the ini file in the correct folder. I am using the `navdata API enabled` option since I purchased the airport from the msfs marketplace. any ideas?
1 years ago
Not needed according the manual but sometimes GSX doesn't detect the BGL file so replace the path in the ini file with your local installation path in case of AFCAD problems.
[general]
afcad_path = \\?\Your local path\aerosoft-airport-ebbr-brussels\scenery\EBBR\scenery\EBBR_Placements.bgl)e
1 years ago
Deleted Account
feruzumcu
Hey. This also works for the Just Sim version? if so anything needed for the path location?
2 years ago
Unfortunately not
1 years ago
Deleted Account
ZMLM79