The corrected 'aircraft.cfg' Collection Thread

#1
I want to open this sticky thread to gather the corrected aircraft.cfg exit positions for the most commonly used add-on aircraft.

Introduction
Jetway misalignment has always to do with incorrect exit position in the aircraft.cfg. SODE uses this exit position for the calculation. SODE's AircraftParameters.ini however is only used for the hood extension, so that the hood nicely follows the fuselage contours.

Again, SODE relies on a proper aircraft.cfg exit position. This is the same source the default CTRL+J jetways (and all other IK-jetways like FlyTampa's etc) use. The difference is that SODE is more precise and a small shift is noticeable visually, whereas the IK-based jetways are pretty coarse.

I have inspected some of the aircraft.cfg available and they are mostly off. While it is not officially documented in the SDK, the exit position should be located in the middle of the door frame. Former ACES developer Adrian Woods mentioned this in his Jetway SDK tutorial video, and if you inspect the default aircraft, their main exit position is always in the middle of the door frame.

Thanks to the ModelConverterX Tool from Arno, you can now visually inspect the exit position of the aircraft.cfg. In the latest development version, you are even able to edit those points and move them to the correct location, which is the middle of the door.

This way, SODE jetways as well as all other IK-based jetways will work as intended.

I will collect all data in the next post. Thanks for your help!
 
#2
The Collection

Aerosoft Airbus

[EXITS]
number_of_exits = 4
exit.0 = 0.4, 28.5, -6.5, 0.0, 0
exit.1 = 0.4, 28.5, 6.5, 0.0, 0
exit.2 = 0.4, 23.0, 5.5, -6.0, 1
exit.3 = 0.4, -60.0 , 5.5, -6.0, 1
[EXITS]
number_of_exits = 4
exit.0 = 0.4, 30.0, -6.5, 0.0, 0
exit.1 = 0.4, 30.0, 6.5, 0.0, 0
exit.2 = 0.4, 23.0, 5.5, -6.0, 1
exit.3 = 0.4, -60.0 , 5.5, -6.0, 1
[Exits] // A320
number_of_exits = 4
exit.0 = 0.4, 35.5, -6.5, 0.0, 0
exit.1 = 0.4, 35.5, 6.5, 0.0, 0
exit.2 = 0.4, 23.0, 5.5, -6.0, 1
exit.3 = 0.4, -60.0 , 5.5, -6.0, 1
[EXITS] //A321
number_of_exits = 4
exit.0 = 0.4, 45.15, -6.5, 0.0, 0
exit.1 = 0.4, 45.15, 6.5, 0.0, 0
exit.2 = 0.4, 38.0, 5.5, -6.0, 1
exit.3 = 0.4, -60.0 , 5.5, -6.0, 1


PMDG B777

[exits]
number_of_exits = 5
exit.0 = 0.4, 65.5, -9.607, 6.4, 0 ;Door 1L
exit.1 = 0.4, 32.8, -10.2, 6.4, 0 ;Door 2L
exit.2 = 0.4, 49.639, 10.121, -3.736, 1 ;Fwd Cargo
exit.3 = 0.4, -46.387, 10.121, -3.736, 1 ;Aft Cargo
exit.4 = 0.4, -61.272, 5.341, 2.906, 1 ;Bulk Cargo
[exits]
number_of_exits = 5
exit.0 = 0.4, 65.862, -8.900, 6.4, 0 //Door 1L
exit.1 = 0.4, 49.639, 10.121, -3.736, 1 //Fwd Cargo
exit.2 = 0.4, -46.387, 10.121, -3.736, 1 //Aft Cargo
exit.3 = 0.4, -61.272, 5.341, 2.906, 1 //Bulk Cargo
exit.4 = 0.4, -45.479, -10.029, 3.300, 1 //Main Cargo
[exits]
number_of_exits = 5
exit.0 = 0.4, 82.179, -9.607, 6.4, 0 //Door 1L
exit.1 = 0.4, 49.179, -10.2, 6.4, 0 //Door 2L
exit.2 = 0.4, 65.954, 10.121, -3.736, 1 //Fwd Cargo
exit.3 = 0.4, -62.184, 10.121, -3.736, 1 //Aft Cargo
exit.4 = 0.4, -77.069, 5.341, 2.906, 1 //Bulk Cargo


QualityWings B757

[exits]
number_of_exits = 2
exit.0 = 0.2, 31.25, -6.25, 7, 0
exit.1 = 0.2, -28.5, 5.5, -0.8, 1
[exits]
number_of_exits = 2
exit.0 = 0.2, 44.50, -6.25, 7, 0
exit.1 = 0.2, -38.0, 5.5, -0.8, 1
 
#3
Very interesting thread discussing somewhat unusual, rarely touched aspects of our hobby. Please keep up!


Sent from my Galaxy S4 using Tapatalk
 
#4
Do you think it would be a better idea to include coordinates for SODE to override the aircraft.cfg so we don't have to ask users to edit the aircraft.cfg
 
#5
Do you think it would be a better idea to include coordinates for SODE to override the aircraft.cfg so we don't have to ask users to edit the aircraft.cfg
I also thought about that. The thing is, that I'd have to reliably detect every possible aircraft add-on and have config files for every one of them. I want to avoid using another set of config data. That would be difficult to maintain as well, because I do not own them all, and from my experience, the help from the community is pretty non-existing sadly. IMHO, it is easier that the end-user just corrects a couple of lines for their aircraft at hand.

The most reliable source for exit positions is the aircraft.cfg, because it has a direct relation with the underlying 3D model. And if properly set up by the add-on maker, there would be no problem at all. Unfortunately, a lot of exit coordinates are just plain wrong when you visualize them, some are not even near the door painted on the fuselage texture. It is surely not my job to provide proper coordinates, it should be a quality feature of the add-on plane...

However, GSX, which comes with own config data, will be able to use them when interacting with SODE and thus override the aircraft.cfg. So for GSX users, the work is already done.

I hope you can follow my reasoning.
 
#6
I am having some trouble figure out how to get the coordinates for addon aircraft, and the Readme hasn't really helped me. Is there any way to get coordinates for certain aircraft?
 
#7
Hi Will,

As described in the top post, you may use Arno's ModelConverterX tool to visualize the exit points of any of your installed aircraft. In the tool, open the corresponding aircraft.cfg and edit/move them to the center of the door.
Don't forget to post back here so everyone can make use of the corrected data :)
 
#8
I couldn't figure out how to get it to say the spoiled thing, but here is the quality wings 757 coordinates!


QW 757-200:

[exits]
number_of_exits = 2
exit.0 = 0.2, 31.25, -6.25, 7, 0
exit.1 = 0.2, -28.5, 5.5, -0.8, 1

QW 757-300:

[exits]
number_of_exits = 2
exit.0 = 0.2, 44.50, -6.25, 7, 0
exit.1 = 0.2, -38.0, 5.5, -0.8, 1
 
#9
Do you think it would be a better idea to include coordinates for SODE to override the aircraft.cfg so we don't have to ask users to edit the aircraft.cfg
Update: Just implemented your suggestion for V1.3.1. If SODE has custom positions, they'll be used. You were right, it is much easier for everybody in the end.
 
#11
Default B747
Enables 1L and 2L for double-jetway docking.

[exits]
number_of_exits = 3
exit.0 = 0.4, -31.1147, -9.5702, 1.11891, 0 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)
exit.1 = 0.4, -62.2539, -9.6109, 1.1891, 0 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)
exit.2 = 0.4, -43.8000, 7.1000, -8.400, 1 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)
 
