virtuali

Hi, I received mine today, the hardware is very nice and once you update the firmware, setup it’s really plug-and-play: just keep the SimAppPro open, and it will automatically recognize either the Fenix A320, or the default Asobo A320. It doesn’t recognize iniBuilds A320 from Beta SU15, but I guess this is to be expected, since the airplane is not officially out yet. However, there’s seems to be a problem with DX12: if it’s enabled, it will make the sim crash in WWTFS.DLL, which seems to be part of the support software. No issues with DX11. In fact, checking the app folder, there’s a .dll for DX10 and one for DX11, suggesting the app doesn’t work in DX12. Can anybody who received it confirm this?

GSX doesn't have anything to do with it, it's a known MSFS bug which has been known since it came out, we reported it to Asobo in 2022 before GSX was even released, they confirmed it to be reproducible on their end, but it has never been fixed. https://devsupport.flightsimulator.com/t/some-longstanding-jetways-issues/4487

There aren't two installers/updates, the program is just one and it's the same .EXE that runs, just with a reduced interface when started from the Live Update icon. I guess that somebody might have been confused assuming we have "two installers", because there's a Couatl_Updater.exe and a Couatl_Updater2.exe, but that's just the system which allows the updater to "update itself", so the 1st .exe doesn't do anything other than checking online if there might be a new version of the 2nd part (and download it if there is one). The 2nd .exe is what does the actual work of updating the products. When started from the "Live Update" icon, the updater does only one thing: it updates all FSDT installed products and it automatically quits at the end. Nothing else. When started from the "FSDT Installer" icon, the updater shows its full interface which does many other things (install, activate, deactivate, read manual, read release notes), and will let you update selected products, or even just one so, you have more options, but it's the same, identical .exe that runs and, the "Update ALL" button is functionally identical to calling the program from the "Live Update" interface.

I also had this problem, and tried all the possible sensitivity and null zone settings suggested on Fenix site and other sites as well, but what REALLY fixed it for me, was calibrating the joystick (Thrustmaster TCA joystick + Honecomb Bravo throttles) from the Windows Control Panel. This solved the issue, even with the previous (before B2) version.

The airplane surely will do the same thing, since it hasn't been updated, so we don't know if it's not setting the passengers variable intentionally, or it was just an oversight. However, if you have the latest GSX update installed, it won't trust the airplane passenger variable if it's 0, and it will use Simbrief directly.

