FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: XCLTM3 on September 04, 2013, 04:38:52 am
-
Anyone else had the opportunity yet to test the PMDG 777 with GSX?
Both Cargo loaders/unloaders go to the Right Rear Cargo Door and ignore the Front Right Cargo Door.
Checked the GSX Customize Aircraft Menu and as far as I can see, the Cargo Doors appear to be OK.
Umberto, any idea?
Rgds,
Steve
-
Also the catering service wouldn't work for me.
Umnerto, plus help !
-
I was able to customize the loaders to get them to go to the right areas using the 3d editor and cycling through the different door settings. One thing I still can't figure out though is why GSX isn't recognizing that I've opened the doors it's requesting. GSX states "Waiting for Exit 1 and Exit 2 to be opened" and so I open the main exit and it just goes to asking for "Exit 2", however even after opening all of the doors on the aircraft (both cargo and passenger) the "Exit 2" request still flashes and the simulation of the cargo being offloaded doesn't startup. From what I could see GSX was viewing Exit 2 as my cargo doors. Also, unlike a lot of my other aircraft, there is no stair truck at the rear left exit with the 777.
Hope this additional information helps, and any further clarification to help me get GSX up to snuff with the new guy in town would be awesome!
-
I was able to customize the loaders to get them to go to the right areas using the 3d editor and cycling through the different door settings. One thing I still can't figure out though is why GSX isn't recognizing that I've opened the doors it's requesting. GSX states "Waiting for Exit 1 and Exit 2 to be opened" and so I open the main exit and it just goes to asking for "Exit 2", however even after opening all of the doors on the aircraft (both cargo and passenger) the "Exit 2" request still flashes and the simulation of the cargo being offloaded doesn't startup. From what I could see GSX was viewing Exit 2 as my cargo doors. Also, unlike a lot of my other aircraft, there is no stair truck at the rear left exit with the 777.
Hope this additional information helps, and any further clarification to help me get GSX up to snuff with the new guy in town would be awesome!
I'm also getting that same problem with the Exit Doors 1 & 2........let's wait & see what Umberto says/does.
Hopefully GSX are working on a cfg for the 777 as we write.
-
I'm also getting that same problem with the Exit Doors 1 & 2........let's wait & see what Umberto says/does.
It's more than likely that PMDG (same as with the 747 and the 737 NG) used custom XML variables to represent the door's status so, GSX can't check them using the default FSX variables normally linked to Exit1, Exit2, etc.
This means, to get GSX working correctly, you have the following options:
1) Configure GSX to ignore the doors status, by setting the affected door as not having any checks. This is by far the easiest option, and will result in GSX operating correctly, but without checking if the doors *are* open or not, which means if you forget to open them, the service will start anyway, and you'll see baggage and crew passing through the bulkheads.
2) Figure out the names of the custom XML variables PMDG used, and configure the affected doors to use a custom XML expression with a custom name too. This is explained at Page 28 in the GSX manual. Figuring out XML variable names us usually done by peeking inside the .MDL of airplane with an hex editor. You don't have to change/edit anything, just searching for the name (usually contains "door" string) it's enough, the XML expression is usually very straightforward to write, such as:
(L:MyCustomDoorVar, bool)
Then, assign the custom variable a name same as the one PMDG use to name that door, which will help identifying it.
This option, if done correctly, will result having the behaviour of a natively-supported airplane.
3) Wait for us to add a 777 configuration. I'll try to do this as soon as possible, if only to have a look at possible more advanced interactions between the 777 and GSX beyond just doors, for example with wheelchocks, GPUs, etc.
-
Great, looking forward to that config file. Can you also code the cargo pallets for another airline? I want to have ground services unload cargo pallets that say Lufthansa or DHL when I am flying an Aerologic airplane.
-
Thx again Umberto....I'll wait for the GSX certified cfg.
Rgds,
Steve
-
Thx again Umberto....I'll wait for the GSX certified cfg.
I'm downloading the PMDG 777 right now. My only regret is that I will never have the time to fly/learn the bird and have fun with it: I had to buy it ONLY to create a proper GSX config...
-
Thx again Umberto....I'll wait for the GSX certified cfg.
I'm downloading the PMDG 777 right now. My only regret is that I will never have the time to fly/learn the bird and have fun with it: I had to buy it ONLY to create a proper GSX config...
Thanks Umberto for your quick response to this. I appreciate your hard work.
John
-
Thanks Umberto!! Looking forward to the update!! :)
-
where do we download the 777 gsx config?
-
Umberto PMDG implemented time acceleration for long flight to do a 9 hours flight in 1 hour :D. I've just tried with the tutorial flight and works perfectly also with activesky working with winds.
-
It's on the Live Update now. Force a check for updates in the Couatl menu, and it will download the updated files to support the PMDG 777
-
Thank you very much :D
-
I did the live update and I'm still having the same issue. Both loaders go to the rear cargo door, and I'm permanently stuck with it saying "open cargo fwd, open cargo aft" even though I've got all doors open.
-
I did the live update and I'm still having the same issue. Both loaders go to the rear cargo door, and I'm permanently stuck with it saying "open cargo fwd, open cargo aft" even though I've got all doors open.
I'm experiencing the same problem......I've d/l the update twice and even restarted FSX the 2nd time....but still GSX is not playing well with the 777.
Steve
-
I got it working now, just did an fsx restart and all is well.
-
I got it working now, just did an fsx restart and all is well.
Umberto,
after downloading & installing the latest update 4 times now, and restarting FSX 3 times, I'm still having the same problem??
Any idea what is going on???
Steve
-
I did the live update and I'm still having the same issue. Both loaders go to the rear cargo door, and I'm permanently stuck with it saying "open cargo fwd, open cargo aft" even though I've got all doors open.
Doesn't happen here. Be sure you did what I've said here:
http://www.fsdreamteam.com/forum/index.php?topic=5481.msg72711#msg72711
But it shouldn't be related to your case, since if you see the cargo doors labeled correctly, it seems you don't have a .cfg file. However, just to be sure, Reset the config.
-
I did the live update and it is requesting to open the fwd cargo door!
-
I did the live update and it is requesting to open the fwd cargo door!
I can only confirm that after the Live update, the program correctly detects all 777 doors, and correctly recognize them being open/closed. I've just tried it now.
If it doesn't happen on your system, it's because you still have a .cfg file which you edited yourself or downloaded, and it must be removed, either with the Reset button or by manually removing the file.
-
I did the live update and it is requesting to open the fwd cargo door!
I can only confirm that after the Live update, the program correctly detects all 777 doors, and correctly recognize them being open/closed. I've just tried it now.
If it doesn't happen on your system, it's because you still have a .cfg file which you edited yourself or downloaded, and it must be removed, either with the Reset button or by manually removing the file.
Is there any chance there may be a programming problem depending on the panel state we choose to start up with in the 777?
Just asking.....
-
I had to reset my Aircraft config in the Settings for this to work.
Sean
-
I had to reset my Aircraft config in the Settings for this to work.
That's what I've said in all those threads: the user-defined files always take precedence over the files coming from GSX, which of course makes sense, otherwise you would lose the ability to customize a natively supported airplane in the editor.
This means the config MUST be Reset, in order to use a plane which native support has been added AFTER you already started doing your modifications (or downloaded a pre-made .CFG file from anywhere)
Of course, you CAN further customize a natively supported plane, but you must start your first modification from scratch AFTER having updated GSX with the Live Update, so the editor will create a brand new .CFG file BASED on the GSX *updated* (and now correct) native data, which contains custom names and (more important) custom XML variables.
-
Is there any chance there may be a programming problem depending on the panel state we choose to start up with in the 777?
No, because GSX reads the variables that handle the door's visual animation so, regardless of what the airplane simulation is doing, if you *see* the door as open, the variable will react to that.
-
I did the live update and it is requesting to open the fwd cargo door!
I can only confirm that after the Live update, the program correctly detects all 777 doors, and correctly recognize them being open/closed. I've just tried it now.
If it doesn't happen on your system, it's because you still have a .cfg file which you edited yourself or downloaded, and it must be removed, either with the Reset button or by manually removing the file.
I reset the cfg file and downloaded the update, restarted fsx and still get a request to open the fwd cargo door.
Now what?
-
So sorry.....I forgot the cfg. file i had copyed and put into the 777-200 aircraft file. I deleted that and it is ok, now!! Maybe a lesson for other users!
-
So sorry.....I forgot the cfg. file i had copyed and put into the 777-200 aircraft file. I deleted that and it is ok, now!! Maybe a lesson for other users!
I was quite sure of that...yes, of course, a .cfg file in the airplane folder would have an higher priority compared to the one coming with GSX.
The manual explains that, but I admit it could be better explained, this is how the airplane configuration priority system works:
- If there's nothing at all, meaning the airplane is not supported by GSX and there's no config file anywhere, GSX will try to figure out some rough config taking data from the aircraft.cfg. This won't be usually precise enough, but it could be a starting point for a better customization.
- If there's an Intelliscene.cfg in the Simobjects\Airplanes\AIRPLANE_NAME root folder, it will take precedence over the aircraft.cfg.
- If the airplane is supported by GSX in its own internal database ( file FSX\fsdreamteam\Couatl\common\AircraftDb.PYE, which is updated by the Live Update feature ), it will take precedence over the intelliscene.cfg
- If there's a GSX.CFG file in the Simobjects\Airplanes\AIRPLANE_NAME root folder, it will take precedence over the GSX internal database.
- If there's a GSX.CFG in the %APPDATA%\Virtuali\Airplanes folder, it it will take precedence over the GSX.CFG file in the Simobjects\Airplanes\AIRPLANE_NAME root folder.
In addition to that, if you start customizing an airplane with the GSX airplane editor, a new GSX.CFG file will be created in the %APPDATA%\Virtuali\Airplanes\AIRPLANE_NAME folder, starting from data of the best possible data source at THAT time (when you first launched the editor on that airplane).
Best practices are:
- If GSX adds support for a new airplane, especially if it's one with tricky custom variables, it's usually best to remove ALL your GSX.CFG files, either in the Simobjects\Airplane\AIRPLANE_NAME AND in the %APPDATA%\Virtuali\AIRPLANE_NAME folders, otherwise the GSX internal data won't be used.
- The Simobjects\Airplanes\AIRPLANE_NAME is supposed to be used by DEVELOPERS, as the best possible place to put a GSX.CFG file made by themselves for their own airplane. This way, they can easily distribute the GSX.CFG file, because it's on the airplane root folder together with the aircraft.cfg, and users CAN even customize it further, because users modifications made with the editor will appear in the %APPDATA% folder, so the original file supplied by the developer won't be touched.
-
I did the live update and I'm still having the same issue. Both loaders go to the rear cargo door, and I'm permanently stuck with it saying "open cargo fwd, open cargo aft" even though I've got all doors open.
Doesn't happen here. Be sure you did what I've said here:
http://www.fsdreamteam.com/forum/index.php?topic=5481.msg72711#msg72711
But it shouldn't be related to your case, since if you see the cargo doors labeled correctly, it seems you don't have a .cfg file. However, just to be sure, Reset the config.
You might have missed my second reply in the thread, but I've got it now. I just restarted FSX and all was well. Thank you for the quick update and support for the 777.
-
I've forced the live update and I was able to fix the loaders going to the wrong place, but I'm still getting the error where GSX is prompting me to open cargo doors even though they're already open. Any advice?
-
I've forced the live update and I was able to fix the loaders going to the wrong place, but I'm still getting the error where GSX is prompting me to open cargo doors even though they're already open. Any advice?
I have found this happens to me often when my panel state sets the doors to open on loading the flight. If you have your doors closed when the flight loads, gsx sees the doors open before you call them. Like in the PMDG, I used to save a panel state with doors open, but that causes that problem with gsx asking to open an already opened door. You have to press close then open again and then it sees it open correctly.
-
Like in the PMDG, I used to save a panel state with doors open, but that causes that problem with gsx asking to open an already opened door. You have to press close then open again and then it sees it open correctly.
GSX simply ask for a variable value to FSX, because even a custom XML variable is still an FSX variable, it doesn't have any interaction with the airplane directly.
If it's not updating correctly when saving or loading a state, it means those animation variables are not kept in sync with internal doors status when the state loads and they go back in sync only when you operate the door again.