Author Topic: The addon <unknown> is causing the Couatl Scripting Engine to restart.  (Read 1783 times)

swaor

  • Newbie
  • *
  • Posts: 18
So just today I encountered this error: http://prntscr.com/shdii2.
After which Couatl asks to be restarted and after doing so it will just enter a endless loop of crashing and wanting to restart.
Opening the error log, it contains the following:


couatl v3.2 (build 4334)
panic log started on Fri May 15 15:31:09 2020

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\modelCustomization.py", line 618, in setJetwayAirlineCode
  File ".\common\modelCustomization.py", line 662, in getModelForCouatlType
  File ".\common\modelCustomization.py", line 631, in getModelsForCouatlType
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\modelCustomization.py", line 461, in _cache
WindowsError: [Error 3] Das System kann den angegebenen Pfad nicht finden: ''
{'Airport': 'EDDM'}
reset FSDT_GSX_AIRCRAFT_SERVICE_1_TOGGLE to 0


Flight was as the error log says from EDDM, tested it with the FSLabs A319 as well as the default F22 and also tested it in EDDH, same problem.
I already tried the Live Updater but no luck.

swaor

  • Newbie
  • *
  • Posts: 18
Got it fixed in the meantime by completely re-installing GSX / L2.
Though it would be nice to know if anyone knows a solution other than re-installing for people having this problem in the future.
Cheers

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51238
    • VIRTUALI Sagl
Your problem was caused by:

- you not having run the FSDT Live Update, because your log shows you had an older version of Couatl.exe.

- the program couldn't find your custom texture folder or your own account folder, which is of course not normal, most likely a permission problem in your user account.

It's likely you fixed this with the installer, which reset correct file permission on your user folder. The program cannot automatically fix itself, in case you or some other program ( antivirus, for example ) changes file permissions on a folder you should always have permission to access to, only the installer can do that.