Presents - BluePrint Simulations · Parking spot configuration and airline gate assignments Technical support and contact information Scenery fixes and upgrades Acknowledgements Scenery

OnDuty Support Systems LLC. 2007 - 2013 All rights reserved. 1

Presents

http://www.blueprintsimulations.com/



Contents Scenery Description Scenery Features Software Compatibility Suggested Hardware Configuration Installation Instructions Parking spot configuration and airline gate assignments Technical support and contact information Scenery fixes and upgrades Acknowledgements

Scenery Description BluePrint Simulations CYUL, Montreal – Trudeau (formerly Dorval) International Version 2 depicts Quebec’s most important airport as it exists during the winter of 2013 in full three-dimensional detail (BluePrint’s “True3D”). The scenery includes custom-made, highly-detailed, accurately-textured and fully three-dimensional models for the main terminal complex including the air-traffic control tower, the new US Trans-border facility and the Marriott hotel. It also includes four piers (or concourses): domestic, satellite, international and US trans-border, each featuring accurately located boarding gates and the corresponding aircraft parking positions. Each gate features individually configured jetways, custom-made and when appropriate airline-branded static service vehicles as well as realistic night-lighting and ramp illumination effects. Most gates also feature simple yet realistic parking alignment aids. All 3D models feature high-resolution (32px/meter) custom-made textures with high-quality transparency effects. Our scenery also includes the vast majority of maintenance and general aviation facilities located within the field’s boundaries. Highlights include the new deicing pad and fire station; Bombardier’s manufacturing facilities (Bombardier Ltd is one of the world’s leading regional and business aircraft manufacturers); the Air Canada’s and Air Transat’s maintenance hangars; and the general aviation facilities located west of the passenger terminal and at the northeast corner of the field. Most aircraft maintenance and storage hangars are fully three-dimensional and usable. As it is characteristic of BluePrint sceneries, CYUL v2’s entire field is located as accurately as possible to match official aeronautical publications (Note: Version 2 corrects the slight misalignment in the original version 1 scenery). The scenery includes a set of high-resolution, high-quality terrain replacement textures based on real satellite images and featuring seasonal changes. The replacement textures are intended to reproduce the actual terrain at the immediate vicinity of the airport and are painstakingly blended with the surrounding terrain to appear realistic during a normal approach to any of the runways. All three runways feature accurately located and fully three-dimensional approach lighting systems and navigational-aid antennae. All taxiways feature taxiway signs and ground markings including flashing lights at every runway/taxiway intersection. Taxiway signs are carefully positioned to facilitate taxiing in the simulated environment. Finally, our scenery includes a highly-detailed AI traffic mapping file (AFCAD) featuring accurate airline-gate assignments (optional). A complete listing of gates including aircraft wingspan limitations and airline assignments is included below.


Scenery Features

Custom-made, optimized Gmax models of the entire facility including the main terminal and four piers (domestic, satellite, international and US trans-border), the air traffic control tower and all relevant general aviation, aircraft maintenance and cargo facilities within the field’s boundary.

Custom-made, high-resolution textures for all Gmax generated models including transparency effects.

Custom-made, high-resolution photo real ground textures depicting seasonal changes and carefully blended with the surrounding terrain.

Accurate runway and taxiway layout including detailed markings and signs.

Realistic taxiway and ramp markings and ramp illumination effects

Two levels of scenery complexity and detail: o NORMAL complexity includes terrain texturing, autogen vegetation, airport layout

with taxiway signs and basic navigation equipment models (actual localizer and glide slope radio signals are available regardless of the scenery complexity setting), most buildings within the field’s boundaries including the terminals, the air traffic control tower and cargo and maintenance facilities.

o VERY DENSE complexity adds detailed instrument approach lighting system models, animated runway intersection lighting, and static ramp vehicles (optional).

Advanced, custom-made AI mapping file including realistic gate and parking spot layout as well as airline gate assignments. A basic AI mapping file without gate assignments is also available as an option

Software Compatibility FS2004 (FS9) and Windows XP, Vista, 7 or 8 (All versions) Note: A FSX compatible version is available and sold separately. Please visit our web site for additional information.


Suggested Hardware Configuration

