Problems after updating to GSX PRO version 3.1.4 **SOLVED in 3.1.5**

[Lawrence]

I have updated to the new GSX Pro version 3.1.4 and have noticed that when using the  TFDI MD11 in MSFS2000 almost any action that I request crashes the Couat. The only actions that are working seem to be the newly added features of lavatory and water service and the fuel request. Any other action like request stairs or jetway or boarding or request GPU are crashing the Couat.

Before this upgrade a few days back this was working absolutely fine. Not sure what this might be.

Thanks

[pete_auau]

just used  fenix  and  had  no issues,  have  you tried other  aircraft to see  if  you have  the  same  issues if  you dont  then it most likely  be  the  tfdi md 11  at fault

[katzzang]

After updating to the latest version 3.1.4, GSX cannot run and keeps prompting for an update. Even after completely uninstalling and reinstalling, it still prompts for an update. I hope you can resolve this as soon as possible.

[Concorde]

Same issue, with inibuilds a300

[steveduemila]

Hallo,
i have the same issue, after the update to 3.1.4 and after using also the offline addon manager as instructed by Umberto in his post.
Attached my log of the error.
Is there any workaround?
Thank you!

[Lbraendle80]

Same here with the Flybywire A320 :-(
I also tried the Fenix with the same error.

[steveduemila]

I found a solution: simply reinstall gsx.cfg file for the aircraft you use!
This solved all the problems for me, except the request of GPU (see the error in the log file attached).

[Lbraendle80]

Thanks Steve for the hint. Unfortunately it didn't work with the flybywire if i tried boarding.

Traceback (most recent call last):
  File ".\common\fsm.py", line 67, in switchToState
  File ".\GSX\assistanceServices\__init__.py", line 1114, in enter
AttributeError: 'NoneType' object has no attribute 'v'
{'Airport': 'LFPG', 'User Pos': (49.01645274348121, 2.5390555555557617, 107.87 m, 2.687 m, 191.8708122529706, 0.005417788955503713, 0.003490658476948738, 0.0004027879150115067, 2.7096721046447754, 1.0)}

[jd_jay]

Ive Just came here looking for some answers to this problem.  Using the Fenix 321 I get this error upon starting to load using the EFB and selecting GSX to load the aircraft.

If I use GSX for everything apart from the loading, ie jet bridge, pushback then I do not get any error.

[mwyatt]

Same issue at EGNJ (Humberside), Stand 3, Inbuilt A320, request Boarding crashes GSX, Request Water services is OK.
Any fix ??

[mwyatt]

Updating to 3.1.5 fixed the problem for me.
That was a quick fix, many thanks.

[alexberry]

Since updating to 3.1.4 and now 3.1.5, the couatl engine for MSFS won't load, preventing GSX from working.

No couatl.log file is generated.  Starting Couatl64_MSFS.exe generates the following error:

C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe

The file or directory is corrupted and unreadable.

I have uninstalled entirely and reinstalled but makes no odds.

Other possibly relevant information - made no changes to Antivirus setup.
MSFS with GSX last run on Thursday evening with no issues.  Updated to 3.1.4 this morning, and then to 3.1.5 later on before running MSFS.

Log files attached

[mleuck]

Same issue for me. I have updated to latest version, but cannot load. I have run the updater twice.

[alexberry]

Since updating to 3.1.4 and now 3.1.5, the couatl engine for MSFS won't load, preventing GSX from working.

No couatl.log file is generated.  Starting Couatl64_MSFS.exe generates the following error:

C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe

The file or directory is corrupted and unreadable.

I have uninstalled entirely and reinstalled but makes no odds.

Other possibly relevant information - made no changes to Antivirus setup.
MSFS with GSX last run on Thursday evening with no issues.  Updated to 3.1.4 this morning, and then to 3.1.5 later on before running MSFS.

Log files attached

A full uninstall of FSDT Universal Installer (Addon Manager) and reinstall appears to have resolved things

[mleuck]

Not for me. problem continues as GSX will not load and is unusable!