Scripting Error Message in the Fly The Maddog X

[kmanning]

Hi,
I just ran the Live Update. Ever since running that update, I'm getting this message:

The addon <unknown> is causing the Couatl Scripting Engine to restart. Please run Live Update.
Do you want to open log to see error details?

I'm running the P3Dv4.5 flight simulator in Windows 10 Pro. The airport scenery I'm using is the Imagine KATL Atlanta Hartsfield and I'm flying the MaddogX MD-82 and parked at gate C41. I ran this exact same scenery last night and everything worked just fine. After running the Live Update, I ran the same scenery today at the exact same gate, C41. I clicked YES to run the log so that I could post it here but it won't open nor do anything. It seems to me I remember seeing a Log Folder and now it doesn't appear. Why is it that I'm all of a sudden having this issue? I haven't made any changes. Yes, I ran the Live Update again but it made no difference. Yes, I know that this was discussed but I still have not found the solution.

When I loaded the MaddogX MD-82 at another airport, it does the exact same thing. I've tried it at several airports and I get the error message the addon is causing the Couatl Scripting Engine to restart. I don't understand that. When it says "the addon," does that mean it's the MaddogX that's causing the problem? Why is that? How can my addon, the MaddogX, stop the scripting engine from running? It was doing just fine the night before I ran the update and I have not made any changes whatsoever. Anyway, I've tried another aircraft and there was no error message and everything worked fine. So, what is it about my addon, which is the MaddogX MD-82 that would cause the scripting engine to have to be restarted? When I  press CTRL and F12 to bring up the menu, nothing happens, apparently because the script engine is not running. I just don't understand why all of a sudden, I'm having problem with this, and that did not happen until I ran the Live Update. So, I'm confused as to what is causing the problem.

I finally found the log I was looking for. See the attachment below.

Ken.

[kmanning]

Is there anyone from support that will answer my post? I've been waiting since yesterday.

Ken.

[golfkung05]

Hi, I also got this issue as well in P3Dv4.5.

After I read the forum, I understood there might be an issue with the P3Dv4.5.

Here is my extract log from the report. Hope there will be a troubleshooting update very soon.

[kmanning]

Hi, I also got this issue as well in P3Dv4.5.

After I read the forum, I understood there might be an issue with the P3Dv4.5.

Here is my extract log from the report. Hope there will be a troubleshooting update very soon.

Hi golfkung05,

Are you saying that the problem is with P3Dv4? I don't know if that's true. Will you post the link to that. Everything was working fine until I ran the Live Update. When the message popped up that the unknown addon was restarting the script engine and if I wanted to open a log, I clicked YES but nothings happens nor did a log open. There's also something here that I don't understand. I've noticed that the log you posted here says Couatl.err.txt. But the only one I see is the diagnostic log called Couatl.log, and there is no Couatl.err log. The Couatl.log is the one I've posted, and it's much longer than the Couatl.err log you've posted. Where do I find the Couatl.err log? According to the GSX Options under Troubleshooting, it's found in C:\Users\Admin\AppData\Roaming\Virtuali\Couatl.err. But there is no file nor folder named Couatl.err.

Ken.

[gabo_13_13]

Same here, I can't use any maddog model of the family since the last update, I'm sharing the coualt.err here, of course as .txt, .err isn't accepted to upload.

couatl v4.8 (build 5335)
panic log started on Fri Apr  5 21:22:19 2024

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\__init__.py", line 1269, in checkAirplane
  File ".\common\aircraftDb.py", line 185, in cockpitDoorOpen
ValueError: invalid literal for int() with base 10: '1.'
{'Airport': 'KVPS', 'User Pos': (30.49934154903158, -86.51128614051737, 29.4521 m, 2.93508 m, 192.17776871800461, 0.012711873278021812, 0.01448623277246952, -0.0002413608914714161, 2.9108400581359866, 1.0)}

[jmlucia]

Hi
I reported the same issue on April 2nd.
I use P3D v5.4.
http://www.fsdreamteam.com/forum/index.php/topic,31444.0.html

[kmanning]

