Exit 1L Data

[garrett_frank 150]

Just to pick back up on this... James' coordinates for 1L work great using the 77L and the new LIRF from Aerosoft/MK-Studios. However, SODE only detects a 1L Upper which doesn't make any sense... and to which it won't dock to because it says it's too high. There are no other entries in my aicraftparameters.ini and everything is as it should be in the 77L exits section.

 

 

edit: Just found out why. Some liveries loaded from PMDG Ops Center include a CFG entry for "atc_model" and use "777-200LR" or something and not the "77L" listed under the [general] tab. If any of that makes any sense...

[xkoote 57]

Well let's see,

 

1. Opened -300ER in Rome. Door out of range for Door 1L

 

2. Added: [b77W]

                2L = 3.75, 0.0, 0.0, 3.9, 4.0

 

3. Modified aircraft.cfg and changed atc_model to B77W (To match ini file)

 

4. SODE still says the aircraft has Door 1L and it is still out of range.

 

5. Modified ini file to add B77L Data from this post and edited House -200LR ATC Model to B77L

 

6. Still unable to dock

 

7. Edited CFG file from B77L to 77L. No change. Changed BOEING to B and back. No change.

 

8. The -300ER stays at door 1L even though I set only Door 2L in the ini file and the -200LR

    tells me to connect to Door 1L or 1L Upper (Which is the default B744 entry).

 

I don't know what else to try to make SODE at least match my actual airplane to the INI settings.

I am using P3D v3.1 and Aerosoft's Rome.

 

Cheers,

 

Xander

[xkoote 57]

LS,

 

I have since solved the problem after half a day of poking around. I had a hard time searching for a definitive answer of what was wrong

and the documentation for SODE was vague until I opened the SDK pdf file. In short, the problem was that the exit parameters for the 

