GSX Problem P3D v2.5

[virtuali]

Ya it is still not working, same issue, I give up now. Thanks for the help! You were very patient!

We don't want to "give up", because there are plenty of other troubleshooting steps that can be tried.

Enable Logging in the "Troubleshooting" section of the GSX Settings, than restart FSX, go to the same airport you tried before, let the error appear, and see if GSX created a Couatl.LOG file and eventually a Couatl.ERR file in your %APPDATA%\Virtuali folder. Send me both files, or at least the Couatl.LOG file, if no .ERR file has been created.

[b777futurepilot]

Would you mind telling me the exact path, I can't find the error when I checked the troubleshoothing in the settings.

[virtuali]

Would you mind telling me the exact path, I can't find the error when I checked the troubleshoothing in the settings.

The exact path depends on your system and user name. Which is why, I said to use THIS path:

%APPDATA%\Virtuali

Which it's always valid. Just type it on the any explorer windows or the start area, and press Enter, and the right folder will open. As I've said, you will surely have a Couatl.LOG file ( assuming you HAVE enabled Logging ), but you might have or not a Couatl.ERR file, and that's normal.

[b777futurepilot]

Ok it wouldn't let me attach an error file or a log file, so I am going to copy and paste what it says in each file here.

Loading airport EGPH from C:\Program Files (x86)\MyTraffic\Scenery\BR2_EGPH.BGL

[b777futurepilot]

And here is the Error File:

couatl v3.0 (build 3066)
panic log started on Mon Jun 01 22:09:19 2015

problem raised by addon <unknown>Traceback (most recent call last):
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
  File "couatl\common\simObjectMoverIK.py", line 305, in run
  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
  File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
  File "couatl\common\simObjectMoverIK.py", line 305, in run
  File "couatl\GSX\assistanceServices\__init__.py", line 1199, in waitWarningFunc
OverflowError: long int too large to convert

Here is the Error File.

[virtuali]

Ok it wouldn't let me attach an error file or a log file, so I am going to copy and paste what it says in each file here.

You can attach every kind of file, if you ZIP the two files together first.

Loading airport EGPH from C:\Program Files (x86)\MyTraffic\Scenery\BR2_EGPH.BGL

This lines indicates you are NOT using a default AFCAD. As I've said in my previous messages, in order to understand if the error is caused by the AFCAD, you must test with a default AFCAD first.

1) Exit from FSX

2) Remove the 3rd party AFCAD WITH FSX CLOSED

3) Restart FSX and be sure GSX is updating its cache.

4) Try again on the SAME airport you removed the 3rd party AFCAD.

[b777futurepilot]

No, same problem, not an AFCAD problem.

[virtuali]

No, same problem, not an AFCAD problem.

Send the new Couatl.LOG and Couatl.ERR files after the error, so we can verify again which AFCAD you used. ZIP both files together and attach the ZIP file.

Also, clearly indicates the gate where this is happening, on the default airport you said you enabled in place of the 3rd party one you still have enabled the last time you sent the LOG file.

[b777futurepilot]

Here is the zipped file! Sorry it took so long, couldn't see my computer for weeks!!!

[b777futurepilot]

Problem solved!!! I called the guys over at Jetline Systems, and as he was going through my settings inside of p3d, the "timings" tab, for some reason the timings box was set to something like:
=====================================================================

Intervals between messages(s): 5000000000.0

=====================================================================
He changed it to:
=====================================================================
Intervals between messages(s): 30.0
=====================================================================
Anyways thanks for going over troubleshooting this issue!!!

     Sincerely,
         Joseph J.

[virtuali]

for some reason the timings box was set to something like:

Intervals between messages(s): 5000000000.0

Alright, that makes sense, you probably set it to a very high value, in order to get rid of the prompt to open doors, which by default repeats itself every 10 seconds. We'll probably need to a checks against unreasonably high values...