Recent Posts

Pages: [1] 2 3 ... 10
1
GSX Support MSFS / FSDT Universal Installer Live Update question
« Last post by trisho0 on Today at 08:19:04 pm »
I have the MSFS2020, MSFS2024, P3Dv4 and P3Dv5 installed in the same PC machine. After updating the msfs2020 do I have to switch to msfs2024 and to repeat the update? Or the Live Update takes care of all sims at once?
Also, after Live Update is complete, is it recommended to restart the PC machine?

Patricio Valdes
2
GSX Support MSFS / Re: Aerosoft CRJ v2-seated pax?
« Last post by trisho0 on Today at 08:11:56 pm »
Every airplane with an internal cabin is an obvious candidate for the Seated passengers feature. We are working on other things first, and the A350 from iniBuilds will likely be the next airplane to get Seated passengers support, but surely the CRJ is interesting.
Hi Umberto, if every airplane with an internal cabin is candidate for the Seated passengers, then why the PMDG 777-300ER the pax disappeared right after pax seated?

Patricio Valdes
3
I have to manually start Couatl engine when I load MSFS 2024, so make sure you've actually opened that app, first, then GSX works fine.
4
GSX Support MSFS / GSX pro not loading in MSFS 2024, no icon in menu
« Last post by mirabeau on Today at 07:40:13 pm »
Since update to 3.4.4
GSX does not load into MSFS 2024

Removed and reinstalled many times, deleted everything in FSDT addon Manager, reinstalled and still does not load
checked MSFS 2024 exe.xml ( couatl64_boot.exe and Couatl64_MSFS2024.exe are there).

Please advise any solution
5
The Live Update app claims 3.4.4 is installed. Could this be lying to me? Offline Installer wants to install 3.4.3, which is not the newest version, so seems pointless. I've looked at the configs I have for the PMDG 737 and both doors are marked as uldcode = AUTO
It's getting it correct on the front cargo door, but not on the rear. I'm going to change the rear ones to BELT and see if that cures my problem. I'm just baffled how it's getting it wrong on the rear, but correct on the front
6
GSX Support MSFS / Re: GSX Pro not loading after new update
« Last post by Alti on Today at 01:55:51 pm »
Hi, run Updater today, since the PROBLEMS in MSFS20204
Here ist the Log:
couatl v5.0 (build 5621)
panic log started on Sat Apr  5 13:56:20 2025

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\__init__.py", line 590, in aircraftLoaded
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\aircraftData.py", line 2594, in getAircraftData
  File ".\common\aircraftData.py", line 1068, in __init__
  File ".\common\aircraftData.py", line 646, in _dataFromAircraftDb
  File ".\common\aircraftData.py", line 591, in _convertDbData
AttributeError: 'FlippedExit' object has no attribute 'width'
{'User Pos': (52.35877900005193, 13.504346277777865, 45.8968 m, 2.88983 m, 249.47250371798864, 0.003490658476948738, 0.003490658476948738, 0.0, 2.7736801162719726, 1.0)}

Run Updater again and again, did not help here!
7
GSX Support MSFS / Re: 3.4.4 Deletes iniBuilds A350 Aircraft Profile
« Last post by virtuali on Today at 12:25:21 pm »
2020 and 2024. Does it matter what simulator?

Of course it does, the airplane is located in completely different folders, both the airplane itself, and the

Quote
Looks like your CDN is failing you.

Not sure what you screenshot of your custom profiles folder has anything to do with this or how you relate it to a CDN issue. Your custom profile folder is not supposed to contain anything about a certain airplane UNLESS you start customizing it.

The iniBuilds A350 is internally supported by GSX AND it comes with its own profile in the airplane package, which means:

- It's normal you don't have anything about the A350 in the %APPDATA% folder, things will appear there only if you customize the airplane or download a profile shared by somebody. We never install *anything* there with our installer EXCEPT airport profiles for FSDT airports, nothing else.

- Even if your GSX was outdated, suggesting a possible CDN issue, in the worse case you would be missing the Internal profile, which sets up a few specific things which are not possible to set with a normal profile but, the airplane would WORK and would be IDENTIFIED thanks to the profile supplied by iniBuilds.

So, your screenshot seems to indicate as if the airplane was completely unknown, with no GSX profile, no developer-provided profile and no user-made profile, which is very strange.

Which is why, I asked the simulator, because I only checked 2024 and there it works, now you said you use both, I'll check 2020 too.

8
GSX Support MSFS / Re: GSX Pro Issues with Inibuild A350
« Last post by virtuali on Today at 12:17:53 pm »
It's not very clear when you see this problem. I can see the normal GSX parking menu just fine, the menu you are seeing there is the one after you complete a pushback.
9
UPDATE:.... I just updated it twice again just now and it looks like it's fixed. I will check again in the morning.

Of course it fixed itself, that what I keep trying to explain, for example here:

Quote
It's *possible* that, if you were the first one calling for that file in your area (same local node), it might require trying an update Check twice.
10
If users are updating to the latest version and not getting correct files, surely that is not their fault and an issue on your side?

And where, exactly, I ever said it's the "user's fault" ?

Quote
Maybe fix your constant issues with Cloudflare or look for another CDN?

Yes, because nobody uses Cloudflare...

Quote
Just one software developer to another, maybe ensure that all files have reached the CDN before allowing the end-user to be able to see the update. Just a suggestion.

And you think we don't do that ? Of course tests are being made before a new release, using a VPN, but it's not as if I can test each and every node individually. An example, a user in Melbourne didn't get the latest file. I checked with a VPN and tried all nodes in Australia (there are about 6-7 of them), and ALL of them had the latest file EXCEPT the Melbourne one!

The issue is, when I open a ticket to Cloudflare, by the time they reply (usually a couple of days), the node has already refreshed, so I have no evidence to supply to them to understand why some nodes refresh faster than others.
Pages: [1] 2 3 ... 10