FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: b777futurepilot on May 25, 2015, 11:59:48 pm
-
Hi all, I am having an issue with GSX in P3D v2.5 right now. I have been using GSX for over a month now, in P3D, and I have had no issue except now I virtually cannot use it anymore. When I press Ctrl+12 to bring up the start menu, same process, I pick deboarding etc. The trucks load, everything goes well until, it says this... (whatever is in the picture attached). I am guessing I get this error when usually GSX asks you to open a specific door, I don't know. Anyways, need a little help! Also, I have reinstalled GSX and have updated the addon manager for the latest one.
Also, this may help. I looked at the Couatl in Notepad, and this is the error which is the same for each time I have tried loading GSX
OverflowError: long int too large to convert
(the whole paragraph)
couatl v2.0 (build 2378)
panic log started on Mon May 25 12:37:02 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 291, in run
File "couatl/common/simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
Every Message (paragraph) is the same disregarding the times accessed. So this is the problem, I guess, but how do ai fix it?
-
You have omitted the most important information, which is what airplane you use, and if you made or edited a configuration file for it, or you are using the stock configuration that comes with GSX.
If you use a default airplane or a 3rd party airplane that is supported internally by GSX, try to use the "Reset" option in the Airplane configuration editor in GSX, to restore the configuration that comes with GSX.
If you use an unsupported airplane that you configured yourself, it's likely there's an error in your configuration file so you might use the Reset option anyway, and redo it from scratch. Or, you might want to post your GSX.CFG file for that airplane, so I can have a look at it.
-
I use the PMDG 777 in this case, but I also have the Aerosoft A320, and GSX does not work with that either, but I will post the .cfg files soon!
-
Okay I just reset the configurator, didn't work. But the cfg. files, do you want the ones from the actual airplane I have, or are there cfg. files in a gsx folder?
-
But the cfg. files, do you want the ones from the actual airplane I have, or are there cfg. files in a gsx folder?
Both the Aerosoft A320 and the PMDG 777 are internally supported by GSX so, they are not supposed to have GSX.CFG files in the airplane folder.
If you put them yourself, maybe because you download them from some place, maybe made by some *before* we officially supported these airplanes, they might be the problem.
But, since the airplane folder is supposed to be a place where *developers* place a GSX.CFG file to be distributed with their airplane (we hope developers won't create wrong files...), the Reset option of the Airplane configuration will NOT remove them, on the assumption that, if you made a mistake editing a file and want to reset it, the Reset will not start from scratch, but from a configuration that should work, because is *supposed* to be provided by the airplane developer.
That's why, if you placed a wrong/corrupted/outdated GSX.CFG file in the airplane folder, the Reset option won't fix anything, because is not supposed to remove them, so you must remove them manually.
So, try again and be sure you don't have ANY GSX.CFG file in the airplane folder. Use the "Restart Couatl" option BEFORE trying again, after removing a file.
-
Hi I checked and I do not have any gsx.cfg files and the couatl still says:
OverflowError: long int too large to convert
-
Also I have already tried uninstalling gsx then installing it again, but it does the same thing, what should I do!!! ???
-
Also I have already tried uninstalling gsx then installing it again, but it does the same thing, what should I do!!! ???
Please indicate the gate used and the airport used. If the airport is not default, clearly indicate the scenery used and the AFCAD in use. You can check which AFCAD is used, by opening the scenery editing dialog with the "customize this parking position" option in GSX.
-
The last gate that I was at was Shanghai Pudong's Gate 116 Heavy
Afcad C:/Program Files (x86)/MyTraffic/Scenery/BR2_ZSPD.BGL
Yes, this was default.
-
The last gate that I was at was Shanghai Pudong's Gate 116 Heavy
Afcad C:/Program Files (x86)/MyTraffic/Scenery/BR2_ZSPD.BGL
Yes, this was default.
Could you please try using the default AFCAD ? It should be enough to temporarily rename the .BGL file to something like .BAK (with FSX CLOSED), and try again, being sure GSX is using the default AFCAD.
THis doesn't mean GSX won't work on a modified/3rd party ACAD. It's just to TEST if the problem IS the AFCAD.
-
I tried that and this is what happened. It said something like Error could not find file C:/ProgramFiles (x86)/Mytraffic/Scenery/BR2_ZSPD.BGL, is it ok that the scenery AFCAD is under MyTraffic.
Also, I don't know if this helps but when I landed at Toronto Pearson I thought I would try out GSX again. So I picked gate 181 Heavy, again. All the vehicles loaded, the marshaller even guided me in and told me to cut the engines etc. I pressed the deboarding action, the cargo loaders came up to the cargo doors, and the second that is is SUPPOSED to tell you to open the doors, it gives me that same error, long int too large to convert.
-
I tried that and this is what happened. It said something like Error could not find file C:/ProgramFiles (x86)/Mytraffic/Scenery/BR2_ZSPD.BGL, is it ok that the scenery AFCAD is under MyTraffic.
Assuming you renamed the .BGL when FSX was closed ( if it wasn't, that would surely explain the error ), try to force a complete scenery cache rebuild, by removing the following folders ( with FSX CLOSED!! )
c:\ProgramData\Virtuali\Couatl
c:\ProgramData\Microsoft\FSX\SceneryIndexes
Then try again.
-
I'm sorry, same thing happened again with the error.
-
I'm sorry, same thing happened again with the error.
As I've said in my previous message, you can check which AFCAD is used, by opening the scenery editing dialog with the "customize this parking position" option in GSX.
This to be sure that you removed the 3rd party AFCAD and GSX is in fact using the default one.
Also, you can try to install the latest Couatl 3 Public Beta, here, which has many fixes, and it will also tell you in the airplane configuration editor, which is the data source of the airplane customization.
http://www.fsdreamteam.com/forum/index.php/topic,11796.0.html
-
Ya it is still not working, same issue, I give up now. Thanks for the help! You were very patient!
-
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.
-
Would you mind telling me the exact path, I can't find the error when I checked the troubleshoothing in the settings.
-
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.
-
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
-
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.
-
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.
-
No, same problem, not an AFCAD problem.
-
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.
-
Here is the zipped file! Sorry it took so long, couldn't see my computer for weeks!!!
-
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.
-
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...