BluePrint sceneries are designed to work properly in the average computer at the time of each release. For optimum performance while taking advantage of most scenery features we suggest the following hardware configuration:

Intel Core Quad CPU or better (Q9300 @ 4 x 2.50 GHz fully tested)

4 GB RAM (fully tested) nVidia 8000 series video processor with 256-bit memory interface and 512 MB dedicated video memory or better (nVidia GeForce 8800 GT fully tested). nVidia 9000 series video processor and 1 GB dedicated memory may be required for best performance when using the VERY_DENSE scenery complexity setting (nVidia GeForce 9800 GT fully tested).



Installation Instructions

1. Download the installer and save it in any folder of your choice. The installer is a file labeled CYULv2.1.1.exe.

2. Double click on the file labeled CYULv2.1.1.exe to run the scenery installer. 3. Please read carefully and make sure that you understand all the terms of the End User

License Agreement (EULA) before continuing with the installation. 4. Select the folder where the scenery will be located. The installer will search your

computer hard drives for the location of the Microsoft Flight Simulator and suggest a path to a folder to be created inside the folder containing the simulator’s files. If it cannot find the simulator it will suggest a path to a folder to be created inside the folder where the simulator files should be located if the suggested default path was used during the simulator’s installation. You may choose any installation path at this point as long as you are able to locate the folder containing the scenery files in order to add the scenery to the simulator’s scenery library as explained below.

5. Complete the installation by following the onscreen instruction. 6. Run the Flight Simulator and add the new scenery to the scenery library as follows: 7. Upon starting the flight simulator the following screen should open:


9. If you have setup your simulator to skip this screen at start up, you can reach it as

follows:

Press the “Esc” key or from the main menu bar, under “Flights” select “End Flight”.

Confirm “End Flight” on the next screen:

Now select “Settings” on the screen shown in step 7. The following screen should open:

10. Select Scenery Library … The following screen should open:


11. Select Add Area … 12. Navigate to the “FS9_root_directory”\BluePrint Simulations\ directory

Note: in a standard installation, the directory will be: C:\Program Files\Microsoft Games\Flight Simulator 9\BluePrint Simulations If you specified a different directory during installation of FS or the BluePrint scenery, please navigate to the directory you specified to find the scenery files.

13. Select the CYUL folder (Select only, do not “double click”) 14. Press OK 15. The CYUL directory should appear at the top in the Scenery Area list shown in the

following image: (KCLE is used in this image as an example. CYUL should appear at the top instead).


Note: the scenery may be moved down on the list. You must ensure, however, that it is located above any other add-on that may affect in any way the scenery and/or terrain at CYUL’s location or its immediate vicinity (This includes regional or global terrain add-ons).

16. Press OK and restart the Flight Simulator

In some instances, an incompatibility issue between FS2004 and Windows 7 or 8 prevents the user from adding new sceneries to the FSX library using the standard procedure. Please visit the FAQ section of our web site for the latest information regarding the addition of new sceneries to the FS2004 library when running the Windows 7 or 8 operating systems. Please note that detailed instructions for scenery activation may also be found in the FS2004 help menu.