#13
I realised that the SODE jetway did not connect correctly to the FSLabs A320 anymore, so I made these changes to the AircraftParameters.ini and it works nicely now:

[A320]
1L = 1.0, -0.4, 4.0, 2.19, 2.3

Feedback welcome.
 

jtanabodee

Resource contributor
#15
Hi Jeffry,
I have two questions
1. I was wondering if we need the AircraftParameters.ini for every aircraft we have in FSX or we just need it when we have seen some miss alignment of the jetway to the door of the aircraft. I guess SODE looks for this information in the aircraft.cfg in the program. But once we want to edit it for SODE jetway, we need to correct them here. Am I correct?
2. You said that we can use ModelConverterX to visually inspect the exit position of the aircraft.cfg. I went through MCX manual and I cannot find how to do it. Would you mind clarifying this?
Thanks
 
#16
1. AircraftParameters.ini contains the detailed information for SODE so that the jetway hood nicely fits the aircraft model. The actual door position itself is looked up in the AircraftExits.ini. It is SODE's internal database of exit positions. If SODE doesn't find it there, it will get the exit position from the aircraft.cfg. I can tell you that most of those aircraft.cfg is not accurate regarding to the exit positions, so that's why I collect the corrected ones in the AircraftExits.ini.
However, SODE allows GSX to provide their database of accurate exit positions to be used, so GSX users benefit from that.

2. I think it is only available in the development version of MCX -> https://www.scenerydesign.org/development-releases/ There will be a button (aircraft symbol) "Show CFG Points". Load an aircraft.cfg and MCX will load the corresponding MDL. Enabling that "Show CFG Points" button will show all those CFG points (exits, contact points, engine etc etc). MCX will also have an integration aircraft.cfg Editor whichs allows you to edit the aircraft.cfg and get visual feedback directly on the 3D view.
 