PMDG 777-300ER (Haven't started on the -200LR yet) were wrong. Especially the door (exit) height. 

 

The default values of my -300ER

 

[exits]

number_of_exits = 4

exit.0 = 0.4, 50.179, -9.607, 12.298, 0 //Door 2L 

exit.1 = 0.4, 65.954,  10.121, -3.736, 1   //Fwd Cargo

exit.2 = 0.4,  -62.184,  10.121, -3.736, 1   //Aft Cargo

exit.3 = 0.4, -77.069, 5.341, 2.906, 1     //Bulk Cargo

 

1. The value 12.298 was too high and I constantly got an error that the door was out of reach. Going in the xml files of SODE for

Rome showed indeed that the vertical limit was 11 point something. So I lowered it to 6 (random lower value) and the gate 

started reacting. After some fine tuning I managed to get the gate to dock nicely to door 2L.

 

2. I then set out to make door 1L available as a second door and managed to find the values for those too. I could now connect both

jetways to the -300ER.

 

3. The B77W that should be added in the AircraftParameters.ini should match the atc_model value under the [General] section of 

the aircraft.cfg file. I was changing the atc_model value of the individual aircraft. This doesn't need changing. These were the values 

I used in the INI file.

 

[b77W]

1L = 2.0, 0.0, 0.0, 3.8, 3.8

1L Upper = 2.0, 0.0, 10.0, 3.4, 3.7

 

I will now explain the only limitation I found, and someone please add in if they know the solution. As you can see from the exits, I placed

door 2L as the main exit (exit.0). Why? Because I want the CTRL+J to work as I want to (Connect to the 2L door) when not using SODE.

So exit.0 is 2L and exit.1 is 1L. Now it seems that SODE keeps a natural progression of doors. 1L, then 1L Upper, then 2L. So it sees my 

exit.0 as door 1L (while it actually door 2L) and exit.1 as door 1L Upper (while it is actually door 1L). That is why I have to name the doors

accordingly in the INI file. And I also have to keep that in mind when connecting the jetways.

 

4. My new and updated exit section for the -300ER is:

 

[exits]

number_of_exits = 5

exit.0 = 0.4, 50.179, -10.607, 5.5, 0 //Door 2L

exit.1 = 0.4, 82.179, -8.107, 5.3, 0 //Door 1L 

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

 

I hope this can be of use to someone. The reason I posted is because of the frustration I had and the lack of guidance to make the setup 

work. Again, if someone knows how to let SODE know what is main exit 2L and what is secondary exit 1L please share.

 

 

Regards,

 

 

[LRW 42]

[update to what I wrote below.   I tested this at gate F7 at KATL.  I went back in a tried gate A6 and got the "door too high" warning.  I'll have to do more testing to see if that's because of different configs (or models) for different gates.]

 

With Imagine Sim's KATL now supporting SODE, I found this thread once I realized that the 777 didn't work with SODE as-is.   Using some of the examples and tips from this thread, I played around with the parameters and ended up with this for the 200LR and the 300ER

 

%appdata%\12bPilot\SODE\AircraftParameters.ini

 

[b77L]

1L = 2.0, 0.0, 10.0, 3.4, 3.7

2L = 2.0, 0.0, 0.0, 3.8, 3.8

 

[b77W]

1L = 2.0, 0.0, 10.0, 3.4, 3.7

2L = 2.0, 0.0, 0.0, 3.8, 3.8

 

 

<P3D>\SimObjects\Airplanes\PMDG777-200LR\aircraft.cfg

[exits]

number_of_exits = 5

exit.0 = 0.4, 35.0, -9.8, 6.1, 0     //Door 2L

exit.1 = 0.4, 67.0, -8.9, 6.1, 0     //Door 1L

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

 

 

<P3D>\SimObjects\Airplanes\PMDG777-300ER\aircraft.cfg

[exits]

number_of_exits = 5

exit.0 = 0.4, 51.0, -9.8, 6.1, 0     //Door 2L

exit.1 = 0.4, 84.0, -8.7, 6.1, 0     //Door 1L

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

 

SODE prompts for L1 or L2 when connecting, the jetway and hood line up nicely, and Ctrl-J still connects to L2 at non-SODE airports (as Xander showed).

Edited January 24, 2016 by LRW

[xkoote 57]

What I noticed is that SODE is still in its infancy. I have 3 airport that use SODE.

 

- Drzewieki Design Moscow: Uses its own key combo, parks the jetways at default positions

 

- Aerosoft Rome: Depends on aircraft.cfg data in a different way than,

 

- ImagineSim Atlanta which for one uses the v 1.3 setup.

 

ImagineSim sees the doors as entered in the ini file without problems. Door 1L and 2L. With LIRF this isn't the case. But now that I have only SODE 1.3 installed, the old UUEE works as before. But LIrF stopped working. Due to its infance this still requires a lot of patience

 

Xander

[jordanal 70]

[update to what I wrote below.   I tested this at gate F7 at KATL.  I went back in a tried gate A6 and got the "door too high" warning.  I'll have to do more testing to see if that's because of different configs (or models) for different gates.]

 

With Imagine Sim's KATL now supporting SODE, I found this thread once I realized that the 777 didn't work with SODE as-is.   Using some of the examples and tips from this thread, I played around with the parameters and ended up with this for the 200LR and the 300ER

 

%appdata%\12bPilot\SODE\AircraftParameters.ini

 

[b77L]

1L = 2.0, 0.0, 10.0, 3.4, 3.7

2L = 2.0, 0.0, 0.0, 3.8, 3.8

 

[b77W]

1L = 2.0, 0.0, 10.0, 3.4, 3.7

2L = 2.0, 0.0, 0.0, 3.8, 3.8

 

 

<P3D>\SimObjects\Airplanes\PMDG777-200LR\aircraft.cfg

[exits]

 

number_of_exits = 5

exit.0 = 0.4, 35.0, -9.8, 6.1, 0     //Door 2L

exit.1 = 0.4, 67.0, -8.9, 6.1, 0     //Door 1L

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

 

 

 

<P3D>\SimObjects\Airplanes\PMDG777-300ER\aircraft.cfg

[exits]

 

 

number_of_exits = 5

exit.0 = 0.4, 51.0, -9.8, 6.1, 0     //Door 2L

exit.1 = 0.4, 84.0, -8.7, 6.1, 0     //Door 1L

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

 

 

 

SODE prompts for L1 or L2 when connecting, the jetway and hood line up nicely, and Ctrl-J still connects to L2 at non-SODE airport

s (as Xander showed).

 

PERFECT! Many thanks, Larry! Now I have the PMDG-77x working on P3Dv3.1 with IS KATL 2016 with SODE 1.3. 

[wde12 19]

 

 

I went back in a tried gate A6 and got the "door too high" warning.  I'll have to do more testing to see if that's because of different configs (or models) for different gates.]

 

Hoping for a little bump here and a notice to LRW. Did you ever have any progress since your post? Since updating GSX, the SODE jetway disappear issue has since been resolved. I tweaked the aircraft parameters stuff as described and had some success at KATL. Basically, the jetway docks with my 777 at some gates - at others the door is still too high for some reason. 

 

Is there a definitive set of values for the PMDG 777? The one on the SODE author's site (12bpilot) doesn't work (at least with the PMDG 777 and Imaginesim KATL). Your post and values were much appreciated ....but like you, I am not all the way there.

 

Thoughts?

[medic89 6]

Basically, the jetway docks with my 777 at some gates - at others the door is still too high for some reason.

 