Parking Spot Configuration and Airline Gate Assignments As a fundamental rule, we seek to represent the airport as closely as possible to real life using every resource available in the flight simulator. By default our sceneries are configured to handle ATC operations and AI traffic as realistically as possible based on direct observation and/or airline gate assignment information available to the public via the airport’s official website. Consequently, aircraft parking spots are configured to accommodate specific aircraft types according to the actual gate configuration and the airline and aircraft type that use that gate most often in real life. In order to ensure proper ATC and AI traffic operations you must take care of a few items that we consider and assume to be simple and basic knowledge for any user interested in our high-performance sceneries. If you are interested in AI traffic and realistic ATC operations you must ensure that your aircraft, be it the one you are flying or any AI traffic, is properly formatted as described below. MSFS’s parking spot configuration is based on the aircraft’s wingspan and the location of its center of gravity (or C.G.) as specified in each individual aircraft model. The model refers to the simulated aircraft (i.e. MSFS’s default B747-400) as opposed to the aircraft in real life! Consequently, proper handling of an aircraft by the AI traffic engine will depend on the proper configuration of the aircraft model by each individual flight simulator aircraft designer. The wingspan and C.G. location parameters are not easily accessible to the user so we must rely on the aircraft designer to accomplish the task properly. Improperly formatted aircraft models are simply not supported by our sceneries. As scenery designers we do have access to the parking spot configuration and we are not only able but required to set at least four parameters: location as lat/lon coordinates, heading, radius and type. We are also given the option to specify a few other parameters including airline, and pushback direction preference. The values assigned to each parameter will determine the way any given aircraft will be handled by the simulator air traffic control engine. There is no way at this point to instruct the traffic engine to park or direct any given aircraft to any specific parking spot (or gate). All we can do is set parking spot parameters to provide the traffic engine with a basic set of rules to follow. Assuming that the aircraft models are properly formatted, the simulator’s AI traffic engine will accommodate AI aircraft in the available parking spots according to the parameters mentioned in the previous paragraph. The most basic parameters that we must consider are the location and heading. While heading is straightforward and simple to understand, location is not. The location of a parking spot is defined by a set of latitude/longitude coordinates. It is essential to understand that all the simulator’s traffic engine can do is position aircraft that geographic location using one single point in the aircraft visual model as a reference. That point happens to be the C.G. It is also important to understand that the location of the front gear, the point actually used in real life to park an aircraft at the gate, is essentially irrelevant. The next parameter to be considered is the parking spot radius. For any given parking spot, this parameter defines the maximum size of the aircraft that will be parked at that spot by defining a circular area around the parking spot location as defined above. All the simulator’s traffic engine knows is that the aircraft must fit within that circular area using the model’s wingspan as a reference. It is important to understand that this parameter only sets a restriction on the maximum size of the aircraft that will fit on a given spot. It sets no restrictions on the minimum size at all.


As all aircraft types and models have different wingspans and C.G . locations, not all aircraft will fit perfectly in each parking spot. For example, a Boeing 737 aircraft may not fit perfectly in a parking spot configured to fit a Boeing 777 aircraft. The front gear on a B777 is much further away from its C.G. than that of a B737 is from its own C.G. Nonetheless, the simulator’s AI traffic engine may park a B737 aircraft in a parking spot configured for a B777 aircraft and it will not account for the need to move the B737 forward so that its front wheels end up at the same location where the B777’s front wheels would be as it is done in real life. The bottom line is that by properly formatting the parking spot radius all we can do is prevent the simulator’s traffic engine from parking a B777 aircraft in a parking spot that will only fit a B737 or smaller aircraft because otherwise it would end up impelled in the terminal building or its wing will crash with the aircraft parked in the adjacent gate. This is particularly important when, as in real life, some parking spots are designed and configured to fit only smaller aircraft. In our effort to represent the airport as it is in real life we have also chosen to assign specific airlines to each terminal gate by setting the optional parameter mentioned above. Detailed information about the gate assignments is provided below. The option to disregard airline gate assignments is now provided during installation of our sceneries. Please note that for a given aircraft to be directed toward or parked at a gate assigned to a specific airline the aircraft must be properly formatted. There are two parameters that must be configured within the “aircraft.cfg” file associated with each flyable or AI traffic aircraft. It is not enough that the aircraft is labeled according to the corresponding airline texture applied to each instance of a given aircraft model. You must make sure that the aircraft designer has properly formatted those two parameters for each texture associated with a given aircraft model or you must add those parameters to the aircraft.cfg file yourself. This can easily be accomplished by editing the aircraft.cfg file using a text editor such as “Window’s Notepad”. The two parameters are: A parameter that defines the type of parking spot to be used. Values may be GATE for passenger terminal gates, CARGO for cargo ramp parking spots and MILITARY for military ramp parking spots and RAMP for general aviation ramp parking spots. A parameter that specifies the airline such that the AI traffic engine can identify it. Consequently, each instance of a given aircraft as defined in the aircraft.cfg file must contain these two lines: atc_parking_types= atc_parking_codes= The following fictitious example corresponds to a properly formatted MSFS default 737-400 aircraft displaying textures representing the “Southwest Airlines” livery [fltsim.0] title=Boeing 737-400 Southwest Airlines sim=Boeing737-400 model= panel= sound= texture=SWA kb_checklists=Boeing737-400_check kb_reference=Boeing737-400_ref ui_manufacturer=Boeing