Hi
I reported the same issue on April 2nd.
I use P3D v5.4.
http://www.fsdreamteam.com/forum/index.php/topic,31444.0.html

Has it been that long? My problem only started about 2 days ago after I ran the live update.

[kmanning]

Hi,

Will someone explain to me why I don't have a file called Couatl.err, which is much shorter than the Couatl.log. From what I understand, the Couatl.log is a diagnostic log, and it's much longer. The Couatl.err is a panic log that all of you have posted, and is much shorter. Why is it that I don't have a Couatl.err log? I only see a Couatl.log. I don't think they're the same because my log is much, much longer than the ones you all have posted and it's totally different. I want a copy of this panic log, or Couatl.err, so that I can view it. Am I doing something wrong, and where should the Couatl.err log be located?

Ken.

[jmlucia]

Hi.
I posted on April 2, which is when I realized the error after updating to the latest version of GSX (couatl v4.8 (build 5335). It didn't happen to me before.
I have the Couatl.err file in C:\Users\user\AppData\Roaming\Virtuali\ ("user" is your username).
When the error occurs and the scripting error window appears, the location of the file will appear in it.
It is posted as txt because err is not supported for attachment.

[jmlucia]

I will also tell you that I just did a scan for the Couatl.log file and it is the one that does not appear to me.
I know why: I didn't have it activated in the settings. There you will be able to see the locations of these files.

[kmanning]

I will also tell you that I just did a scan for the Couatl.log file and it is the one that does not appear to me.
I know why: I didn't have it activated in the settings. There you will be able to see the locations of these files.

Thanks for explaining that. I think I understand how it works now. There is a box in the Settings, and if that box is checked, you won't see the Couatl.err. You'll only see the Couatl.log. If you uncheck that box, you'll see both the Couatl.err and the Couatl.log. But you mentioned that it did not appear. It appears on mines.

Here's my Couatl.err log:

couatl v4.8 (build 5335)
panic log started on Sun Apr  7 15:00:45 2024

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\__init__.py", line 1269, in checkAirplane
  File ".\common\aircraftDb.py", line 185, in cockpitDoorOpen
ValueError: invalid literal for int() with base 10: '1.'
{'Airport': 'KATL', 'User Pos': (33.64227309629249, -84.43201012449715, 315.704 m, 2.98031 m, 269.78253253046313, 0.011725185438990593, 0.01448623277246952, -0.0, 2.9108400581359866, 1.0)}

Ken.

[kmanning]

By the way, how do we know when the fix is released? Will it be posted here, and if so, where?

Ken.

[moshwing]

I too experiencing the same issue when flying the Maddog 2.2b848. It only occurs with this plane, all others are running fine (Aerosoft A320/21 | PMDG 737NG/747/777 | 787 QualityWings)

Would love to know if we can revert back or have a temporary fix until next updated, hopefully this will get resolved by then.

Thank

[moshwing]

I too experiencing the same issue when flying the Maddog 2.2b848. It only occurs with this plane, all others are running fine (Aerosoft A320/21 | PMDG 737NG/747/777 | 787 QualityWings)

Would love to know if we can revert back or have a temporary fix until next updated, hopefully this will get resolved by then.

Thank

Update: I've completely uninstalled GSX and ran the most recent installer from fsdreamteam main page together with the updates (usually runs right after installation is complete).
After testing I no longer receive scripting errors.

Hope this helps,

Cheers,

Hope it works for you as well

[kmanning]

Update: I've completely uninstalled GSX and ran the most recent installer from fsdreamteam main page together with the updates (usually runs right after installation is complete).
After testing I no longer receive scripting errors.

Hope this helps,

Cheers,

Hope it works for you as well

I don't understand that. It's seems to me if that solves the problem, one of the support team members should have posted that here. At least, that is their job. Here's what irritates me. Not one support team member has offered to answer the questions posted here as to what is causing the problem and when the problem will be fixed. Not one person. We're just out here in the dark discussing this issue and I'm very irritated that the support team just ignores our questions and won't tell us what's happening.

Ken.