Direct Airplane Interface, a new GSX feature

[mseiwald]

Jap this would be a really cool Feature if doors would operate automatically.

[blueskydriver]

Just installed GSX tonight and now going through it. My biggest question right away is this; Is there a way to handle the aircraft pax, catering and cargo doors outside of the PMDG 737NGX method of assigning keys to them and/or using the FMC (CDU) to do this?

The reason is this, when using the PMDG 737NGX in a full-size homecockpit (meaning the type you sit in and fly, not desktop), the PMDG 737NGX CDU is not used. Currently, I am using Project Magenta, but it has ntohing to do with PMDG in the sense of interaction. Another way to see this is, think of just using the PMDG 737NGX flight model only. So, without the PMDG 737NGX FMC (CDU) being used, there is no way to key command the doors.

With AES, the doors were not required to be opened, but GSX has the requirement. Thus, either another way of keying the doors is needed or a way to disable the door open requirement. However, I could use FSUIPC for the doors, but not sure at the moment of the key commands and if they'll workout correctly... Do you know which I should use in this case being this is not a default FSX aircraft being used? Better yet, has anyone setup the keys with the PMDG 737-700 NGX FMC (CDU0 and can copy the data from the .ini file they're located in?

Another issue right way is the Pop-up dialog for making selections. You have the Pop-up being brought up via the Ctrl-F12 keys, which is fine and can be changed, but the problem is where it pops up and how long it stays up. Currently, it pops up center screen and it only stays up for about 30 seconds. The problem is that 30 seconds is way to short for it to be on screen and for a center starting position every time that FSX is opened and closed, is difficult because it has to be moved each time.

With AES you could use a remote PC to select the gates for the follow-me vehicle, why not a remote selection method for all the pop-up windows in GSX? The reason is in a home cockpit, I use a 3 projectors on a huge screen, so a pop-up window really takes awy from the illusion of the flying. Additionally, a way to include the use of the mouse scroll wheel to quickly scroll the gates would be nice because using the F1 or F2 keys is way too slow.

I know most Add-on companies do not think about cockpit builders/home cockpit builders, but I wish you did. You would not believe the use we get from your products. We essentialy follow the same methods as desktop flyers, but we're more concerned with the events and those events sounds when discussing programs like AES and GSX. So, when we call for the boarding/deboarding, catering, cargo, fuel truck and etc., we see some of the vehicles, but we hear them more from an enclosed cockpit. Therefore, the sounds are more effective from the cockpit position. Where in a desktop, the sounds are usually right in your face and not position located. In other words, when a vehicle is at the rear of the plane it sounds like it is at the rear and not in our face.

Okay, I guess I am rambling a bit, but I very animated about the use of a home cockpit and I tend to plea with the Add-on companies to think of us builders, as well as the desktop pilots. I bet you didn't know it that when someone comes to see my cockpit and they see the AES and now GSX vehicles, the first thing they say is "WOW! where did you get those cool vehicles that service the plane?"...

Finally, I will post more as I go along. I must say though, FS DreamTeam you guys have out done yourselves again...BRAVO on this great program! Keep them coming and I do hope to see the real passenger animations soon.

Blueskydriver

[virtuali]

I'd say that, in order to control an airplane with non-standard door controls, your best option would probably using Linda

http://forum.avsim.net/forum/424-linda/

which is made just to allow communication between hardware and complex airplanes like the PMDG, and I understand the NGX is very well supported.

This would be the correct way of dealing with this. A "GSX ignore the doors" option wouldn't be a good idea: since you said yourself seeing the nice GSX animations is one of the highlights of your installation, it won't look very nice having (for example) the service people or luggage passing through closed doors.

[blueskydriver]

Thank you for replying to my post. I certainly agree with you on the non-standard door controls that are otherwise assigned through the methods that PMDG is using for the 737 NGX. Sadly, with the NGX it is tied to the Systems of the Aircraft and thereby, the CDU must be available to select the options pages to assign the keys for the doors. And, even though you assign them, they'll still not work because once you remove the Systems, you effectively remove the power to open them (in a way of speaking).

Considering that how I am using the flight model only, there is no way to get around this door power issue (believed me when I say "I tried"). Although, the method of using the flight model inconjunction with the older PMDG visual model, provides a way for you to still get the animations and doors openclose routines to work. Thus, the fwd left door, the aft left door and both cargo doors can be opened via FSUIPC "Toggle Aircraft Exit" (parameters 1-4 must be used and by assigning them to keys like Ctrl-NumPad 1 through Ctrl Numpad 3; Ctrl-Numpad 4 would be the Catering doors, but they do not open). So, collectively I can use the GSX, but without using or selecting the Catering Vehicles aspects of the add-on.