ui_type="737-400" ui_variation="Southwest Airlines" atc_id=N737 atc_airline=SOUTHWEST atc_flight_number=1123 atc_parking_types=GATE atc_parking_codes=SWA description="One should hardly …" Note: parameters labeled ui_ correspond to the User Interface only (i.e. to be used in the aircraft menu) while those labeled atc_ correspond to parameters to be used by the ATC and the AI traffic engine to properly identify and handle the aircraft. If the two parameters mentioned above have not been properly configured or are missing, which is the most common occurrence unless the user has manually modified the file, the AI traffic engine will not know the intended parking spot type and corresponding airline associated with the aircraft. On the other hand, If the aircraft is properly formatted as shown in the example above, the aircraft will be swiftly and efficiently directed toward a passenger terminal gate that has been configured for a B737-400 or smaller aircraft and that has been assigned to “Southwest Airlines”. Unless the option to disregard airline assignments is selected during installation, there are very few unassigned parking spots available for the AI traffic engine to use in our sceneries. Consequently, this option should be selected unless care has been taken either by the manufacturers or by you to properly format the aircraft.cfg file for the aircraft that you intend fly or use as AI traffic


Domestic Terminal

Gate

Maximum Aircraft

Wingspan (ft)

Typical Aircraft Formatted

for AI Aircraft

Parking Type Airline Codes

A1* 120 E75, E90, 319, 320, 321 N/A N/A ACA

A1B 200 E75, E90, 319, 320, 321,

763, 333 333 GATE ACA

A2* 120 E75, E90, 319, 320, 321 N/A N/A ACA

A2A 180 E75, E90, 319, 320, 321,

763 763 GATE ACA

A3 200 E75, E90, 319, 320, 321,

763, 333 333 GATE ACA

A4* 120 E75, E90, 319, 320, 321 N/A N/A ACA

A5 120 E75, E90, 319, 320, 321 320 GATE ACA

A6 180 E75, E90, 319, 320, 321,

763 763 GATE ACA

A7 120 DH4 N/A GATE POE

A8 80 DH4 N/A GATE CRQ

A9 120 DH4 N/A GATE POE

A10 80 DH4 N/A GATE CRQ

A11 120 E75, E90, 319, 320, 321 320 GATE ACA

A11B* 220 E75, E90, 319, 320, 321,

763, 333, 772, 773 N/A N/A ACA

A12 80 N/A GATE SPR

A13 N/A N/A N/A N/A N/A


A15 120 E75, E90, 319, 320, 321 320 GATE ACA


A17 80 732 N/A GATE FAB, SPR


A19* 200 N/A N/A GATE N/A

A19A 120 DH4 N/A GATE AIE

A19B 120 DH4 N/A GATE AIE


A21* 200 N/A N/A GATE N/A

A21A 120 DH1, DH2, DH4, CR1, CR2,

CRA N/A GATE ACA, JZA

A21B 120 DH1, DH2, DH4, CR1, CR2,




A23 80 DH1, DH2, DH4, CR1, CR2,



A25 80 DH1, DH2, DH4, CR1, CR2,



A27 80 DH1, DH2, DH4, CR1, CR2,


A28 80 DH1, DH2, DH4, CR1, CR2,



A30 80 DH1, DH2, DH4, CR1, CR2,



A32 80 DH1, DH2, DH4, CR1, CR2,



A34 80 DH1, DH2, DH4, CR1, CR2,


A47 120 736, 73G, 738 738 GATE WJA

A48 120 736, 73G, 738 738 GATE WJA

A49 120 736, 73G, 738 738 GATE WJA

A50 200 E75, E90, 319, 320, 321, 763, 313, 333, 772, 773

333 GATE ACA, TSC

A51 200 E75, E90, 319, 320, 321, 763, 313, 333, 772, 773

333 GATE ACA, TSC

A52 200 E75, E90, 319, 320, 321, 763, 313, 333, 772, 773

333 GATE ACA, TSC

Gates A17 - A34 are in the satellite terminal

* Gates blocked when the alternates are in use and not included in the AFCAD file


International Terminal

Gate

Maximum Aircraft

Wingspan (ft)


for AI Aircraft

Parking Type Airline Codes

