PilotsDeck/StreamDeck Profile for GSX Pro
(Including GSX Service/Question Automation!)
This is the standalone Version of the GSX Integration built in to my Fenix A320, FBW A32NX, iniBuilds A300 and WorkingTitle 787 Integrations for PilotsDeck.
(So if you have one of these Profiles, you don't need this Package! Just copy over the GSX Folder on your StreamDeck to any other Profile)
- Full interactive & dynamic GSX Menu on the StreamDeck! You can do everything now from your StreamDeck - the GSX In-Game Menu can be disabled in the Toolbar.
- Displays current De-/Boarding and Cargo Un-/Loading Progress
- A "Smart-Button" which calls the next Service in the Sequence (the whole Depature including Push-Back through one Button) and shows the current active Service, Question, selected Gate or selected De-Icing Pad
- GSX Service Calls can be fully automated and certain GSX Questions can be skipped (like in Fenix2GSX) - if you ever wondered if you can Fenix2GSX for Plane XY: This is the closest you can get ;)
- NOTE: You don't need to have a StreamDeck to use it. The included Lua-Script File for FSUIPC (paid Version required!) can be used independently from PilotsDeck!
There are both a SD and XL Version in the Archive - choose the one for your Setup! They both have the just mentioned Features, the XL Version has only additional Buttons to directly call a specific Service. There will be no SD+ Version since it has too less Buttons, but you can copy & paste the Buttons to your SD+ of course!
The Package contains the following:
- The mentioned Profiles as .streamDeckProfile Files
- Lua-File which provides the Menu-Data for PilotsDeck and does the Service Calls
Requirements & Setup
Requirements:
- You need to have at least Version 0.7.8 of my PilotsDeck Plugin installed & running
- Since the core Functionality is provided through a Lua-Script, you need to have a registered (purchased) Copy of FSUIPC7
Installation:
- Double-Click the Profile File to install it. Make sure to select the correct StreamDeck first in the UI before installing the corresponding Profile (if you have more than one StreamDeck).
- Place the Lua-File in your FSUIPC7 Application Folder (the Path where you've installed it).
- Setup the Automatic Start of the Lua-File in your FSUIPC7.ini (make a Backup before editing it, see Description below).
- Edit the Path to your Addon Manager/GSX Installation in the Lua-File (see Description below).
You can also start the Script manually when you Start a Flight if you prefer that for any Reason.
Automatic Start for Lua-File:
First you have to start FSUIPC (and close) once so that FSUIPC will add the Lua-Files to it's Configuration. (You can of course add them manually, IF you know how to do that)
Add this to your FSUIPC7.ini File (same Folder where the Script is):
[Auto]
1=Lua GSX_AUTO
Ensure the following: The [Auto] Section can only exist once. If you already have such a Section, add the '1=Lua GSX_AUTO' Line below exisiting [Auto] Section. The Number assigned to the Script does not matter, but ensure each Number exists only once in that Section (so if you already have '1=Lua SOMETHING', add it as '2=Lua GSX_AUTO' and so on).
GSX Script
In order for the Script/Profile to work, you need the configure the Path to your "Addon Manager" Installation (where GSX resides). Edit that Line with your real Path (use forward-Slashes!) in the GSX_AUTO.lua File:
local GSXAUTO_CFG_PATH = "X:/YOURPATH/Addon Manager"
Your Path has to be in the same Way: using Forward-Slashes ( / ), enclosed as String ( " ), must end with the Addon Manager Folder without a trailing Slash.
The Script uses FSUIPC Offsets 0x4300 through 0x4533, if theses are already used by something else in your Setup, configure a new Base-Address!
If you use this Script only for the Service Automations without any Output-Devices (like StreamDecks), you can disable this Menu-Output (set GSXAUTO_CFG_OFFSETS to false).
Usage
StreamDeck Menu
The Usage of the Menu is pretty mutch the same as with the In-Game Menu: Use the "GSX Menu" Button to open/activate the Menu, then select something in the Menu. If GSX has any Question (De-Ice, Direction) directly select the Answer in the Menu.
Since the GSX Menu is now completely on the StreamDeck, you can (and should) disable the In-Game Menu to prevent it popping up! (=Icon not white in the Toolbar)
The only Thing to note: the Menu on the StreamDeck will not be "empty" when the GSX Menu times out. So if you did not select something for some Time, press the Menu Button first before selecting something in the Menu (even if you see the Service Selection on the Deck).
The mentioned "Smart-Button" (aka the Service/Call Button) calls the next Service in Sequence when pressed, depending on the current Flight-State:
- On Start, it will call the Refuel Service
- When the Fuel Truck is on the way or active, it will call the Catering Service
- After Catering is finished, it will call Boarding
- After Boarding is finished, it will call Push-Back
- During Push-Back the Button will show if there is a Question active (e.g. "De-Ice?" or "Direction?"). Answer that through the Menu!
- After Push-Back is finished, it will confirm good Engine-Start. That is: selecting Option 1 in the Menu. So if it you press it before GSX waits for that Confirmation, the Button will stop the Push-Back.
- If you select a Remote De-Ice Pad during "Taxi-Out", the Button will show the Pad's Name. When you have arrived there, the Button will start the Procedure.
- When you have selected your Gate during "Taxi-In", the Button will show the Gate Number.
- When you have arrived at the Gate (Engines stopped), it will request Deboarding
The other Buttons on the (XL) Profile call the respective GSX Service, but some Notes:
- "Dis-/Connect" Button will toggle Jetway, Stairs and GPU (on non-Jetway stands). Use that to connect the Plane intially!
- The "Jetway" Button just sends the normal TOGGLE_JETWAY to the Sim instead of calling the Jetway through GSX. This is more for troubleshooting (e.g. GSX won't call the Jetway because it is waiting on another Service)
- The "Unfreeze" Button is an "Emergency-Button" only to be used when your Plane does not move after GSX Push-Back. (Like the name suggests it attempts to unfreeze the Plane)
Service Automations
The Service Automations are enabled by default & globally. You can customize them either globally by setting the respective GSXAUTO_CFG_* Variable on the Top of the File (See Comments in File for Description).
But they can also be set individually per Airplane (and even Variant): check the Examples in the GSX_AUTO_LOAD_AC Function on how to do that (very basic Understanding of Lua required).
Don't worry if you use Fenix2GSX: The Script disables all Automations when the Fenix is loaded! ;)
Service Flow:
- Refuel will be called as soon as the Aircraft is connected (=Jetway and/or Stairs connected) and the Navigation-Lights are on.
- Catering is called together with Refuel (can't be separated - only with an AC specific Customization Script).
- The Boarding Call can have three different Triggers:
- As soon as the Fuel-Hose of the GSX Truck is connected
(GSXAUTO_CFG_AUTOSERVICES_BOARDAFTERCATER & GSXAUTO_CFG_AUTOSERVICES_BOARDAFTERREFUEL both false) - As soon as Catering is completed
(GSXAUTO_CFG_AUTOSERVICES_BOARDAFTERCATER is true) - As soon as Refuel is completed
(GSXAUTO_CFG_AUTOSERVICES_BOARDAFTERREFUEL is true and GSXAUTO_CFG_AUTOSERVICES_BOARDAFTERCATER is false)
- As soon as the Fuel-Hose of the GSX Truck is connected
- The Stairs are removed when Boarding is finished (GSXAUTO_CFG_REMOVESTAIRS_AFTERBOARD)
- The Jetway will be removed automatically by GSX as soon as Push-Back is called
- Associated Doors are open/closed automatically by GSX if the Plane/Door supports that (else an AC specific Customization Script is required)
- Deboard is called as soon as the Engines are stopped and the Beacon is off. (Jetway/Stairs are called automatically by GSX)
- There is a small Delay of 60s before the Refuel Service is called again. If you need more Time, just turn off the Navigation-Lights!
Non StreamDeck Usage
The StreamDeck Buttons all call Lua Functions in the GSX_AUTO Script. Since that is done by standard FSUIPC Mechanics, you can also call these Functions with any Joystick-Button/Key bindable by FSUIPC!
- Select "LuaToggle GSX_AUTO" in the Dropdown for "Control sent when button pressed" (Button & Switch Assignments in the FSUIPC GUI)
- Enter the associated "Flag-Number" of the Function you want to call as Parameter (See the event.flag Lines at the Bottom of Lua-Script File for the Functions and their Number)
This way you could for Example bind the mentioned "Smart Button" to a Joystick-Button (i.e. to start Boarding earlier or Confirm/Stop Push-Back).
I however just want it to be used as a keypad to request all the services instead of using my mouse to select it on screen.
So basically I don't want any automation. How would i do that please?
2 months ago
2 months ago
Fragtality
clintferns
i cannot get it to work. I have full version of FSUIPC7, i have installed the PilotDeck Plugin and the Streamdeck profile, but still GSX does not work. Only dots on all buttons.
What am i missing?
3 months ago
3 months ago
Fragtality
L00K
3 months ago
3 months ago
Fragtality
sonny147
I have checked the log and there seems to be no errors.
EDIT: I have now seen that the delay in updating the Menu in the Streamdeck and receiving a feedback is around 10 seconds. Also, is there any way to still have the on screen messages?
4 months ago
4 months ago
Fragtality
Kiwi0ne
"259750 *** LUA Error: C:\FSUIPC7\GSX_AUTO.lua:8: '' expected near '/'"
Any help would be greatly appreciated.
EDIT: Issue now fixed, I was missing the " " around the file path in the GSX_AUTO script. Now all working as intended.
4 months ago
4 months ago
Fragtality
MisterV
5 months ago
5 months ago
Fragtality
rparpinelli
The path to Addon Manager is C:/Program Files (x86)/Addon Manager
FSUIPC loads the GSX_AUTO lua script
PD version is 0.7.11
SD reacts in some way - without MSFS running, it shows "0" on every key, after starting MSFS it shows "..."
What might I be missing?
6 months ago
6 months ago
Fragtality
borisvp
7 months ago
7 months ago
Fragtality
HaiiroFTW
7 months ago
7 months ago
Fragtality
simtw1104
The GSX actions are executed with delay ... any idea what can cause a delay when trigger any gsx action ?
12 months ago
I don't know what you mean with "Delay"?
The Script/StreamDeck Integration just calls the Services by a different Way, but it does not change GSX' Behavior. The Fuel-Track for Example will not instantly beamed to the Aircraft just because it is called in a different Way.
The Menu-Entries are refreshed every 500ms, that is not really a Delay. And it will only show what it reads from GSX. So if the displayed Menu-Entries do not change after 500ms, there is nothing the Script could do about.
12 months ago
Fragtality
EisernUnion