When boarding it keeps saying "open exit 2". i have all doors and cargo open??

You have to go into the GSX menu and change the settings for the 777 aircraft.  I shut down door one as door 2 is the main door.  Make sure in the PMDG menu that it shows door 2 Close.  If it shows open that means the door is closed.

 

Best regards,

Jim

or just close it and and open it. When starting a session with doors open GSX does not always get the state of the opened door right as it has not seen the opening of the door.

 

Dick

I don't know if thsi is related to the OP's question:  When I try and use GSX with the PMDG B777 (loaded at a gate), I always get the error message that GSX cannot run since the gate is too small for my aircraft. 

 

Thanks,  Bruce.

 

 

 

I always get the error message that GSX cannot run since the gate is too small for my aircraft.

 

I saw this a lot too and you just have to make sure you find a space for heavy's.  It's a huge aircraft.  I found that the gates around gate 111 at KLAX are the only ones that work so far with GSX.  You have huge loaders loading and unloading.

 

Best regards,

Jim

Thanks Jim. Is the gate size something I can change with an airport editor? And would that let GSX work at a gate that I had modified? Like you say, those "heavy" gates are rare and sometimes nowhere near the terminal that I want to leave from.

 

Hoping that this isn't derailing the OP's thread too much,,,,

 

Thanks, Bruce.

Sorry I can't help you there Bruce in regards to an Airport Editor.  You're just going to have to do a lot of testing at your favorite takeoff/landing airports and find the gates that work.  It took me awhile before I found the right gates at KLAX as even the Gates listed as Heavy were too small. 

 

Hopefully the OP's questions have been answered.

 

Best regards,

Jim

There is an easy way Bruce.  Start FSX, select the PMDG 777 and select a gate that does not work. Go to coauti menu in fsx. Select "Customise airport position.

In the box that appears you will see Max allowed wingspan, click the little button with a pic of an aircraft on it. Presto, your gate is now big enough. Press apply. You can do that with any gate at any airport.

Awesome, thanks Julian. Hopefully Jim will see this too.

 

Thanks mate, Bruce.

It's great to know some people read the manual!  :lol:    Thanks Julian!

 

Best regards,

 

Jim

It works! Thanks Julian!

 

Now to find a solution to GSX not working at KSFO (FlightBeam).....

 

Bruce.

 

 

Now to find a solution to GSX not working at KSFO (FlightBeam).....

 

Think you have to buy AES to get the gates to move.  But otherwise GSX works fine for me at FlightBeam's KSFO.

 

Best regards,

Jim

or just close it and and open it. When starting a session with doors open GSX does not always get the state of the opened door right as it has not seen the opening of the door.

That's not the issue.

 

The OP said that GSX is listing the door as "Exit 2", which is the generic name used when there's no configuration for an airplane OR if he downloaded and/or created himself a configuration for the 777 BEFORE we added official support for it, which happened 2-3 days after the 777 was released, but some people were so eager to use it, that they downloaded and/or created files themselves, which might not work well, especially if the user doesn't know how to create an XML expression, which is required for complex 3rd party airplanes that use only custom variables for doors.

 

The "Exit 2" name should be a tell-tale about the fact that GSX is not using its own configuration, because we always supply doors with their proper names as provided by the airplane developer, like "Exit 2 L", which I think is the name PMDG uses to refer to that door.

 

A custom/user created customization always takes precedence over the one that comes with GSX, on the premise the user should be allowed to build and improve upon the configuration that comes with GSX, but in this case if the user config was based on a config which was made BEFORE GSX already had official support for the 777, it's still missing the correct variables, unless of course the user is able to figure them out already and write an XML expression for them.

 

Of course, there's no need to do that, now that GSX fully support the 777, but it's necessary to get rid of that custom configuration, which can be done in the following way:

 

- Being sure GSX is fully updated with the latest Live Update. If not sure, best to reinstall it, so the installer will download all the current updates online.

 

- Entering in the GSX Airplane configuration editor with the PMDG 777 loaded and selecting the "RESET" button, which will revert to the default config that comes with GSX.

 

- Use the "Restart Couatl" option to make the new config active without having to restart FSX.

 

And, it's not that GSX can't always detect the door's status, because it does. It's the PMDG that sometimes doesn't update its custom variables status with the doors status, especially when using the Save/Load State functions on the FMC.

That's not the issue.

 

The OP said that GSX is listing the door as "Exit 2", which is the generic name used when there's no configuration for an airplane OR if he downloaded and/or created himself a configuration for the 777 BEFORE we added official support for it, which happened 2-3 days after the 777 was released, but some people were so eager to use it, that they downloaded and/or created files themselves, which might not work well, especially if the user doesn't know how to create an XML expression, which is required for complex 3rd party airplanes that use only custom variables for doors.

 

The "Exit 2" name should be a tell-tale about the fact that GSX is not using its own configuration, because we always supply doors with their proper names as provided by the airplane developer, like "Exit 2 L", which I think is the name PMDG uses to refer to that door.

 

A custom/user created customization always takes precedence over the one that comes with GSX, on the premise the user should be allowed to build and improve upon the configuration that comes with GSX, but in this case if the user config was based on a config which was made BEFORE GSX already had official support for the 777, it's still missing the correct variables, unless of course the user is able to figure them out already and write an XML expression for them.

 

Of course, there's no need to do that, now that GSX fully support the 777, but it's necessary to get rid of that custom configuration, which can be done in the following way:

 

- Being sure GSX is fully updated with the latest Live Update. If not sure, best to reinstall it, so the installer will download all the current updates online.

 

- Entering in the GSX Airplane configuration editor with the PMDG 777 loaded and selecting the "RESET" button, which will revert to the default config that comes with GSX.

 

- Use the "Restart Couatl" option to make the new config active without having to restart FSX.

 

And, it's not that GSX can't always detect the door's status, because it does. It's the PMDG that sometimes doesn't update its custom variables status with the doors status, especially when using the Save/Load State functions on the FMC.

 

Does GSX help with moving all jetways at different airports or is that a different add-on?

Does GSX help with moving all jetways at different airports or is that a different add-on?

GSX doesn't handle jetways in any way. If they move ( or not ), it's entirely unrelated with GSX.

 

All FSX default sceneries, all FSDT sceneries and recent sceneries from Flightbeam, UK2000, all support proper FSX animated jetways so, they will work regardless if GSX is installed or not.

 

If a 3rd party scenery has static jetways, installing GSX won't change this (but of course the airport will be entirely serviced by GSX vehicles), and if it uses a non standard way of animated them, it will continue working that way and, again, GSX won't change this.