Boarding with the iniBuilds A320 works in general, but there a issue with it: Other iniBuilds sets a custom LVar to set their internal passenger number. GSX reads this, so the passenger number would be in sync even if you don't use Simbrief. This works for A300 and the A310 but, for some reason, in the A320 the variable is not set even if you specify a certain number of passengers in the EFB, so it stays to 0. This confused GSX a bit, because it assumed that, if the variable is there, it would be used, but in this case, it wasn't (remember, the airplane is still a BETA!), so GSX ended up setting a 0-passenger number IF Simbrief was used. We fixed this in today's update, 2.9.7 that, if an airplane sets a custom variable for the number of passengers, but it doesn't use it (so it's still 0), GSX won't use it and will instead either look on Simbrief or estimate the passengers based on Payload, as it normally does.

You should also remove all your old/sold devices from your Microsoft account.

Only for the VGDS, which are the only models GSX loads as soon as you enter an airport (if you use a profile that comes with GSX VGDS, of course), the other models are only loaded on demand and have only one version (in multiple LODs', of course) Which is why, if your airport profile comes with a lot of VGDS, you can save on the maximum number of objects, if you set the option in the profile to not create static VGDS so, instead of creating all the static ones + the animated one for the gate you are using, it will create ONLY the one for the gate you are using, and only after you select a gate. This of course means you won't see any VGDS which are not of your assigned parking spot, but (depending how many GSX VGDS an airport profile has defined), will reduce GSX contribution to reaching the maximum Simobject limit.

None of those screens you posted shows it asked to install the Xbox version: on Windows, the one and only version you can install is the PC version. You are being confused by the diagram of the Xbox controller, but that doesn't mean you are installing the Xbox version of the sim: it simply means that, IN CASE you'll connect an Xbox controller (which works just fine on a PC), those will be the button mappings, that's it. It went through all the initial setup screens, because for some reason you lost your settings.

Since the GSX passengers' voices are controlled by the cockpit door, while the Fenix airline announcements are controlled by the PA Volume, by closing the cockpit door and turning the PA Volume up, you'll achieve exactly that: you'll hear only the Fenix airline announcements.

In the most obvious and elegant way: by closing the airplane cockpit door, if it has one that can be opened and closed. Well, ok, I'm being a bit optimistic, because few of the airplanes that have one you can open/close are yet supported with this feature in GSX, since the feature is brand new, right now the ones where GSX recognizes an animated cockpit door are: - MS ATR-42/72 - Leonardo Maddog MD8x - Justflight BaE-146 - Fenix A320 - Inibuilds A300/310 - Justflight F-28 If you know of any airplanes that DO have a cockpit door that can be opened/closed, just name them, so we might add them to the list of supported ones.

They can't, there's no way to add anything on the Xbox if it's not on the MS Marketplace, no matter if it's paid or not.

If you read my previous replies, it explains exactly that: you caused this by using the Addon Lilnker instead of the GSX installer, which does the extra required steps when Unlinking or Relinking, including disabling/enabling the Couatl engine from autostarting with the sim.

We are still trying to understand if it's best to set Windows 8 Compatibility On or Off for the Couatl64_MSFS.EXE file. With all my tests, it's best to disable it, but in the previous update (when we set it as Disabled by default), many users said with Windows 8 Compatibility enabled, it was crashing in mid-flight, so we set it back on. Try setting it back to disabled, which we'll probably do automatically on the next update anyway, since now we have the auto-restarter app, it shouldn't matter if it crashes during flight.

Its web based; I don't see why it wouldn't work on MS Edge on Xbox.

And to completely close this issue, I'll reply to this too, saying there are several other MSFS addons (some of them fairly popular) which can't be disabled with the Addon Linker, either because there have nothing in the Community folders, or they have packages in the Community folder AND support software elsewhere exactly like GSX, so they require separate actions to be completely disabled. They are: FSUIPC7.exe: starts with the sim as long as it's active in the EXE.XML FSRealistic.exe: starts with the sim as long as it's active in the EXE.XML MSFS2020_AutoFPS.exe: starts with the sim as it's active in EXE.XML. MDClient.exe from Leonardo MD80s: starts with the sim even if you disable the airplane from the Community folder with the Addon Linker FenixBootstrapper.exe: starts with the sim even if you disable the airplane from the Community folder with the Addon Linker. Those are the ones I know of, I'm sure they might be others. So no, it's not correct saying you can use the Addon Linker to disable "all other MSFS Content", except GSX, as if GSX was unique. There are several others that also can't be fully disabled "just" with the Addon Linker.

There are use cases where you want to disable GSX at start: maybe you are planning one or many GA flights for a small airplane on bush airports: GSX won't be particularly useful there, so you might want to keep the sim leaner, start faster, then enable GSX again when it's time to use airliners. And that is precisely why we have a proper Unlink procedure in the FSDT installer to begin with, which performs steps that cannot possibly be known to a generic utility like the Addon Linker. I was just trying to explain WHY this message came out (which is not a "bug"), it was just because GSX was *partially* disabled, because the Addon Linker was used instead of the FSDT Installer.

If you would rather use the Addon Linker for everything, just suggest a new feature to it, to associate a certain entry in the EXE.XML to a package that will be disabled by it, so it would more or less mimic what the FSDT Installer does.

See my previous answer: if you disable GSX in the proper way, using the FSDT Installer, it does all the extra steps required to truly disable GSX.

Not surprising at all, and happens because you use the Addon Linker, instead of the official method in FSDT Installer: Uninstall and reply Yes to the first question (UNLINK) and No to the second question (Uninstall). By not using the FSDT installer, you are skipping several steps which are required to Disable/Enable GSX correctly, with the most important one being the removal of the Couatl entry from EXE.XML, which is the most important thing to do. By using the Addon Linker, you just remove the GSX packages which contains mostly vehicles and textures, but not the actual software, which will now work in an unpredictable way, since it starts, but with no objects/texture package in the sim, causing all sort of errors it for any reason (even accidental, or triggered by some 3rd party app that integrates with GSX) it *tried* to create objects the sim can't see anymore. That's why the Couatl engine must always be disabled together with the GSX packages in the Community folder, if only because it's no use starting the Couatl engine with no packages installed. The FSDT Installer removes/restores the entries in the EXE.XML as required when Unlinking/Relinking. Other extra operations which are performed when Relinking GSX with the FSDT Installer (which the Addon Linker will miss), are the automatic scan to Disable GSX Jetways on 3rd party airports, in case you installed NEW airports during the time GSX was Unlinked, or installing GSX profile for FSDT airports, in case you installed any new FSDT airport during the time GSX was Unlinked.

That's the 3rd probable reason for this to be happening having left the menu open from the last session, so the simulator reopened it for you, without having to press the Hotkey. A case which, again, would be prevented by simply following the suggested workflow.

Of course this is how it works, and I can only confirm my previous explanation is correct. When I've said, "from a previous session", it also means a new session long after you closed the sim because, the sim remembers which Toolbar icons were Enabled when you closed it, so if you start afresh, the sim, they will open automatically. So yes, it's yet another good reason to follow the workflow in the manual, which suggests closing the GSX Toolbar menu when you are done with GSX, usually before take-off. With another benefit: if the menu is closed, GSX won't do anything during the flight, not even periodically querying the Navdata to look for nearby airports in case you'd want to pre-select a gate in flight. Which will not only decrease traffic over Simconnect and reduce the risk that any problem with the Navdata might cause a crash in flight (of GSX, not the sim, which shouldn't be a problem anymore since we added an auto-restarter), but it will reduce the CPU occupation as well, by not having to make any unnecessary calls to Simconnect, when you indicated your will to pause using GSX for the time being, by closing the Toolbar menu.

The announcement doesn't come out for no reason. It comes because you either opened the GSX menu, or you left the GSX menu Active (icon white) from a previous session with GSX, and then pressed the GSX Hotkey when you were parked. Since you seem surprised by this, indicated you haven't opened the menu yourself, it might suggest you might have pressed the GSX hotkey instead. Is it possible the key assigned to GSX be is also assigned to some other function, so you called that function and the GSX menu (which you left Enabled from a previous session) opened? Preventing the menu to be opened by accident is another reason for the GSX manual to suggest this workflow, at Page 90, where the menu is explained: By following this method, since you'll Deactivate the GSX Menu when you don't need it anymore, the menu won't open accidentally if you don't need GSX at that time, even if you had a key conflict with something else. Because, as explained in the same chapter, when the menu icon is not Active (so it's darkened), GSX won't issue any notifications or pop-ups, and won't even respond to the Hotkey.

Avsim forum doesn't allow editing a post after a while so, I'm quoting it here, to clarify version 2.9.6 has been released officially now, no need for the Beta installer anymore, just run the normal FSDT Live Update to get all the latest files. I have been flying all day, making complete flights from start to end, and it seems very stable now. the new couatl64_boot.exe also logs what's happening in %APPDATA%\virtuali so, if you still have issues with it, you might want to report them on our forum or the GSX Channel on Discord, possibly with the log from the new app.

Just run the Offline installer on top of a normal installation. And don't do an update, otherwise you'll go back to the regular version.