Finally, I'd still like to see a hold on the pop-up window, so that once you place it somewhere, it'll be there next time you close/open FSX, as well as, for the pop-up to not disappear until I press another keyboard command(s). In addition, a remote computer interface like that of AES would be extremely useful because it would remove anymore then needed windows from the FSX screens (projected images). I think Peter Dowson was touching on the same aspect in a different post; for cockpit builders we prefer no keyboards and/or a mouse, so any other way of doing a pop-up/control window remotely is much better then seeing it on the main FSX computer...

BSD

[blueskydriver]

Looks like I might have spokento soon. After trying the GSX functions, the Baggage handlers do not see that the Cargo Doors are opened; I keep getting the message to open them, even though they are opened. Thus, without the baggage being unloaded/loaded the fueling will not start, as well as the loading/unloading of passengers will not progress.

It might be a total loss if there is no way to adjsut the GSX to see the doors are opened. What area of the files is GSX looking to read that the doors are in effect opened/closed? Is it part of the FSX.cfg, model.cfg, panel.cfg or somewhere else that I can adjust for GSX to read the file. Assuming GSX is using simconnect or fsuipc methods, there has to be a way. Or, what files can I send you to help rectify this?

BSD

[blueskydriver]

Umberto,

I've been reading other threads regarding this issue and you say that the GSX only reads if the doors are open or not. Can you tell me where GSX reads this data from? If I can figure out where the read is, I should be able to produce the action to show the read data...

BSD

[virtuali]

When a model is not using standard doors commands, GSX reads the L: variables that controls the model animations, which are embedded in the .MDL file so, if you can write the proper values, GSX will be ok with it. As I've said, with Linda+FSUIPC, you should be able to read/write any L: variable you want.

The Linda support forum could be a good place to ask for more details, since they worked a lot on the PMDG NGX.

[blueskydriver]

Thank you Umberto.

My problem is not so much with PMDG 737 NGX, it is the idea that the actual aircraft model being used is from the PMDG 737-700 (FS9). I know before you say "wait a second?"...let me explain.

As you likely know, PMDG 737 NGX does not work without it's own systems. So, for guys like myself, we're looking for the right flight model to work with Project Magenta, ProSim or SimA. The PMDG 737 NGX has a good model, but in order for it to visually work you have to import the older PMDG 737 (FS9) model file. Thus, it is a mix of both.

I know you're not working GSX with PMDG 737 (FS9), but I was hoping the mdl file being read would work in a similar fashion as an FSX plane for the reading of the L: variable. The thing I am not sure about is that if the mdl is producing an L: variable or not.

As far as what I see, the aircraft is opening the left fwd and aft, as well as the cargo doors. The rear stairs and the cargo/catering vehicles do not line up properly, so I thought it was a factor (or not)? Additionally, I thought to try the renaming of the door opening process (key mapping) and even add the door gauge. In both cases doors open, but like you said I have to find out if that L: variable is actually there and actually working...

Do you know of a way that I can determine this, such as in the case with using FSUIPC. With Linda, I don't think it would work, since the mdl is older...

Thank you again for all your help,

John

[virtuali]

GSX doesn't read the .MDL file and doesn't need it. The L: variable is not "produced" by the .MDL, but by the PMDG gauges so, what I was saying is, if you can produce the same L: variables using Linda+FSUIPC, and you surely can, it will work with GSX even if you don't use the original .MDL and don't load any gauges at all.

I repeat and confirm: this CAN be done using Linda+FSUIPC, without having to modify GSX in any way.

Sometimes an L: variable is also altered/created by the .MDL itself, but it's usually happening in the Virtual cockpit, when you click on something. This usually fires some kind of event, which will in turn modify an L: variable but, it's really not a big difference, as long as you replicate that same using other means ( C/C++ gauge you write yourself, or Linda or FSUIPC or both...), and the L: variable gets the correct values, it will work.

[FS++]

I repeat and confirm: this CAN be done using Linda+FSUIPC, without having to modify GSX in any way.

Sometimes an L: variable is also altered/created by the .MDL itself, but it's usually happening in the Virtual cockpit, when you click on something. This usually fires some kind of event, which will in turn modify an L: variable but, it's really not a big difference, as long as you replicate that same using other means ( C/C++ gauge you write yourself, or Linda or FSUIPC or both...), and the L: variable gets the correct values, it will work.

For what it's worth, I can confirm the statements above are correct.

Ian

[nordstar]

