FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: frgamer on March 04, 2017, 03:47:53 pm
-
Hi I was trying to do a flight in the PMDG 747 v3 and when I requested boarding it said to open exit 1 and 2 which I did, but it still kept saying to open exit 2, anyone know why?
I saw somethibg about choosing to ignore the door status or sometjing like that but idk how to.
-
Hi I was trying to do a flight in the PMDG 747 v3 and when I requested boarding it said to open exit 1 and 2 which I did, but it still kept saying to open exit 2, anyone know why?
That's because you either downloaded or made a custom configuration for it, before the airplane was supported by GSX. Now the airplane IS supported (assuming you HAVE applied the latest Live Update), but your custom configuration is still taking precedence on the one that comes with GSX, so you still see the default door names.
Use the "Reset" button in the airplane customization page to restore the airplane configuration to the one that comes with GSX.
-
I had the same issue, with FSX I just used SHIFT-E-2, and the message went away, and ground activities continued. This was with a freeware 747 I downloaded.
-
I had the same issue, with FSX I just used SHIFT-E-2, and the message went away, and ground activities continued. This was with a freeware 747 I downloaded.
Why you think this is an "issue" ? That's exactly how GSX works: would you find realistic that GSX would try to load cargo or catering with the doors still closed ?
If you use a freeware 747, it's normal the cargo door would be called "Exit 2", because that's the default name for it and, usually, freeware airplanes work like a default airplane, so the default assignment should work.
The first post was about the PMDG 747, instead, which is an internally supported airplane (in the latest GSX update), so the door shouldn't be called "Exit 2", UNLESS the user configured it already before it was supported, so it took the default name, which means the configuration must be reset, since user customizations always takes precedence over the internal ones.
-
Yes... it is an issue.
I am using the PMDG 747-800 (V3) and I have reset the settings to default. I also reloaded the airport cache and tried to board passengers.
It still asks me to open exit 2.
So I opened ALL the doors on the 748i...
It still asks me to open exit 2.
-
Open the FMC FS Actions-doors. If OPEN, close it and open again, wait and all goes fine.
-
Open the FMC FS Actions-doors. If OPEN, close it and open again, wait and all goes fine.
No... it still get that Open Exit 2 "prompt.
-
No... it still get that Open Exit 2 "prompt.
This means the airplane is not configured yet. Do you realize this is a thread from 2017 ? The 747 discussed here was the 747-400, and this IS supported internally by GSX now. The new 747-8 is not, but there's a file you can download in the sharing section of the forum which should work.
-
open customize aircraft and use these values.. they are for 747-8 but work flawlessly....
[exit1]
pos = -3.00 24.30 4.92 5.00
code = (L:7X7XCabinDoor1L,number)
name = Exit L1
[exit2]
pos = -3.25 10.88 4.92 0.00
code = (L:7X7XCabinDoor2L,number)
name = Exit L2
[exit3]
none
[exit4]
pos = -2.50 -27.10 4.92 -10.00
code = (L:7X7XCabinDoor5L,number)
name = Exit L5
[service1]
pos = -3.00 24.30 4.92 -5.00
code = (L:7X7XCabinDoor1R,number)
name = Exit R1
[service2]
pos = -2.50 -27.10 4.92 10.00
code = (L:7X7XCabinDoor5R,number)
name = Exit R5
[cargo1]
pos = 2.00 20.28 3.00 0.00
code = (L:7X7XforwardcargoDoor,number) 990 >=
name = Cargo FWD
uldcode = AUTO
[cargo2]
pos = 2.00 -17.00 3.00 0.00
code = (L:7X7XaftcargoDoor, number) 990 >=
name = Cargo Rear L
uldcode = AUTO
[cargomain]
none
-
Open the FMC FS Actions-doors. If OPEN, close it and open again, wait and all goes fine.
No... it still get that Open Exit 2 "prompt.
My mistake, sorry. It worked for me when GSX asked to open Entry 1. GSX asked for Exit 2 still an issue.
-
this will solve it!
-
this will solve it!
I'll try out you configuration as soon as I land. ;D
-
open customize aircraft and use these values.. they are for 747-8 but work flawlessly....
[exit1]
pos = -3.00 24.30 4.92 5.00
code = (L:7X7XCabinDoor1L,number)
name = Exit L1
[exit2]
pos = -3.25 10.88 4.92 0.00
code = (L:7X7XCabinDoor2L,number)
name = Exit L2
[exit3]
none
[exit4]
pos = -2.50 -27.10 4.92 -10.00
code = (L:7X7XCabinDoor5L,number)
name = Exit L5
[service1]
pos = -3.00 24.30 4.92 -5.00
code = (L:7X7XCabinDoor1R,number)
name = Exit R1
[service2]
pos = -2.50 -27.10 4.92 10.00
code = (L:7X7XCabinDoor5R,number)
name = Exit R5
[cargo1]
pos = 2.00 20.28 3.00 0.00
code = (L:7X7XforwardcargoDoor,number) 990 >=
name = Cargo FWD
uldcode = AUTO
[cargo2]
pos = 2.00 -17.00 3.00 0.00
code = (L:7X7XaftcargoDoor, number) 990 >=
name = Cargo Rear L
uldcode = AUTO
[cargomain]
none
Now the jetways won't work....
Every time someone alters the .cfg to make one function work, they subsequently prevent another function from working.
ADMINISTRATOR:
When a developer creates an aircraft (in this case, the PMDG 748i), the developers for this software should be releasing updates to accommodate for the new aircraft. The expansion is great, but what use is it when it does not support new releases? In the real world, airports made adjustments for new aircrafts; they configure gates to support A380s and 747-800 Intercontinentals, yes?
PMDG releases the 8i... shouldn't there be an update to fix the gate issues for this aircraft?
-
Now the jetways won't work....
What do you mean with "jetways" ? Default jetways ? GSX Level 2 jetways ? Where ? Made by who ?
ADMINISTRATOR:
When a developer creates an aircraft (in this case, the PMDG 748i), the developers for this software should be releasing updates to accommodate for the new aircraft.
We usually do, but you cannot expect we'd follow each and every release of every airplane daily. That's why GSX comes with an easy to use airplane configuration editor, fully documented, that allows everybody to create a configuration for every airplane that comes out, without having to wait we'll add it to the internal GSX database.
The sort of service you are asking for, is something like a paid subscription service, in which we could set apart some kind of budget to pay someone that would spend all his working hours looking for new airplanes released, BUY ALL of them, and make a professionally-made configuration for them, which will appear in GSX automatically.
Yes, we are looking in doing something like that in the future, but always an as option. In the meantime, we offered all the means to BOTH create a configuration for yourself AND a sharing area to download configurations made by others.
The expansion is great, but what use is it when it does not support new releases?
GSX can support every new airplane released, if you use the included instruments to add support for it. In addition to that, we have a Sharing section in this forum, were users can share they own configuration and you can download the files, if you don't want to use the GSX airplane configuration yourself.
In the real world, airports made adjustments for new aircrafts; they configure gates to support A380s and 747-800 Intercontinentals, yes?
Not sure how GSX can be considered "an airport". Unless you are changing subject here, and are starting to refer to a particular airport.
PMDG releases the 8i... shouldn't there be an update to fix the gate issues for this aircraft?
Which gates issues ?
-
You are missing the main topic, admin... basically either there isn't support for the PMDG 748i or THE .CFG IS WRONG. The .cfg for this particular aircraft will not allow the cargo to be loaded into the aircraft! Below is FSDT profile installed:
[aircraft]
nosegear = 25.94
refueling = 1
battery = 1
iscargo = 0
trafficcones = 0
preferredexit = 3
wingrootpos = 3.42 -4.51 2.80
wingtippos = 34.33 -21.02 2.80
fuelpos = 0.00 0.00 0.00
waterpos = 0.00 0.00 0.00
lavatorypos = 0.00 0.00 0.00
engine1pos = -21.46 -8.23 -0.78
engine2pos = -12.45 0.02 -1.61
engine3pos = 12.45 0.02 -1.61
engine4pos = 21.46 -8.23 -0.78
[exit1]
pos = -2.81 24.26 0.67 0.00
code = 2
name = Exit 2
embeddedStair = 0
[exit2]
pos = -3.31 11.01 0.67 0.00
code = 1
name = Exit 1
embeddedStair = 0
[exit3]
remove = 1
[exit4]
pos = -3.36 11.38 0.66 0.00
code = 1
name = Exit 1
embeddedStair = 0
[service1]
pos = 3.06 24.76 0.66 -0.00
code = 0
embeddedStair = 0
[service2]
flip = 4
code = 0
embeddedStair = 0
[cargo1]
pos = 3.08 19.28 -1.44 0.00
code = 2
name = Exit 2
embeddedStair = 0
uldcode = AUTO
[cargo2]
pos = 3.08 -15.69 -1.44 0.00
code = 2
name = Exit 2
embeddedStair = 0
uldcode = AUTO
[cargomain]
pos = 1.63 -20.23 0.58 0.00
code = 2
name = Exit 2
embeddedStair = 0
uldcode = AUTO
Note the items in red... According to the GSX .cfg profile for the 748i, passenger exit 1 and cargo 1,2 and cargomain are tied into Exit 2. When ever you began to load passengers and cargo, GSX asks that you open EXIT 2...
You can open EVERY DOOR of the aircraft and it will still asks that you OPEN EXIT 2! The passengers will board because [exit2] (aptly named Exit 1) has been cleared and opened but the cargo will not load.
Once this is cleared, it should not matter what airport you use, because you alter that in the airport configuration settings.
Hope this helps.
-
You are missing the main topic, admin...
I'm not missing anything.
basically either there isn't support for the PMDG 748i or THE .CFG IS WRONG.
Of course is wrong. Who made it ? The file I posted here doesn't look anything like that:
http://www.fsdreamteam.com/forum/index.php/topic,19003.0.html
According to the GSX .cfg profile for the 748i, passenger exit 1 and cargo 1,2 and cargomain are tied into Exit 2. When ever you began to load passengers and cargo, GSX asks that you open EXIT 2...
Sure.
The file you are using IS definitely wrong but, as I've said, it's not what has been posted in the sharing section of this forum.
-
Stand by. trying something out.
-
Okay. I fixed it.... somewhat. ;)
By default, the first pax door on the PMDG 747 series is L Entry 1... GSX does not recognize that... It recognizes Exit 2. However, you can not configure the doors like it SUPPOSED to be in the PMDG without GSX working. So this is what I did:
I went into the Customize Aircraft menu in GSX and RESET THE ENTIRE CONFIGURATION. That, in turn will wipe the configuration file.
Next, I labeled the Pax Door 1, which is the jetway door, L ENTRY 1. I then went into the 3D editor and MOVED door 1 position to Door 2.
Then I DISABLED Cargo Main... this here is the main problem, because GSX failed to make two separate configurations for the cargo variant and the passenger variant of the 747... so GSX recognizes Cargo Main (for the 747/748i/F) as EXIT 2!
I then labeled Pax Door 2, L Entry 2 and moved its position to the first door using the 3D editor.
I created Pax 4, labeled it L Entry 5 and moved it to the last left door of the 747... that is where the airstair positions itself on the aircraft.
Finally, I made Service 1, Cargo 1, Cargo 2 and Service 2 doors open and close without GSX checking them.
Ran the GSX service and everything now works... I moved the jetway to the 2nd door because realistically you don't want economy walking through First and Business Class.(https://www.facebook.com/photo.php?fbid=2088327667853264&set=p.2088327667853264&type=3)
-
By default, the first pax door on the PMDG 747 series is L Entry 1... GSX does not recognize that... It recognizes Exit 2
That's normal, and it's what you are supposed to see when an unsupported airplane is being used with NO configuration. So, you know you must create a new one. Or download a pre-made one that works, like I said you should...
Ok, so you wanted to do it yourself, which is fine...
I went into the Customize Aircraft menu in GSX and RESET THE ENTIRE CONFIGURATION. That, in turn will wipe the configuration file.
That's what the Reset does.
Next, I labeled the Pax Door 1, which is the jetway door, L ENTRY 1. I then went into the 3D editor and MOVED door 1 position to Door 2.
This is wrong, and not required. What you should have done, if you want to have a *GSX* Jetway moving to the 2nd door was:
- Create Door 1 normally, and leave it there.
- Create Door 2 normally, and set it as a "Preferred Exit", which is done either in the dialog by clicking on the "Preferred Exit" label, which will turn blue to indicate the Door 2 is now the preferred one, or in the 3d editor, by pressing F2 when editing the Door 2, which will also turn Blue, to indicate it's the preferred exit.
Then I DISABLED Cargo Main... this here is the main problem, because GSX failed to make two separate configurations for the cargo variant and the passenger variant of the 747... so GSX recognizes Cargo Main (for the 747/748i/F) as EXIT 2!
GSX hasn't failed in anything. The configuration you are working on is valid for the currently loaded airplane only. If you want to configure a new variant, you must load it first, and configure that one.
If the airplane are similar, you can SAVE some time this way:
- After you complete a configuration for one variant and are sure it's saved, load the other variant and start creating a configuration by doing something minimal, like moving a door or even just changing its name, just to let the editor create a new GSX.CFG file in this new variant folder.
- Copy the GSX.CFG that has been created in %APPDATA%\Virtuali\Airplanes\AIRPLANE_NAME folder for the FIRST variant (the one you completed earlier) to the %APPDATA%\Virtuali\Airplanes\AIRPLANE2_NAME folder, the one for the variant you just created.
- Restart Couatl, so the variant will now use the same configuration of the first one, which you can change in their differences only.
This is not required, it's just a way to save time.