Generalized Version of Fenix2GSX bringing GSX Automation and App Volume Control to all Aircrafts!
- GSX Automation (ie. calling Services, skipping Questions) can be enabled for all Aircrafts
- App Volume Control available to all Aircrafts to control the Volume of Apps via Knobs in the Cockpit
- Aircraft Plugin System to enable Fuel-, Payload- and Equipment Sync for specific Aircrafts
- SmartButton Control for every Aircraft to call the next Service / trigger the next Call (the INT/RAD Thingy known from Fenix2GSX)
- EFB App for MSFS2024 to check on the App Status, SmartButton Trigger and GSX Menu
- PilotsDeck Integration bringing the GSX Menu to your StreamDeck (replacing the GSX Script known from my PilotsDeck Profiles)
- Can be used together with Fenix2GSX, Any2GSX is not meant as a Replacement (check the Addon NOTAMs)
Check the Addonn Repository which Aircrafts are supported directly out-of-the-box:
Aircraft Plugins
Audio Channels
Aircraft Profiles
- Windows 10/11
- MSFS 2020/2024
- A properly working and updated GSX Installation (not needed when only Volume Control is used)
- Capability to actually read the Readme up until and beyond this Point 😜
- The Installer will install the following Software automatically:
- .NET 8 Desktop Runtime (x64) - Reboot your System if it was installed for the first Time
- Any2GSX' CommBus WASM Module
Download Any2GSX-Installer-latest.exe
(Currently only Development Builds available)
Just Download & Run the Installer Binary! It will check and install Requirements like the .NET Runtime or WASM Module.
Any2GSX will display a orange Circle on its SysTray/Notification Area Icon if a new Version (both Stable and Development) is available. Your existing Configuration persists through Updates (stored persistently in the AppConfig.json File in the Application's Folder).
On the second Installer Page you can select if Auto-Start should be set up for Any2GSX (recommended for Ease of Use). While it is possible to install the WASM Module to only one specific Sim Version/Variant, it is recommended to just install it to all. If you choose to install the WASM Module to only one Simulator, make sure you select Update only existing Installations when updating the App (else the Module will be installed on all Simulators)! The Force Module Update Option is mostly for Troubleshooting to force an Update of the WASM Module.
You do not need to remove the old Version for an Update (unless instructed) - using 'Remove' in the Installer completely removes Any2GSX (including WASM Module and Auto-Start). This also removes your Configuration including Aircraft Profiles and saved Fuel!
It is highly likely that you need to Unblock/Exclude the Installer & App from BitDefender and other AV-/Security-Software.
The App will be installed to (cannot be changed): %appdata%\Any2GSX (C:\Users\YOURUSERNAME\AppData\Roaming\Any2GSX)
DO NOT run the Installer or App "as Admin" - it might work, it might fail.
When starting it manually, please do so when MSFS is loading or in the Main Menu.
To automatically start it with FSUIPC or MSFS, select the respective Option in the Installer. Just re-run it if you want to change if and how Any2GSX is auto started. Selecting one Option (i.e. MSFS) will also check and remove Any2GSX from all other Options (i.e. FSUIPC), so just set & forget.
For Auto-Start either your FSUIPC7.ini or EXE.xml (MSFS) is modified. The Installer does not create a Backup (not deemed neccessary), so if you want a Backup, do so yourself.
If you use Addon Linker to start your Addons/Tools, you can also add it there:
Program to launch C:\Users\YOURUSERNAME\AppData\Roaming\Any2GSX\bin\Any2GSX.exe
Wait for simconnect checked
The Rest can be left at Default.
There are two Version Channel for Updates to be released:
- The "Dev" or "Beta" Version is located in the Source Files as Any2GSX-Installer-latest
(Click 'View Raw' or the Download Icon to the Right to download) - The "Release" or "Stable" Version is located under Releases
(Under Assests, the Any2GSX-Installer-vXYZ.exe File)
Whenever there is a new Commit to Code, the -latest Installer will contain these Changes (the Description of the Commit(s) summarizes what has changed). For example Fixes to open Issues, Changes for GSX Updates or new Features added. So that these Changes & Fixes can be tested publicly.
After some Time and positive/good Feedback, all these Changes will be published as the Release Version.
So some general Rule-of-Thumbs:
- Most Users should use the Release Version
- If experiencing an Issue, then try if the Dev Versions works better
- When eager to test new Stuff as soon as possible, you're welcome to use the Dev Version, as long as you understand it as something that is being worked on 😉
Unless otherwise stated in the App or Readme, the Term 'Aircraft Profile' referrs to the Profiles configurable within the App. So that has nothing to do with the Aircraft Profiles GSX will use.
Aircraft Profiles are an essential Part of the App, basically the Glue bringing everything together: they determine what Any2GSX Features (GSX Automation, Volume Control, PilotsDeck Integration) should be active for a specific Aircraft and which Aircraft Plugin and/or Audio Channel should be loaded for that. All Automation Settings found in the 'Automation' View are stored per Profile - so together with the Ability to filter on specific IDs, Airlines or Titles/Liveries you can have different Settings for different Airlines having different SOPs to follow (or just having different Operator Preferences for different Airlines).
Within the App, Automation referrs to all Options which either call GSX Services automatically or answer GSX Questions/Pop-Ups automatically. Which is NOT Integration: that is understood as the Aircraft and its Systems responding/reacting to GSX Services as they get active (who or what ever called these Services) - so typically Fuel-, Payload- and Ground-Equipment-Sync.
Any2GSX differentiates between what is an Automation and what is Integration. So even with the GSX Automation completely turned off for an Aircraft Profile, the configured Aircraft Plugin will still provide Integration like Fuel- and Payload-Sync. AND Ground-Equipment-Sync: so Equipment like Chocks, GPU, PCA is still automatically placed or removed! (Since that is an Response/Reaction to the GSX Pushback Service - see the Definition above).
In any Case, the Automation works in different Phases reflecting the general Flight State so that the App calls the appropiate Services. For Example calling the Departure Services (Refuel, Catering, Boarding, ...) in the Departure Phase or calling Pushback in the Pushback Phase. The Sequence is: SessionStart -> Preparation -> Departure -> Pushback -> Taxi-Out -> Flight -> Taxi-In -> Arrival -> Turnarond -> Departure. The App can also be (re)started in Flight, where it will directly switch from SessionStart to Flight (and then continue normally).
The Volume Control Features allows to map specific Apps to Audio Channels in the Cockpit (e.g. the App 'vPilot' on Channel 'VHF1'). When that Channel's Volume is manipulated in the virtual Cockpit (e.g. turning the VHF1 Knob), the Volume of the App will be set accordingly.
It is mostly the same Code as in Any2GSX and works the same Way, with on big Difference: For that Feature to work in Any2GSX, you will need an Audio Channel Definition File providing the necessary Information of the Aircraft Controls. It basically tells the App what Channels there are and how they can be read.
These Audio Channel Files are Textfiles containing the Definition in a JSON Notation. So it is relatively easy to extent the App for a specific Aircraft with good Text-Editor (Notepad++, VSCode). The Intention is a bit like GSX' Aircraft or Airport Profiles: knowledgable Users can create these Channel Definitions and can then share that with others. Any2GSX' Plugin-Repository can also provide the Channel Definitions in a central Place - so if you have created a Definition and want to share it centrally, just get in Touch with me / open an Issue/PR in the Plugin-Repo to get it added! 👍
Note that the whole Volume Control Feature runs completely separate from everything else. So even if you don't use/own GSX at all, you can still use Any2GSX to control the Volume of Apps!
Any2GSX can Integrate with my StreamDeck Plugin PilotsDeck (so you need that Plugin on your StreamDeck in order to use this Feature). This Integration serves as an Replacement for the Functionality provided by the GSX Script shared with my PilotsDeck Profiles.
When the Integration is enabled, Any2GSX will send Data to the Plugin which then can be used by the Plugin's Actions to display Data like the current Flight-Phase, current SmartButton Action, De/Boarding Progress and the whole GSX Menu (color-coded by Service-State while at the Gate).
So basically you can use your StreamDeck as a complete Replacement for the in-Game GSX Menu and to interface with Any2GSX' Automation. A premade GSX Pro Profile is available on the PilotsDeck Repository.
The SmartButton is a Way to send a Signal to the App that it should call/trigger the next 'Action'. For Example to call the next GSX Service (i.e. call Boarding while Refuel is still active), call Pushback or confirm a good Engine-Start to GSX. For Any2GSX Users: it is the INT/RAD Switch Feature in a generalized Form.
A SmartButton Request can be send via different Ways:
- Aircraft Plugins can map it to actual Cockpit Controls for an 'out of Box' Experience
- When the generic Aircraft Plugin is used, the User can define a SimVar and Comparison for a manual Mapping to a Cockpit Control
- In any Case, it will always monitor the Variable
L:ANY2GSX_SMARTBUTTON_REQfor Changes for generic Mapping in external App (e.g. like PilotsDeck)
Any2GSX does have its own Plugin System to enable Integration with specific Aircrafts - for Example to provide Fuel-, Payload- and Ground-Equipment-Sync. The Intention is that other People can also write Plugins to extent the App for additional Aircrafts. If a Plugin is needed at all: Airplanes with a proper (independent) GSX Integration (like FBW) don't need that.
Plugins can be directly installed in the UI either from the central Plugin-Repository or from a Zip-File when shared externally. As with the Audio Channels: if you created a Plugin and want it to be shared centrally, please get in Touch! 😉
When no Plugin is available (or needed), the App has a builtin 'generic' Plugin with the Ability to configure/map SimVars to the most basic but essential Aircraft Data (like Avionics powered, Power connected, Nav Lights on, etc).
Any2GSX has two Plugin Types using different Languages and Approaches: Either as Lua-Script only requiring a (good) Texteditor or as Binary/DLL written in C# requiring a full-blown IDE like Visual Studio. Lua-Plugins are quite powerful, in that they allow Access to all Sim Ressources (i.e. Variables, Events) and provide Access to the Plugin Interfaces - so they can mostly do the same as a Binary Plugin. The Binary Plugins are mostly for Cases where somekind of special Resource (PMDG's SimConnect CDAs) or external Resource (REST-API Call, Memory-mapped File) needs to be interfaced for an Integration with the Aircraft Systems.
For MSFS 2024, Any2GSX will install an App into the Simulators EFB providing:
- Basic State Information for Any2GSX: Flight-Phase and Status, De/Boarding Progress, loaded Aircraft Profile, current SmartButton Action
- Another Way to toggle a SmartButton Requests
- Alternative Frontend for GSX Menu Interaction
For MSFS 2024 it is recommended to use the EFB App to answer GSX Questions manually.
Any2GSX has its own (WASM) Module that needs to be installed into the Sim. The App cannot run without that Module installed!
As the Name suggests it provides the App Access to Simulator's CommBus API providing an additional Way to interface with Aircrafts.
- It is recommended (but not required) to enter your SimBrief Username and have Ignore Time checked to have correct Information on the VDGS Displays.
- For Automated staircases semi-automatic (half-checked) is recommended - but it should work with all Modes.
- It is not recommended to use the Always ask for pushback Option - use Any2GSX to Answer the Question with Yes, No (default) or answer it manually
- The De-/Boarding Speed of Passengers is dependent on the Passenger Density Setting (GSX In-Game Menu -> GSX Settings -> Timings). Higher Density => faster De/Boarding (But "Extreme" can be to extreme in some Cases).
- Ensure the other two Settings under Timings are on their Default (15s, 1x).
- As with GSX itself, Any2GSX runs best when you have a proper Airport Profile installed!
- Up to everyone's Preference, but disabling the Aural Cues (GSX In-Game Menu -> GSX Settings -> Audio) and setting Message verbosity to "only Important" (GSX In-Game Menu -> GSX Settings -> Simulation) can improve Immersion! 😉
The Configuration is done through the GUI, open it by clicking on the System-Tray/Notification-Icon. All Settings have Tooltips explaining them further. It is recommended to familiarize yourself with the Settings and the general Usage (see Section 3) first before starting the first 'serious' Flight with the App!
The first Time you start the App (or the Config was Reset) it will automatically open the GUI and the 'App Settings' View - please enter your SimBrief User (Name and ID both accepted) for the App to work properly!
After this intial Step you might want to check out the 'Plugins' View to check-out which Aircraft Plugins, Channel Definitions or Aircraft Profiles are available to download (see Section 2.3.4 for Details).
Since Any2GSX can be used with all Aircrafts, I'd recommend to check out the 'Aircraft Profiles' View next to configure if and how it should be active for a specific Aircraft. Check Section 2.3.3 for Details.
Configure when Doors, Jetway and Stairs are operated - for Example if Jetway/Stairs should be connected on Session Start and when they should be removed.
The Jetway & Stair Options apply to all Aircrafts, but the Door-Handling Options only apply to Aircraft-Plugins having their own Door-Sync-Code and have implemented these Settings!
Mostly the Min/Max Values for the Chock and Final LS Delays. The Chock Delay and remove Equipment on Beacon Options only apply to Aircraft Plugins implementing Chock-/Ground-Equip Handling!
The Final LS Delay applies to all Aircrafts. It's primarily a Timer which can trigger other Events when expired (like removing the Jetway, or starting Pushback with an attached Tug).
Options allowing to modify the OFP Data when imported - for Example to round up Fuel or randomize the Passenger Count. Note that these are only relevant when Any2GSX is providing Fuel- & Payload-Sync through an Aircraft Plugin!
In addtition the Delays used in the Turnaround Phase can be configured here, which control when Any2GSX will check again for a new OFP on SimBrief.
The Time Source used to compare against the Departure Time can also be configured here.
These Options allow to customize Fuel and Payload Handling like the Refuel Rate, Payload-Reset on Startup or FOB Save & Load.
So they are really Integration Settings, so they still apply when GSX Automation was turned of for the Aircraft Profile. In any Case: they only apply when Any2GSX is providing Fuel- & Payload-Sync through an Aircraft Plugin!
Configure if and when GSX Services are called:
- Reposition on Startup (either use Any2GSX for that or the GSX Setting - but not both!)
- The Service Activation and Constraints (if and when) as well as Order of the Departure Services (Refuel, Catering, Boarding as well as Lavatory & Water)
- If the Departure Services should already be called while Deboarding (in the Arrival Phase)
- If the last called Service should be cancled when using the SmartButton (to call the next Service)
- Calling Deboard on Arrival
- If and when Pushback should be called automatically
- If Departure Services should be canceled in the Pushback Phase
###### **Service Activation**
The Activation Column determines how the respective Service is handled and/or called by the App:
- Skip / Ignore: Service will neither be called nor monitored by the App
- Manual by User: Service will be called externally by the User or another App. BUT: it must be completed to end the Departure Phase
- Previous called: Service will directly be called after the previous Service was called
- Previous requested: Service will be called as soon as the previous Service is reported as 'requested' by GSX
- Previous active: Service will be called as soon as the previous Service is reported as 'active' by GSX
- Previous completed: Service will be called as soon as the previous Service is reported as 'completed' by GSX
- All completed: Service will only be called after all previous Service are reported as 'completed' by GSX
Note: The first Service will always be called directly (if not set to skipped or manual or having Constraints set), as it has no previous Service!
All other Columns allow to skip Services dynamically based on additional Constraints that can be set.
Activate at
Wait to call the Service until X Minutes (or lower) before Departure. A Value of 0 calls the Service without Delay.
The Service Activation still applies when the configured Minutes are reached. The INT/RAD Switch will override the Departure Time Check.
Note that the Time is only evaluated for the next Service in Queue - other Services further down will not be checked until they are next.
The SimBrief Departure Date/Time ('sched_out') is compared against the current Simulator Date/Time by default. The System (UTC) Time can also be used (=> Aircraft Options). But in any Case the current Time Source has to align with the Departure Time for this Constraint to work! I.e. if you change the Simulator Time away from Real-Time, use your System Time and ensure the SimBrief Departure Time is ahead of that.
Min. Flight Time
Skip the Service when the scheduled Block Time is equal or above the configured Minutes - i.e. only call Catering on 'longer' Flights, else skip it.
A Value of 0 ignores the Block Time.
Constraint Skip the Service in certain Situations:
- None: No Constraint applied, the Service is called normally (according to the other Options)
- Only Departure: The Service is only called on the first Departure (resetted by App Restart or new Session)
- Only Turn: The Service is only called on Turn Arounds (resetted by App Restart or new Session)
- Only on Hub: The Service is only called when the Departure ICAO (as of SimBrief) has a Match in the Company Hub List
- Only on Non-Hub: The Service is only called when the Departure ICAO (as of SimBrief) has NO Match in the Company Hub List
- Turn on Hub: The Service is only called on Turn Arounds when the Arrival ICAO (as of SimBrief) has a Match in the Company Hub List
- Turn on Non-Hub: The Service is only called on Turn Arounds when the Arrival ICAO (as of SimBrief) has NO Match in the Company Hub List
Call on Cargo
When checked, the Service will also be called on Cargo Aircrafts (as identified by Profile/Plugin), otherwise it is skipped.
Max Run Time The maximum Time the Service is allowed to run before it is canceled (gracefully). A Value of 0 means no Limitation.
Enable or Disable the automatic Operator Selection. You can also define Preferences to control which Operator is picked by Any2GSX! If no preferred Operator is found, it will use the 'GSX Choice' in the Menu.
The Preferred Operator List Operator List works only on the Name of the Operator as seen in the GSX Menu!
The Strings you add to the Preferred Operator List will be used in a (case insensitive) Substring-Search - so does Name listed in the Menu contains that Text. The List is evaluated from Top to Bottom - so the higher of two available Operator is choosen.
Manage a List of Airport ICAO Codes which define "Company Hubs" for this Aircraft Profile. 1 to 4 Letters per Code.
The Codes are matched in the Order of the List, from Top to Bottom. For each Code, the Departure ICAO is matched if it starts (!) with the Code - so whole Regions can be matched.
If the current Departure Airport is matched, Departure Services with the "Only on Hub" Constraint can be called (otherwise they are skipped). Consequently, Services with the "Only on Non-Hub" Constraint, will only be called if the Airport is not matched.
Not that these Hubs have nothing to do with the Operator Selection!
All Options related to skip / automatically Answer certain GSX Questions or Sim Interactions: Crew Question, Tug Question, Follow-Me Question, skipping Walkaround and reopen the Pushback Menu automatically.
Also the GSX Menu Action triggered from the 'ClearGate' SmartButton Call can be customized (so the Menu after picking the Gate while taxiing to it): per Default it is mapped to select the Option to remove AI Aircrafts from the Gate. But that can also be changed to call the Follow-Me on purpose or even warp to the Gate.
Aircraft Plugins can provide their own Options which are very specific to the Aircraft (e.g. Cargo Lights, Cargo Model/Visual used). If the Plugin has such Options, they can be found in this Category.
For Aircraft Profiles using the 'generic' Plugin, the Options to define basic Aircraft Data/Information is also located in this Category. For Example Options to map the SmartButton to a Cockpit Control, define an additional Trigger for the Departure Phase and most importantly Variables providing Aircraft Power & Light States. The Later are essential for the App's Phase and Automation Flow:
- Avionics powered: Signaling if the essential Aircraft Systems are powered - so typically always true once the Aircraft was woke up from Cold & Dark. Used to determine when Volume Control should become active and is also used for evaluating if the Aircraft is ready for Departure Services.
- External Power available & connected: Signaling if Ground Power is available and when it is connected. The connected State is also used to evaluate if the Aircraft is ready for Departure Services.
- Beacon & Nav Lights: Signaling when the Lights are on (like actually on, not just the Switch Position). The Nav Lights are used for the ready-for-Departure Evaluation and the Beacon (depending on Configuration) to trigger the Pushback Call.
- Parking Brake: Signaling when the Parking Brake is set. Essential Check used in various Phases.
For each of these Variables a Name and a Unit has to be provided (L-Vars have to be prefixed with L:). If in Doubt, use the Unit Number. All Variable used must evaluate to true/non-zero to indicate the on/connected/available State!
Any2GSX will only start to control Volume once the Plane's Avionics are powered. Once the Aircraft is powered, Any2GSX will set each Audio-Channel to the configured Startup State (e.g. 100% Volume and unmuted for VHF1). To customize the Startup State, select the appropiate Channel and set the Volume and Mute State that should be set.
When the Sim Session has ended or Any2GSX is closed, it will try to reset all Audio Sessions of the controlled Applications to their last known State (before it started controlling the Volume). That might not work on Applications which reset their Audio Sessions at the same Time (like GSX). So GSX can stay muted when switching to another Plane (if it was muted) - keep that in Mind.
Any2GSX will control all Audio Sessions on all Devices for a configured Application by default. You can change the Configuration to limit the Volume Control to a certain Device per Application - but on that Device it will still control all Sessions at once.
By default, Any2GSX will only consider App Audio Sessions which are flagged as active. Some Apps (like MSFS2024) can spawn inactive Sessions which become active later or by Demand. In that Cases 'Only active' has to be unchecked to also include inactive Sessions.
You can map freely Applications to any of the Aircraft's Channels - as defined by the selected Audio Channel in the loaded Aircraft Profile. All Mappings are associated to the Aircraft Profile so they are also automatically loaded when the Session starts.
To identify an Application you need to enter it's Binary Name without .exe Extension. The UI will present a List of matching (running!) Applications to your Input to ease Selection. The Use Mute Checkbox determines if the pulling or pushing the Volume Knob is used as Trigger to unmute or mute the Application.
Some Audio Devices act 'strangely' or throw Exceptions when being scanned by Any2GSX for Audio-Sessions. If you have such a Device, you can add it to the Blacklist so that Any2GSX ignores it (normally it should automatically add Devices throwing Exceptions).
But there also Cases where Input (Capture) Devices are reported as Output (Render) Devices which leads to Any2GSX controlling the Volume of your Microphone! In such Cases these "false-output" also need to be added to the Blacklist.
Matching is done on the Start of the Device Name, but it is recommended to use the exact Device Name for blacklisting. Tip: when you hit Ctrl+C on the Device Dropdown (under App Mappings), the selected Device's Name is automatically pasted to Blacklist Input Field.
Aircraft Profiles (again, nothing to do with GSX' Aircraft Profiles) play an essential Role when using Any2GSX. These Profiles allow to have different Automation Settings and Volume Control Mappings for different Aircrafts. Generally, the Profiles define if and which Any2GSX Feature should be active for a given Aircraft (GSX Automation, Volume Control or PilotsDeck Integration). Per default none of these Features are active so the User has full Control of what is active when.
Besides defining the active Features, the Aircraft Profile also defines which Aircraft Plugin and Audio Channel (Definition) should be loaded for given Aircraft - i.e. to load the INI.A306 Plugin when the iniBuilds A300-600 Aircraft is active or load the FBW.A380 Audio Channel when the FlyByWire A380 is active. Typically when installing an Aircraft Plugin, the App/Plugin will create a default Profile for the associated Aircraft so that it just works "out of the Box".
To determine the Profile to load, Any2GSX uses a Matching System using different Data Sources yielding different Scores when a Match is found adding up to a total Score for each Profile. The App will evaluate all Profiles on Session Start and then will use the Profile with the highest overall Score. If no Profile had matched/scored anything, the App will use the default Profile. The following Data Sources can be used for Matching:
- Airline: Matching against the SimVar
ATC AIRLINE. Score: 1 - Title/Livery: Matching against the SimVar
TILE(2020) orLIVERY NAME(2024). Score: 2 - ATC ID: Matching against the SimVar
ATC ID. Score: 4 - SimObject: Matching against the SimObject Path (
AircraftLoadedSystemEvent). Score: 8
Each Profile can have multiple Profile Matches, each defining a String/Text that should be compared (equals, starts with, contains) against a Data Source. In general it is recommended to use SimObject to match the Aircraft and have at least one Profile just using that. Additional Profiles can then also match for a certain Airline or Airframe to have different Settings (i.e. Operator Preferences) for different Airlines.
The String/Text used in a Profile Match can contain multiple Strings at once, separated by a Pipe |. For Example searching the SimObject Path for inibuilds-aircraft-a306 or A300-600 can be written as inibuilds-aircraft-a306|A300-600. If more than one String does match, the resulting Score will still be the same (still 8 Points for the given Example). It could also be written with two different Profile Matches each containing only one String - but in such Scenarios (with multiple Matches), especially when matching against the SimObject Path, the Profile will have such an high total Score that no other Profile can reach. So only do so if that Effect is intended!
The Buttons on Top of the Profile List allow to:
Set the selected Profile as the active Profile (i.e. to setup your Profiles outside of the Sim / without needing to load the Aircraft).
/
To Import/Export the selected Profile to/from the Clipboard to share Profiles with others quickly.
Clone the selected Profile (making a Copy of it)
Delete the selected Profile
Note that each Profile's Name has to be unique. Trying to import a Profile with the same Name for Example will override the existing Profile. Also the 'default' Profile cannot be altered (except for the Any2GSX Features) or deleted - it is the Failback when nothing else can be matched!
The Plugins View will show all installed Aircraft Plugins & Audio Channels. It also allows to remove installed Plugins & Channels, but ensure the Plugin/Channel is not configured in any Aircraft Profile!
Plugins, Channels and Profiles available from the central Plugin-Repository will be displayed in the 'Available from GitHub' Section. The App will highlight installed Plugins/Channels which have an updated Version available. To update an already installed Plugin/Channel just hit 'Install ... from Repo' again.
Note that Plugins (as Profiles) can automatically install the appropiate Channel Definition (if available). For Example after installing the INI.A350 Plugin, the Audio Channels for the A350 are automatically installed too. Or when importing the FlyByWire A380 Profile from the Repo, the FBW.A380 Audio Channel is also installed.
Plugins can also provide customized GSX (!) Aircraft Profiles, in Cases where the internal GSX or Developer-provided Profiles don't work with Plugin. In such Cases, the App will ask if the Profiles should be installed (they are automatically placed in the relevant GSX Folder). Existing Profiles will be overridden! If Profiles should just be automatically installed without Question, select the Checkbox.
It is not required to install the GSX Aircraft Profiles provided by Plugins - they will/should typically report in their Description if something has to be changed in the GSX Aircraft Profiles. But in that Case, the User has to ensure the required/recommended Profile Settings are applied manually!
The 'App Settings' View will contain Options which apply to the whole Application & all Profiles. Options like the UI Unit used, SimBrief User, Restart GSX Options, used Ports for Communication or saved Fuel Values.
- UI Unit Source: Change what Source to check to automatically switch the Unit used in the UI. Per Default the Unit used in the SimBrief OFP is used, but the App can also switch to the Unit used by the Aircraft - if the Aircraft Plugin supports that!
- SimBrief User: Both the Username or numerical ID are accepted. A valid SimBrief User needs to be configured for the App to work correctly. No other OFP Sources are planned.
- FOB Reset Percent: When an Aircraft supports to save/load the FOB (and that is enabled in the Profile), this Percentage (of the total Fuel Capacity) is Part of the Calculation to find the default Value to (re)set the FOB if no saved FOB is found.
- Fuel Compare Variance: When the FOB is checked to be equal, this Value is the maximum Difference allowed. For Example for the FOB still be considered as planned although the APU already burned some of the planned Fuel.
- Restart GSX on Taxi-In: GSX will automatically be restarted once the Aircraft has touched down again and is below 30 Knots GS. Note that this a 'hard' Reset - the Couatl Binary is killed and then started again!
- Restart GSX on Startup: GSX will automatically be restarted on Startup when the Menu fails to open after several Attempts. Note that this a 'hard' Reset - the Couatl Binary is killed and then started again!
- CommBus Port: The TCP Port Range used by the App to receive Data from the WASM/JS Modules. The App will only use one Port, it will the use the first working Port in that Range. If the Port Range is already in Use or just doesn't work, change the it here.
- PilotsDeck URL: If the StreamDeck is not connected to the same PC or if the default PilotsDeck Port was changed, set the correct URL here for your Setup.
- Refresh Gate Menu for EFB: Automatically refreshes the GSX Gate Menu ('Activate Services at...') for the EFB App - so you always have the 'live' Menu there. Only needed if the PilotsDeck Integration isn't used (which also refreshes the Menu automatically).
- Saved Fuel Values: The FOB Values stored for each Airframe. If there are "invalid" Values (i.e. through Testing) you can delete them here.
This Section describes the general Flow of the App and Flight Phases it will go through (and when they change).
- The App will always start in this Phase - Regardless when it was started or restarted in between. So most typically when the Sim Session is started.
- It is recommended to already have the SimBrief OFP filed/generated before starting the Sim Session! (For the correct Aircraft-Type - Any2GSX does not do any Type-Checks!)
- Depending on the State of the Sim and Aircraft it can advance to different Phases from here in the following Order/Priority:
- Flight Phase if the Aircraft is not reported as being on the Ground.
- Pushback Phase if the Beacon Light is on (with the Engines not running) or GSX Pushback is active (the Push Status being greater 0).
- Taxi-Out Phase if the Engines (at least one) are already running.
- Pushback Phase if the Aircraft is already reported as ready for Departure Services and/or GSX Services are already requested - but with the Aircraft's total Weight being already greater or equal to the planned Ramp Value.
- Departure Phase if the Aircraft is already reported as ready for Departure Services and/or GSX Services are already requested and GSX being in the Gate Menu ('Activate Services at ...').
- Preparation Phase after the Aircraft Plugin reports connected, Walkaround was skipped (Sim is not in Avatar Mode) and GSX being in the Gate Menu.
- So most typically, the App will switch to the Preparation Phase after entering the Cockpit.
- If the App directly skips ahead, the SimBrief OFP is imported directly.
- For MSFS2020: Since there is no Walkaround Mode, the App automatically considers the Mode as skipped.
- When GSX is not in the Gate Menu due to Scenery/Airport Profile Issues, the App will remain in this State until the User moved the Aircraft to a valid Position.
- With all Automations enabled, the GSX Menu can be disabled (=Icon not white) to prevent Menu-Popups.
- Reposition is executed (if configured, default enabled).
- Ground-Equipment is placed (if available through the Aircraft Plugin).
- Jetway & Stairs are requested (if configured and if reported as available, default enabled).
- For Online-Network (VATSIM/IVAO) Scenarios, it might be better to disable the automatic Jetway/Stairs Request for Cases where the Position needs to be changed.
- Jetway/Stairs can then be manually triggered by the SmartButton once a valid Position was found.
- If the Aircraft is refueled on the Stair Side (as reported by the Plugin Setting), the Stairs will NOT be called as GSX does not allow Refuel & Stairs at the same Time.
- The App will set the Payload to empty and FOB to the default/last saved Amount (if supported by the Aircraft Plugin and if configured, default enabled).
- With no Aircraft Plugin or the Plugin not supporting that, ensure Payload and Fuel are reset manually (else Refuel or the whole Departure might be skipped).
- The App will then remain in this State until the Aircraft reports Ground-Equipment placed and ready for Departure Services:
- Ground-Equipment is considered as placed when External Power is reported as available and either Chocks are placed or Parking Brake is set.
- The Aircraft is considered as ready for Departure when the Avionics are powered, External Power is connected and Nav Lights are on.
- These Conditions apply to the generic Plugin, Aircraft specific Plugins can overwrite that to use the OFP Import in the EFB or FMS a ready for Departure Trigger (Plugins typically report that in their Description).
- For the generic Plugin, it is possible to configure an additional SimVar & Comparison to be used inn the ready for Departure Trigger.
- Once the Conditions are met the App will switch to the Departure Phase. When it switches the Phase it will import the SimBrief OFP itself and also triggers GSX to reimport the OFP.
- When one of the Departure Services (Refuel, Catering or Boarding) is requested manually/externally in this Phase, it will also advance the Departure Phase (and import the OFP, but not refresh GSX).
- If Jetway/Stairs are not connected, the App will try to connect them now (if configured, default enabled).
- The Departure Services are called as configured in [GSX Services]gsx-services).
- Use the SmartButton to manually call the next Service in the Queue (for Example to start Boarding while Refuel is still active).
- Per Default the App will answer all relevant Pop-Ups/Questions in this Phase (Operator, Crew Boarding, Tug Attachment).
- If the App is configured to allow manual Answers to these Questions, ensure that they are answered!
- There has to be an Answer, or else a proper Flow cannot be guaranteed.
- You can cancel running Services in the GSX Menu if needed - the App will handle that like the normal Completion (and eventually take corrective Measures for planned Fuel/Payload)
- If the Aircraft requires to call GSX Services on its own for its (not really) Integration to work, ensure the respective Services are set to manually.
- If manual Interaction is required depends on the Aircraft and/or Aircraft Plugin used. For Example:
- Starting the GSX 'Integration' of the Aircraft through EFB/FMS if it needs to call the Services by itself.
- For Aircrafts not having a Fuel-Sync, Refuel has to be started manually through EFB/FMS once the Fuel-Hose is connected.
- For Aircrafts not having a Payload-Sync, the Payload has to be manually applied through EFB/FMS.
- If the Aircraft has custom Doors and no native Door-Sync, the Doors need to be opened/closed manually for the GSX Services (Boarding, Catering).
- If the Aircraft is refueled on the Stair Side, the App will attempt to call the Stairs shortly before the Refuel Service (if configured, default enabled).
- Given the configurable Delay was sufficient, GSX can be tricked into having Refuel & Stairs active at the same Time.
- This can rarely cause GSX to crash! Any2GSX can recover from that, but if that happens too often (or should not happen at all), disable the 'Attempt to connect Stairs while Refuel ...' Option!
- Anytime during Departure, the App will remove PCA (if supported by the Aircraft Plugin) once the APU and APU Bleed (or equivalent Indication for 'AC is provided') is on.
- When all Departure Services are either completed or skipped, the App will and advance to the Pushback Phase. It also removes the Stairs then (if configured, default enabled but only for Jetway Stands).
- The App will skip the whole Departure Phase if the Aircraft reports Boarding completed but GSX Boarding wasn't called. In the default/generic Implemenation, Boarding Completed is signaled when the Aircraft is at or over the planned Ramp Weight.
- The App will also skip forward to the Pushback Phase if GSX Pushback Service should become active (not just requested) or Refuel/Boarding are reported as bypassed (typically happens when Pushback gets active).
- If no alternative Frontend (PilotsDeck Integration, EFB App) for the GSX Menu is used: enable the GSX Menu again (=Icon white)! (Latest before Pushback is called for being able to answer the De-Ice Question and select the Direction)
- When the App switches to the Pushback Phase, it will intiate the Final LS Delay/Countdown. Once the Delay expires:
- All open Doors are closed, if the Aircraft Plugin supports that (if configured, default enabled).
- Jetway and Stairs (if still connected) are removed (if configured, default enabled).
- Pushback is called when the Tug was already attached during Boarding (if configured, default enabled).
- All mentioned Ground-Equipment Interactions only apply to Aircraft Plugins supporting that, so if not supported, manual Interaction is required here!
- Once the Beacon is on, Brake is set and Power is disconnected the Ground-Equipment is removed (if configured, default enabled).
- If configured (default disabled) Pushback will be called in this Case.
- If configured (default disabled) the Ground-Equipment is gradually removed (i.e. GPU is removed once Power is disconnected)
- When the SmartButton is used in this Phase, it will remove the Ground-Equipment and call GSX' Pushback Service.
- Removal of Ground-Equipment is in all Cases not forced - it is removed when it is safe to remove (i.e. Power is disconnected, Brakes are set).
- The App will try to automatically reopen the Pushback Direction Menu if the GSX Menu should timeout (if configured, default enabled).
- Successive SmartButton Calls will also try to reopen the Pushback Direction Menu.
- Once the Direction is selected and Pushback is commenced, the GSX Menu can be disabled again. The SmartButton can be used to stop Pushback or confirm a good Engine Start.
- When Pushback is completely finished, the App will advance to the Taxi-Out Phase.
- It is fine to call Pushback on Taxi-Out Stands via SmartButton to remove the Ground-Equipment - as long as the Airport Profile is properly configured (Pushback is disabled, not just all Directions set to none).
- In any Case, the App monitors the Engine running State and uses that as final Failback to remove still present Ground-Equipment and will also advance to Taxi-Out once the Aircraft starts moving.
- If a De-Ice Pad is selected in that Phase, the PilotsDeck Integration/EFB App will display the parsed Pad Name for Reference.
- If a Pad was selected, the App will try to open/refresh the GSX Menu when ever the Aircraft is below 2 Knots GS and the Brake is set (to check if De-Ice can be called/started).
- Use the SmartButton to call/start De-Ice on the Pad.
- INOP 😉
- Once the Aircraft is report on Ground and is below 30 Knots GS, the App will switch to the Taxi-In Phase.
- It might work to preselect the Arrival Gate while Airbone, but that wasn't tested.
- If you try that, ensure you have not set the App Setting to restart GSX on Taxi-In!
- If configured (default disabled), the App will now (hard) reset GSX to ensure a working / non-stuck State.
- With all Automations enabled, the Gate-Selection is the only Time the GSX Menu needs to be enabled on the Arrival Airport.
- It is strongly recommended to select the Arrival Gate while Taxiing.
- The Operator Selection and Follow-Me Question are automatically answered (if configured, default enabled).
- The PilotsDeck Integration/EFB App will display the parsed Gate Name for Reference.
- When a Gate was selected, the SmartButton will trigger the 'ClearGate' Action (every time it is pressed).
- Per Default that is bound to the Menu Option to remove AI Aircrafts from that Gate.
- It can also be configured to actually call the Follow-Me, Show the Gate or directly warp to the Gate for Example.
- The App will advance to the Arrival Phase once the Engines are shutdown, Brake is set and Beacon is off.
- It will also skip forward to the Arrival Phase if GSX Deboarding Service should become requested/active.
- All mentioned Ground-Equipment Interactions only apply to Aircraft Plugins supporting that, so if not supported, manual Interaction is required here!
- Chocks are placed after the Chock Delay has expired.
- When Jetway/Stairs are connected, GPU (and PCA) will be placed.
- The App has a 60s Failback to place the GPU if Jetway/Stairs are not reported correctly by GSX.
- GSX Deboard is called (if configured, default enabled). If not called automatically, use the SmartButton to call it manually.
- If Deboard is not called, the App will connect Jetway/Stairs instead (if configured, default enabled).
- If manual Interaction is required depends on the Aircraft and/or Aircraft Plugin used. For Example:
- For Aircrafts not having a Payload-Sync, the Payload has to be manually removed through EFB/FMS.
- If the Aircraft has custom Doors and no native Door-Sync, the Doors need to be opened/closed manually for Deboarding.
- Once the Deboard Service is reported as completed, the App will advance to the Turn-Around Phase.
- If the Option is checked to Run Departure Services in this Phase:
- Wait for the Deboard Service to be really active (deboarding Pax, unloading Cargo) before publishing a new SimBrief OFP
- The App will use the same Timings as in the Turn-Around Phase to check for new OFP (see below) and it import it automatically
- A new OFP will only be imported if the Gate is connected (Jetway/Stairs) and the Plane signals Ready for Departure (depends on Profile/Plugin - default is Avionics powered & external Power connected & Nav Lights On)
- Once a new OFP Id is loaded, the Departure Services will be called as configured (except the next Service being Boarding). If the Services get directly active depends on GSX allowing certain Services to be run in parallel.
- The App will switch directly to the Departure Phase after Deboarding is completed
- The App will wait 90s (configurable) before checking SimBrief for a new (different) OFP ID. But only if the Aircraft is reported as ready for Departure Services and Jetway/Stairs are connected!
- After that initial Delay, the App will check SimBrief every 30s (configurable) for new OFP ID (with the same Constraints mentioned above).
- When a new OFP is detected it will be imported and the App will advance back to the Departure Phase again. (GSX is also refreshed so that the VDGS shows the new Flight-Number/-Info.
- The Turn-Around Phase can be cancelled anytime by pressing the SmartButton!
- The App will skip forward to the Departure Phase if one the Services is already running (Refuel, Catering, Boarding - GSX/VDGS is only refreshed if Boarding is not yet running).
- The App will skip forward to the Pushback Phase if the Pushback services is requested or active. (No GSX/VDGS Refresh either)
A short Overview of the possible SmartButton Actions:
- Preparation => Call Jetway/Stairs (when not configured to connect automatically and only if allowed)
- Departure => Call the next (valid) Service in the Queue (including Services set to 'Manual')
- Pushback
- Service not yet called => Remove Ground-Equipment and request Pushback
- Service called, Direction not selected => Reopen Direction Menu
- Pushback being commenced => Stop Pushback
- GSX waiting for Confirmation => Confirm Engine Start
- Taxi-Out => Start De-Ice if a Pad was selected and arrived at that Pad
- Taxi-In => Customizable 'ClearGate' Action - typically remove AI Aircrafts from the Gate
- Arrival => Call Deboard (when not configured to be called automatically)
- Turn-Around => Skip Turn-Around (go to Departure Phase again)
Note: the NOTAMs a copied directly from Any2GSX - they should hold true for Any2GSX too.
Any2GSX and Self-Loading Cargo (SLC) should work together: Based on User Reports, you need to disable 'Ground Crew' in SLC!
Generally you only want one Application to control the Service-Flow and Ground-Equipment.
It is strongly recommended to disable the Option Skip 'Ready to Fly'. Else it might happen that Any2GSX starts in the Flight State.
In order to enable/disable the GSX Menu-Entry and prevent the GSX Menu to open/pop-up when Any2GSX does the Service Calls, you need to open FlowPro and Scroll on the GSX Icon. Green means on, not-green means off.
NOTE: Please uninstall the Plugin Flow GSX Launcher: it is outdated since that Widget is already included since Flow Version 2023.30.4.13.
FS2Crew (Fenix Edition): You basically don't need any Ground- or Door-Handling Features of Fs2Crew. This is what another User recommends as Settings to let Any2GSX and FS2Crew work together (thanks for sharing):
If you deviate from that, that is fine, but don't bother me with Any2GSX is not working properly then - Generally you only want one Application to control the Service-Flow and Ground-Equipment 😜
Both Any2GSX and Fenix2GSX can be used together and also can run at the same Time. BUT do not let both do the same Stuff at the same Time! 😉
For Example, if you use Fenix2GSX for the GSX Automation and Volume Control, do not configure Any2GSX to handle Automation and/or Volume Control. With Any2GSX' default Settings, respectively how the default Aircraft Profile is configured out-of-the-box, there is no Issue of both being active at the same Time!
So it all comes down how Any2GSX' Aircraft Profiles are set up. If for Example the GSX Automation should be enabled per Default on all Aircraft and thus is enabled in the default Profile, a dedicated Profile for the Fenix needs to be created with Automation disabled.
If Fenix2GSX was only used in a 'hybrid' Scenario before, so only assisting/enhancing Fenix' native Automation/Integration, Any2GSX is indeed the Replacement for Fenix2GSX in these Use-Cases! In these Use-Cases Fenix2GSX can be removed and Any2GSX needs to be configured with an appropiate Aircraft Profile.
To summarize:
Fenix2GSX for Automation and Volume Control
- Do not enable GSX Automation or Volume Control in the default Profile -OR-
- Create a dedicated Profile (with a SimObject contains Match for 'FNX_3') for the Fenix with GSX Automation and Volume Control disabled
- You can use/install the 'Fenix - PilotsDeck only' Profile in the Plugins View as a Template and then just disable PilotsDeck Integration
Fenix2GSX for Automation and Volume Control & Any2GSX for PilotsDeck Integration
- Install the 'Fenix - PilotsDeck only' Profile in the Plugins View from the Plugin-Repository
Fenix native Automation (and Volume Control)
- Remove Fenix2GSX from your System (via the Installer)
- Install the 'Fenix - Native' Profile in the Plugins View from the Plugin-Repository
- If you want to use Fenix' native Volume Control, disable the Volume Control in this Any2GSX Profile
- Check/Restore the Fenix EFB GSX Settings to your Preference - but do not enable Auto Jetway Simulation.
- Only start loading the Aircraft in the EFB when being in the Departure Phase (Avionic Powered + External Power connected + Nav Lights on)
- Ensure you have fully read and understood the Readme 😉
- Ensure you have checked the Instructions below for common/known Issues
- Ensure your GSX Installation is working correctly - Any2GSX ain't gonna fix it!
- If you report an Issue because you are really really sure that Any2GSX is misbehaving: provide a meaningful Description of the Issue and attach the Log-File covering the Issue ('Log-Directory' in the Systray or
%appdata%\Any2GSX\log). If there are multiple Flights in one Log (it is one Log per Day for 3 Days), provide a rough Timestamp where/when to look. - If your Issue is related to Volume Control, it is strongly recommended to attach the AudioDebug.txt File from the Log Directory (=> 'Write Debug Info' Button in the 'Volume Control' View)
NOTE: It is my personal Decision to provide support or not. So if you don't put any Effort in reading the Readme or properly reporting your Issue, I won't put any Effort in doing any Support or even responding at all. You need to help me in order for me to help you! 😉
You can use the 'App Monitor' View of the UI to monitor the current State of Any2GSX:
- The Sim State Section reports on the Connection to MSFS - it should be all green and a Version and Aircraft should be reported.
- The GSX State Section reports the State of GSX and it Services. Any2GSX can only do as good as the Information provided by GSX!
- The App State Section reports most noteably reports the current App Phase, the current OFP Data, how many Departure Services are queued - besides the general State of its Services/Controllers.
- The Aircraft/Plugin State Section reports basic Information about the Aircraft. Use that to check if the configured SimVars reflect the correct State when configuring the generic Plugin Settings.
- The Message Log Section prints all informational (and above) Messages from the Log - it gives you a rough Idea what Any2GSX is doing.
NOTE: Although a Screenshot of the UI might be helpful in certain Situations, it is not enough to report an Issue! Always include the Log-File!
- It does not open a Window if you expect that. The GUI is only needed for Configuration and can be opened by clicking on the Icon in the SysTray / Notification Area (these Icons beside your Clock)
- Ensure you have rebooted your PC after .NET 8 was installed for the first Time
- Check if the .NET Runtimes are correctly installed by running the Command
dotnet --list-runtimes- it should show an Entry likeMicrosoft.WindowsDesktop.App(with Version 8.0.x). - Please just don't "run as Admin" because you think that is needed. You can try if that helps, but it should run just fine without that!
- Certain AV/Security Software might require setting an Exception
- Please just don't "run as Admin" because you think that is needed. You can try if that helps, but it should run just fine without that!
Check if the GSX Menu is working. If the GSX Menu does not work, Any2GSX will not even start its Service Flow. Consider using the App Setting to automatically (hard) reset GSX on Startup for such Scenarios.
If the GSX Menu is working, there might be a Problem with the reported Aircraft Data. Check if the SimVars reflect the correct States (i.e. Avionics powered, External available, External connected, Nav Lights).
- Can be caused by FlowPro - check the recommended [Settings]42---FlowPro).
There can be certain Situations where the Jetways stops responding. This an 100% Asobo-Problem: Any Application, including GSX, is then not able to call Jetways anymore via SimEvent ("TOGGLE_JETWAY"). When you are in such a Situation, you can try to call the Jetway via the ATC Menu - but that doesn't really fix the Situation.
This can be caused by too many SimObjects being spawned, check the Tips below to reduce the Object Count.
It is also likely that you have Issues with the SimConnect Interface (the API which both GSX and Any2GSX use) being overloaded by too many SimObjects (one of these Things Asobo is incapable or unwilling of fixing).
In most Cases this is caused by AI Aircraft or other Tools spawning SimObjects (e.g. Nool VDGS or even GSX itself). Reduce the Number of SimObjects and check if it works better then:
- Remove Microsoft Fireworks (see below)
- If only tried while connecting to an Online Network, try if it works in an Offline Session
- Disable Road and Boat Traffic in the MSFS Settings
- Disable Traffic in the MSFS Settings (Airport Vehicle / Ground Aircraft / Worker)
- Reduce the amount of AI Planes in your Tool's Settings
- External AI Tools might have the Option to spawn Ground Services for AI Aircraft (AIG-TC e.g.) - be sure to disable that!
- Disable AI Traffic all together - whether it be MSFS or an external Tool
- Disable "Ground Clutter" in GSX (FSDT Installer -> Config)
- Disable other Addons spawning SimObjects
Remove Microsoft Fireworks
- Go to the Content Manager
- Search for 'Fireworks'
- The "City Update 3: Texas" should be listed -> go do List View
- Remove the Package "Microsoft Fireworks"
Offline Installer
There have been also Cases where the GSX Installation was somehow "corrupted". You can try to run the Check in the FSDT Installer multiple Times or use the offline Installer (run a Check again after using that Installer). Else a complete fresh / clean Installation of GSX might be required.