I got the same issue with the PMDG 777 in KATL. I guess(!) this problem could refer to the different types of jetways at KATL. If you open the xml file for KATL there are four or five different types of jetways.+

 

Phil Tereny

[wde12 19]

 

 

I got the same issue with the PMDG 777 in KATL. I guess(!) this problem could refer to the different types of jetways at KATL. If you open the xml file for KATL there are four or five different types of jetways.+

 

That makes sense. I am not familiar with xml files. Where are they typically located? Can you change the 4-5 different types of jetways into just one? And if so, would that be a problem?

[pcubine 143]

 

 

I am not familiar with xml files. Where are they typically located?

For Imagine Simulation KATL 2016 here is one - c:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Imagine Simulation\KATL Atlanta 2016 FSX\config\AirportConfig.xml.

[medic89 6]

Can you change the 4-5 different types of jetways into just one? And if so, would that be a problem?

 

I'm not sure if that is the only factor which averts the jetway from docking to the 777. Yesterday I tried SODE at Positions F1 to F9 and F6 on the other side of the f concourse in Atlanta, and F9 was the only one where the jetway could dock on 1L and 2L on the -200LR as well as on the 300ER. I think the best solution would be, if we contact Imaginesim and raise a ticket.

[wde12 19]

 

 

I'm not sure if that is the only factor which averts the jetway from docking to the 777. Yesterday I tried SODE at Positions F1 to F9 and F6 on the other side of the f concourse in Atlanta, and F9 was the only one where the jetway could dock on 1L and 2L on the -200LR as well as on the 300ER. I think the best solution would be, if we contact Imaginesim and raise a ticket.

 

I posted to their FB page (on the SODE announcement thread). https://www.facebook.com/Imaginesim-795499297198912/

 

Hopefully we will hear something soon. In the meantime, any progress?

[pilot3033 5]

I'm not sure there's something unique to the jetway model at F9 so much as it's just the placement seems to work. I think the ATL jetways just don't go high enough, but for whatever reason the angle of that parking spot allows SODE to come up with a solution. 

 

The answer, I think, is tweaking the jetway models to allow them to go further and higher, but that's something Imaginesim has to do. Has anyone had success at other parking spots?

[wde12 19]

I'm not sure there's something unique to the jetway model at F9 so much as it's just the placement seems to work. I think the ATL jetways just don't go high enough, but for whatever reason the angle of that parking spot allows SODE to come up with a solution. 

 

The answer, I think, is tweaking the jetway models to allow them to go further and higher, but that's something Imaginesim has to do. Has anyone had success at other parking spots?

 

Have fun. I contacted ImagineSim here: https://www.facebook.com/795499297198912/photos/a.795502433865265.1073741828.795499297198912/1063783100370529/?type=3&theater

 

As you can see, they got super defensive and ###### off. "No way it's their problem" They have caught a ton of heat over the years for their products. I get why, they aren't on Flightbeam / Taxi2Gate / FlyTampa level. But I still don't like the criticism because we need as many developers as we can get in this community. I don't want to prove them wrong here. I want to be constructive (if the problem is indeed ImagineSim). Regardless, I want to exhaust all possibilities that it is indeed someone else who can fix it (like SODE) before I go back. 

 

I posted the issue on 12bpilot's forum here FWIW: http://sode.12bpilot.ch/?topic=pmdg-777-door-too-high-imaginesim-katl

 

If you or anyone else can contribute more info for 12bpilot, please do so.

[pilot3033 5]

Have fun. I contacted ImagineSim here: https://www.facebook.com/795499297198912/photos/a.795502433865265.1073741828.795499297198912/1063783100370529/?type=3&theater

 

As you can see, they got super defensive and ######. "No way it's their problem" They have caught a ton of heat over the years for their products. I get why, they aren't on Flightbeam / Taxi2Gate / FlyTampa level. But I still don't like the criticism because we need as many developers as we can get in this community. I don't want to prove them wrong here. I want to be constructive (if the problem is indeed ImagineSim). Regardless, I want to exhaust all possibilities that it is indeed someone else who can fix it (like SODE) before I go back. 

 

I posted the issue on 12bpilot's forum here FWIW: http://sode.12bpilot.ch/?topic=pmdg-777-door-too-high-imaginesim-katl

 

If you or anyone else can contribute more info for 12bpilot, please do so.

 

 

I remember have some success in the past actually editing the jetway parameters, but I was not entirely sure what I was doing, so though every jetway would connect to a 777, the textures would stretch awkwardly or the wheels would straight up leave the ground. There is a way, following the SODE SDK, to edit it how it does the math. I will try playing around a little more. Otherwise I guess all of my Delta flights now leave out of Concourse F