B55 280 738, 343, 773, 744 GATE AFR, QTR, CJA, SWG

B56 120 738 738 GATE CJA, SWG

B56B* 200 313, 333 N/A N/A N/A

B57 200 763,313, 333, 343, M11 343 GATE AFR, KLM, RAM, TSC

B57A* 220 N/A N/A N/A N/A

B58 220 738, 313, 333 333 GATE CJA, SWG, TSC

B59 220 320, 738, 763 763 GATE BAW, CUB, SWG

B60 220 313, 333 333 GATE DLH, SWR, TSC

B61 220 738, 313, 333, 772, 773 773 GATE ACA, AMX, RJA, TSC

C72 120 CR1, CR2, CRA, E75, E90, 319, 320, 321, 736, 73G,

738 320 GATE ACA, JZA, WJA

C73 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 320 GATE ACA, JZA

C73A 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 320 GATE ACA, JZA

C74 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 320 GATE ACA, JZA

C75 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 320 GATE ACA, JZA

C76 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 320 GATE ACA, JZA

C77 80 DH4, CR1, CR2, CRA N/A GATE ACA, JZA, EGF

C77B* 120 DH4, CR1, CR2, CRA, E75,

E90, 319, 320, 321 N/A N/A ACA, JZA, EGF

C78 80 DH4, CR1, CR2, CRA, ER3 N/A GATE ACA, JZA, EGF

C79A* 120 ER3, 738 N/A N/A AAL, EGF

C79 80 ER3 N/A GATE AAL, EGF

C80 120 CR2, E70 E70 GATE AWE, AWI, RPA

C81 120 ER3, 738 738 GATE AAL, EGF

C82 120 CR2, E70 E70 GATE AWE, AWI, RPA

C83 120 CR1, CR2, CRA, E75, E90,

319, 320, 321, 738 738 GATE ACA, JZA, SWG

C84 120 ER4, CR7, E70, 736, 73G,

738 738 GATE

UAL, BTA, ASQ, GJS, TCF, WJA

C85 120 ER3, ER4, CR2 N/A GATE DAL, CPZ, FLG, CHQ

C86 120 ER4, CR7, E70, 736, 73G,

738 738 GATE

UAL, ASQ, BTA, GJS, TCF, WJA




C gates are the trans-border terminal for flights to the USA

* Gates blocked when the alternates are in use and not included in the AFCAD file


Remote Ramp

Parking Maximum

Aircraft Wingspan (ft)


for AI Parking

Type Airline Codes

E1 60 up to 321 N/A GATE N/A

E2, E3 200 Up to 773 N/A GATE N/A

W1 - W7 60 up to 321 N/A GATE N/A

Cargo Ramp (N PARKING)

Parking Maximum



for AI Parking

Type Airline Codes

N1, N2, N3 180 up to 763 N/A CARGO N/A

N1A, N1B, N2A, N2B, N3A, N3B

120 Up to 722 N/A N/A N/A

N4, N5 60 up to 722 N/A CARGO N/A

Remote Ramp

(PARKING)

Parking Maximum



for AI Parking

Type Airline Codes

1,3 220 up to 744 N/A RAMP N/A

2 120 up to A321 N/A RAMP N/A


Air Transat Maintenance

Ramp (PARKING)

Parking Maximum



for AI Parking

Type Airline Codes

4,5 200 313, 333 N/A RAMP TSC

Bombardier

Ramp (PARKING)

Parking Maximum



for AI Parking

Type Airline Codes

6 - 16 80 CRJ N/A RAMP N/A

Air Canada Maintenance

Ramp (PARKING)

Parking Maximum



for AI Parking

Type Airline Codes

17 -25 220 E75, E90, 319, 320, 321, 763, 333, 772, 773

N/A RAMP N/A

26 - 30 120 E75, E90, 319,

320, 321 N/A RAMP N/A

General Aviation

Ramps (NE PARKING)


Parking Maximum



for AI Parking

Type Airline Codes

1,2 120 up to 319, BBJ N/A RAMP N/A

3 - 19 60 N/A RAMP N/A

20 - 22 60 N/A RAMP N/A

23, 24 80 N/A RAMP N/A

30 - 32, 38, 39

60 N/A RAMP N/A