Hi! i'm new to gsx, but found out some anomalies regarding the doors.QW 757 should be fully supported, but it's not, at least not the cargo versions (PF & SF)FSX std doorhandlings for QW757-200 (PF&FS) are Shift E+1 for 1st exit and shiftE+3 for cargo-doors(belly)the other doors are custom by QW-controlpanel(Main cargo).QW757-300 handels 4 doors in fsx std style(L1 main entry,L2 main entry,Cargo,L4 main entry) and the rest custom.GSX as programmed allwayes check foor the doors before starting boarding,catering,cargo-loading.It would be better if there were a switch that started the anim after manually opening the doors instead of letting GSX automatically start/stop the animation after door open-close check.Then it would be possible to have anims att all doors without bothering about HOW THE DOORS ARE HANDELD BY THE AIRCRAFTs INTERFACE OR FSX std DOORHANDLING COMMANDS.The aircraft developer can do what he want.s and GSX can still handle it as the anim will be started by pushing the switsh after opening the doors and you stop the anim manualy by pushing the switch before closing the door.At least i would rather like that instead of auto handling of anims.
I also have a question about the cargo/containerloading facility and the de-icing.Where and how to get to see these vehicles.I've never manage to see those anims.
I also wonder how to get rid of dubble pushbacktrucks at gates.The default ones are still standing there and gets driven through by te GSX one at pushback.If i lower the Airport vehicle slider in FSX all FSX airport vehicles dissapears.......

[virtuali]

QW 757 should be fully supported, but it's not, at least not the cargo versions

The QW757 IS fully supported. But, as explained many times on the forum, GSX doesn't support main cargo doors on the left side of the airplane. They will come in a future update but, for the time being, a cargo airplane will work only with the doors that are shared with the passenger version.

It would be better if there were a switch that started the anim after manually opening the doors instead of letting GSX automatically start/stop the animation after door open-close check.Then it would be possible to have anims att all doors without bothering about HOW THE DOORS ARE HANDELD BY THE AIRCRAFTs INTERFACE OR FSX std DOORHANDLING COMMANDS.

That would be wrong from a realism point of view, because you (as the airplane crew) ARE supposed to operate the doors only, and the ground crew is supposed to do their thing independently.

But the main reason why it's better how it's done right now, is that by doing this, if the airplane is correctly configured, it's not possible to get into a situation were you would see funny-looking "man passing through bulkheads" situations, which would instead possible if you were able to give GSX a go to start a service, without really have opened the door.

If you *really* like that behavior, then simply configure your airplane with all doors set to "ignore", and be sure you open doors BEFORE starting the service, so there you have your "switch": you simply use the GSX menus as "switches", with an airplane with all doors set to "Ignore"

I also have a question about the cargo/containerloading facility and the de-icing.Where and how to get to see these vehicles.I've never manage to see those anims.

There aren't any, they will eventually appear with an update.

I also wonder how to get rid of dubble pushbacktrucks at gates.The default ones are still standing there and gets driven through by te GSX one at pushback.If i lower the Airport vehicle slider in FSX all FSX airport vehicles dissapears.......

There aren't any double pushback trucks at the gates, because the GSX installer will patch the default vehicles_airport.bgl file to get rid of them. Have you changed that file with a 3rd party replacement ? That would explain why your file wasn't patched.

[DMac10121]

Would it be possible to have gate or aircraft specific handlers, by reading the AFCAD or the aircraft.cfg? Or does GSX already do it? If not, I think it would be a cool but doable future feature.

[virtuali]

Or does GSX already do it? If not, I think it would be a cool but doable future feature.

It's already doing it. GSX uses a scoring system to decide which operator use, depending how well it matches the ICAO, like 1 points if it matches only the 1st letter (let's say, K), 4 points if it matches the whole IVAO, and an additional point if it also matches the atc_airline_code in the AFCAD parking.

But when there's a tie, with several operators matching at the same score, the selection will be random between all candidates. We plan to add a feature to present a menu, for the user to choose the operator if there's a tie.

[DMac10121]

Or does GSX already do it? If not, I think it would be a cool but doable future feature.

It's already doing it. GSX uses a scoring system to decide which operator use, depending how well it matches the ICAO, like 1 points if it matches only the 1st letter (let's say, K), 4 points if it matches the whole IVAO, and an additional point if it also matches the atc_airline_code in the AFCAD parking.

But when there's a tie, with several operators matching at the same score, the selection will be random between all candidates. We plan to add a feature to present a menu, for the user to choose the operator if there's a tie.

OK, thanks for the quick reply. I only asked because I parked at the WestJet pier at CYVR yesterday twice and got AC servicing both times. Thanks for the help!