virtuali

With today's update, the Wingwing FCU is now compatible with DX12: I made a complete flight today with the Fenix, in DX12, zero issues.

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.