Products Support > GSX Support FSX/P3D

Scripting Error Message in the Fly The Maddog X

<< < (3/5) > >>

kmanning:

--- Quote from: jmlucia on April 07, 2024, 08:23:23 pm ---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.

--- End quote ---


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:

--- Quote from: moshwing on April 08, 2024, 04:44:52 am ---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

--- End quote ---

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:

--- Quote from: moshwing on April 08, 2024, 04:44:52 am ---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
--- End quote ---


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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page