Because to question about “how do we update it ?” you replied with “with the FSDT Installer”, with a link pointing to the FSDT Universal Installer.
Hence my reply, since the FSDT Universal Installer is not used to update products, but to install the programs that would then allow to install/updated the products.
Thank you for the pushback tug option love it.
I use FSDT Universal Installer for updating, that gives me more information and control. I don’t use Live Update. I know all those things you wrote.
I have a question about starting the program in the simulator, for example with alt and F12. The menu doesn’t appear, just this rotating animation, nothing comes up for a long time, then I have to start it again, reload the situation and then it only appears under alt and F12 the menu, why is that?
I use FSDT Universal Installer for updating, that gives me more information and control. I don’t use Live Update. I know all those things you wrote.
Now I understand why you thought my reply to you wasn’t required, because it looks you are still confusing things a bit. I agree this partially our fault and we might have named the programs a bit better but, I’ll try to clarify again:
The FSDT Universal Installer is the thing that installs the FSDT Installer, which can in turn be used to install, manage and update the various FSDT products.
The FSDT Installer is what probably meant when you said it’s the one that gives you more control.
The FSDT Live Update is something just runs automatically and updates everything it finds automatically, with no user intervention.
Both the FSDT Installer and the FSDT Live Update are just shortcut icons that start the updater to work with different users interfaces, but they are the same .exe.
To compare with the very well known Steam app:
The FSDT Universal Installer does what the SteamSetup.exe does: it just installs the software in the system, if you don’t have it yet.
The FSDT Installer does what the Steam.exe app does: manages and updates products.
and am I right that the desktop shortcuts created are named differently than the exe files they run?
example: the “FSDT Installer” actually runs the “Couatl_Updater.exe” with some additional parameters, and on startup it says “Live Update”, and when the window opens it turns out to be the FSDT Universal Installer window.
That’s exactly what I’ve said before:
They are in fact exactly the same program (same .exe is being started) with two different user interfaces, the Installer interface give more options and control, the Updater interface just updates everything automatically and it’s functionally identical than using the “UPDATE ALL” button from the Installer interface.
I’ll try it to explain it as simple as possible:
The icon named “FSDT Installer” links Couatl_Updater.exe using the /INSTALLMODE=True parameter, so it will show the full Installer interface.
The icon named "FSDT Live Update " calls Couatl_Updater.exe with no parameters, so it will run automatically using the compact interface with no controls and will just update everything.
and when the window opens it turns out to be the FSDT Universal Installer window.
You are also confusing the FSDT Universal Installer with the FSDT Installer. The Universal Installer is the thing that installs the Installer, it’s not the installer/updater itself.
Re-read my Steam example, and it will all be clear to you.
ok then I must have something wrong on my end because this is what I see when I run the Live Installer:
Ill try a re-install, but I think maybe thats what caused the problems in the first place because I had to do a re-install not long ago and it caused some issues.
Nothing wrong, the icon starts the FSDT Installer, which is labeled FSDT Universal Installer (when it’s started with the full interface by the “Installer” icon) since, as a matter of fact, that what it is, in addition to be able to Update products as well. So no, you haven’t done anything wrong, it’s exactly as it’s supposed to be.
And yes, it’s also entirely normal (I understand it might be confusing) the Windows User Account Control page you show in one of your screenshot would call it “Live Update”, but that’s just a result the program .EXE is one and the same , ith two interfaces that will make it look very different just by changing the way it’s started.
However, what the Windows UAC is showing you, it’s the name in the Digital Signature and that can’t change “dynamically” as the program itself can, it’s absolutely immutable and fixed in the .exe ( that’s the whole point of a Digital Signature ), so you can be sure the program hasn’t been altered.
The point of my explanation to was that @mhron posted a link to the FSDT Universal Installer setup .EXE, to somebody asking how to update GSX, that’s what I’m trying to explain: that link will just install the FSDT Universal Installer, it’s not used to update the products it’s used only to install the program itself, and you usually run it only once, the first time you need to install anything from FSDT:
Anyone had a problem recently with GSX’s Couatl engine not exiting when shutting down the sim? It makes Steam thing the sim is still running. I’m on the latest 2.7.6 but it was doing it on 2.7.5 as well when I first noticed it. Seems to work fine, just no longer exiting correctly. I have to go into Task Manager every single time now and end Couatl from running. The sim is fully exited and not showing in Task Manager. No errors in Event Logs either in Windows.
I have a question about starting the program in the simulator, for example with alt and F12. The menu doesn’t appear, just this rotating animation, nothing comes up for a long time, then I have to start it again, reload the situation and then it only appears under alt and F12 the menu, why is that?
Doesn’t happen normally but, again, it would be best if you posted this in the FSDT support forum or the FSDT support email, because there are several things that can cause it, and this is not really the place for support.
Okay thanks!
Version 2.7.7 – October 2nd, 2023
GSX (all versions) FIX: Jitters in Pushback when exiting from Pushback QuickEdit.
GSX (all versions) FIX: Different freeze method for Towbar pushback, should fix jitters in any case.
GSX Pro Change: Couatl engine recompiled with SU13 SDK.
GSX (all versions) Change: Gates and Parking spots positions are now always listed before Runway Start positions in the GSX gate selection menu.
GSX Pro FIX: “Tasklet error” happening sometimes at start which required to restart the Couatl engine to continue.
GSX Pro Installer: Installing GSX Pro from scratch will download packages updated to 2.7.7 which will result in a faster install.
GSX Pro Installer: The lines starting the Couatl engine in the EXE.XML will be added also during an Update or Check, not just when Installing or Relinking.
GSX (all versions) NEW: GSX aural warnings are integrated in the standard GSX audio system, so they are affected by the volume in the Audio settings.
GSX (all versions) NEW: Added the following Handling operators: ViaGo (Finland), SGS (Saudi Arabia), Air Rarotonga (Cook Islands).
GSX (all versions) NEW: Added the following Catering operators: ViaGo and Finnair Catering (Finland), SGS (Saudi Arabia).
This new version (2.7.7) doesn’t seem to be working properly! The GSX objects don’t appear after landing at the destination airport and even when you park and select deboarding, it says that it is, but no objects are there! You have to reinstall GSX for things to work! Also, pushback with Fenix is a mess! Starts very good (no lifting off the ground) but when it stops and the pin is removed, the plane drops down big time as if it crashed! 2.7.6 was generally working fine! Not sure if I need to reinstall it or if others have the same issue!
Also, is it still normal that several objects including passengers can be in the air or a portion of them (passengers) under ground? I am sure this is a Sim issue but it would sure be nice if this is addressed in MSFS 2024!
Have the same problem with GSX objects not being active (even if GSX is working) at arrival airport. Restarts helps. But should be fixed.
(latest version 2.7.7, tried offline installer, followed by a live updater session)
You really need to install (or create) Airport profiles to make the most out of GSX. For a smooth operation, you have to download a GOOD profile for every airport you fly to, theres a specific category on flightsim.to:
https://de.flightsim.to/others/gsx-pro/
Otherwise, the issues you describe will happen on many airports.
Yes, i encountered the same issue. I had to restart couatl multiple times. Worked perfect with the version before, this one seems to be bugged.
The object not appearing at landing are a very well know problem that doesn’t have anything to do with GSX, it’s caused by having reached the maximum number of objects allowed in the sim (1000), it’s very well documented, and it happens more easily when you have highly detailed airport + lots of AI traffic + GSX, no single add-on is responsible for this, it’s a combination of all add-ons creating objects and, until the limit will be eventually raised, you must use whatever tools each add-on offers you to keep the number of objects under control.
On GSX side, these are the Passenger Density slider, the disabling of the Ground clutter option in the Config page (only effective at default airports which are the only ones were you are supposed to use GSX replacement jetways ) and the disabling of the Static VGDS in the Airport profile.
Pushback with the Fenix works much better now and doesn’t bump nearly as much as it did before.
Are you using the Fenix2GSX addon maybe ? We just had a discussion with the author that he had to do some changes to it, because the way the pushback changed in this version, so you might need to check if there’s an update to it.
If you still having issues with the Fenix, please don’t post them here, because this is not the place to get support for GSX. Post it to the FSDT support forum OR the GSX Creators channel on Discord, making complete report indicating all the following:
the airport used and if you had a profile, the custom profile in use
the gate used
the pushback direction you chose
if you are using the Fenix2Gsx add-on, which version
This is the proper way to have things investigated and issues fixed if they need to be.