33 - 37 80 N/A RAMP N/A

40 - 45 80 N/A RAMP N/A

50 - 52 80 N/A RAMP N/A

60 80 N/A RAMP N/A

Airline Codes

AAL American Airlines EGF American Eagle

ACA Air Canada FAB First Air

AFR Air France FLG Pinnacle Airlines

AIE Air Inuit GJS GoJet Airlines

AMX Aeromexico KLM KLM

ASQ Atlantic Southeast Airlines POE Porter Airlines

AWE US Airways QTR Qatar

AWI Air Wisconsin RJA Royal Air Maroc

BAW British Airways RPA Republic Airlines

BTA ExpressJet Airlines SPR Provincial Airlines

CHQ Chautauqua Airlines SWG Sunwing Airlines

CJA Canjet SWR Swiss International

CPZ Compass Airlines TCF Shuttle America

CRQ Air Creebec TSC Air Transat

CUB Cubana UAL United Airlines

DAL Delta Airlines WJA WestJet Airlines


Aircraft Types

100 Fokker 100

AR1 Avro RJ100 Avroliner

141 British Aerospace BAe 146-100





AT4 Aerospatiale/Alenia ATR 42-300/320

312 Airbus A310-200

AT5 Aerospatiale/Alenia ATR 42-500

313 Airbus A310-300

AT7 Aerospatiale/Alenia ATR 72

318 Airbus A318

CR1 Canadair Regional Jet 100

319 Airbus A319


320 Airbus A320


321 Airbus A321


332 Airbus A330-200

CRA Canadair Regional Jet 705

333 Airbus A330-300

D93 Boeing/McDonnell Douglas DC-9-30

342 Airbus A340-200

D95 Boeing/McDonnell Douglas DC-9-50

343 Airbus A340-300

DH1 De Havilland Canada DHC-8-100 Dash 8/8Q

345 Airbus A340-500


346 Airbus A340-600


388 Airbus industry A380-800


717 Boeing 717-200

E70 Embraer ERJ-170

732 Boeing 737-200

E75 Embraer ERJ-175

733 Boeing 737-300

E90 Embraer ERJ-190

734 Boeing 737-400

E95 Embraer ERJ-195

735 Boeing 737-500

EM2 Embraer EMB-120 Brasilia

736 Boeing 737-600

ER3 Embraer ERJ-135 Regional Jet

738 Boeing 737-800

ER4 Embraer ERJ-145 Regional Jet

739 Boeing 737-900

ERD Embraer ERJ-140 Regional Jet

73G Boeing 737-700

M11 Boeing/McDonnell Douglas MD-11

744 Boeing 747-400


748 Boeing 747-800


752 Boeing 757-200


753 Boeing 757-300


762 Boeing 767-200


763 Boeing 767-300


764 Boeing 767-400


772 Boeing 777-200/200ER

773 Boeing 777-300

77L Boeing 777-200LR

77W Boeing 777-300ER


Scenery Fixes and Upgrades

We are committed to providing the highest quality scenery add-ons for Microsoft Flight Simulator. Consequently, we issue fixes and upgrades for our products from time to time. The fixes and upgrades may include simple corrections and improvements (most thanks to the feedback of our customers) as well as significant changes and improvements resulting from technique evolution and refinement on the part of our designers. As our technique evolves, we update previously released products by issuing interim fixes or upgrades. In order to stay current regarding these free fixes and upgrades please visit the “Downloads” page on our web site: http://www.blueprintsimulations.com/

Technical Support Answers to the most common questions about our sceneries can be found in the FAQ section of our website at http://www.blueprintsimulations.com. Any other technical questions must be submitted via email to [email protected].

Acknowledgements

We would like to acknowledge Lee Swordy for his AFCAD version 2.21 freeware, a CAD-style program used for the modification of facility data as well as some of the visible scenery used in Microsoft Flight Simulator. We would also like to acknowledge Arno Gerretsen and the entire www.FsDeveloper.com team for their effort to provide guidance and advice to all MSFS add-on developers.



http://www.fsdeveloper.com/

Documents

Presents - BluePrint Simulations · Parking spot configuration and airline gate assignments Technical support and contact information Scenery fixes and upgrades Acknowledgements Scenery