#17
The actual door position itself is looked up in the AircraftExits.ini. It is SODE's internal database of exit positions. If SODE doesn't find it there, it will get the exit position from the aircraft.cfg. I can tell you that most of those aircraft.cfg is not accurate regarding to the exit positions, so that's why I collect the corrected ones in the AircraftExits.ini. However, SODE allows GSX to provide their database of accurate exit positions to be used, so GSX users benefit from that.
Question, Can you explain how the AircraftExits.ini knows when it should be used?

A little backstory, and perhaps this isn't possible, I am playing around with the QW787 and I would like the aircraft.cfg file to only have the 2L exit so that when I am forced to use the IK jetways, they connect there. I would still like to be able to use both 2L and 1L with SODE where available. My thought was that the aircraft.cfg file would hold the details for the IK jetways and I could use the exit file to hold the updated 1L and 2L information for SODE. However, any changes I make to the AircraftExits.ini file don't seem to be recognized by SODE when I get into FSX.
 
#18
Your idea should work. Indeed, SODE reverts to the aircraft.cfg if it can't find an entry in the AircraftExits.ini.

Now, how does it look it up in that ini? The section title in square brackets is a combination of two strings from the aircraft.cfg, namely from the [fltsim.0] section:
  • ui_createdby=AABBCC
  • sim=XXYYZZ
In the AircraftExits.ini, you need to create the title like this -> [AABBCC:XXYYZZ], note the colon ":" between the two strings!
The data entries "exit.N" themselves are structurally identical to the ones in the aircraft.cfg.

Probably, the section title was not properly defined in your case and that's why SODE wasn't able to look it up.

If you have a working set of data for the QW787, please post them here. I will gladly include them in the installer for the next version :)
 
#19
If you have a working set of data for the QW787, please post them here. I will gladly include them in the installer for the next version :)
Thank you for the explanation. I think it was the [fltsim.0] section that didn't have the ui_createdby field that was throwing it off. It could have been a typo somewhere else too, but it is working now!

I tested both SODE and Non-SODE with these values and they seem to work quite well.

AircraftParameters.ini:
[B788]
1L = 2.0, -0.2, 10.0, 2.2, 2.5
2L = 2.0, -0.2, 0.0, 3.0, 3.0

[B789]
1L = 2.0, -0.2, 10.0, 2.5, 2.8
2L = 2.0, -0.2, 0.0, 3.0, 3.0

AircraftExits.ini:
[QualityWings Simulations:Boeing 787-8 RR]
exit.0 = 0.2, 67.00, -8.0, 5.0, 0;Door 1L //787-8
exit.1 = 0.2, 38.00, -9.0, 5.0, 0;Door 2L //787-8

[QualityWings Simulations:Boeing 787-8 GE]
exit.0 = 0.2, 67.00, -8.0, 5.0, 0;Door 1L //787-8
exit.1 = 0.2, 38.00, -9.0, 5.0, 0;Door 2L //787-8

[QualityWings Simulations:Boeing 787-9 RR]
exit.0 = 0.2, 76.00, -8.1, 5.0, 0;Door 1L //787-9
exit.1 = 0.2, 38.00, -9.0, 5.0, 0;Door 2L //787-9

[QualityWings Simulations:Boeing 787-9 GE]
exit.0 = 0.2, 76.00, -8.1, 5.0, 0;Door 1L //787-9
exit.1 = 0.2, 38.00, -9.0, 5.0, 0;Door 2L //787-9

And for those of you reading, you will also need to update the aircraft.cfg file for both the 787-8 and 787-9. Use which ever exit you want IK jetways going to in the exits section. Add ui_createdby=QualityWings Simulations to the flightsim.0 section.

And now I am off to fly from YSSY (non-SODE, come on flyTampa, get with the times) to KIAH (SODE).
 

jtanabodee

Resource contributor
#20
I have downloaded Project Airbus A380 from https://library.avsim.net/search.php?SearchTerm=a380&CatID=fsxac&Sort=Name&ScanMode=0&Page=2
I looked through the aircraft.cfg:
........
[fltsim.0]
title = Airbus A380-841 Singapore Airlines (wingview)
sim = pa380
model =
panel =
sound =
texture =
kb_checklists =
kb_reference =
atc_id = 9V-SKC
atc_airline = Singapore
atc_flight_number = 319
ui_manufacturer = Project Airbus
ui_type = A380-841
ui_variation = Singapore Airlines
ui_typerole = "Commercial Airliner"
ui_createdby = "Project Airbus"
....................
That means I need to put [Project Airbus;pa380] in the AircraftExits.ini. right?
I put the information of the exits in but there is still a warning that SODE does not have aircraft exit information. What could be wrong? But SODE still looks up though the aircraft.cfg and it found the right position of the doors.
 
Top