Add me to the list of people who have experienced the error message listed in the thread's title. And it is completely reproducible, at least for me.
First, here are the contents of my error log after the error occurs...
couatl v3.1 (build 3577)
panic log started on Tue Jan 17 21:05:59 2017
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 73, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\__init__.py", line 858, in do
File "couatl\common\criticalsection.py", line 23, in _synchronized
File "couatl\GSX\assistanceServices\__init__.py", line 150, in requestVehicles
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 121, in setGate
AttributeError: 'NoneType' object has no attribute 'index'
{'Airport': 'LIMC', 'User Pos': (45.64467469114354, 8.724474918172357, 238.312 m, 4.53098 m, 348.99999027775186)}Here are some details about my system and how I stumbled on the error...
1. I am running FSX/Accel on 64-bit Windows 7 Pro. It is located in C:\FSX, and is started in windowed mode using Run as Administrator. UAC is off. AV and firewalls set to ignore FSX and associated programs.
2. The scenery I used is Download ID No. 189874 from AVSIM: "LIMC - Malpensa Intl Airport - Milan, Italy" written by Ray Smith and Craig Scott. The flight was to go to EGCC but I never got beyond fueling.
3. After loading the default Cessna 172 at Gate 108, I loaded an Aerosoft Airbus A320 CFM and set the parking brake.
4. The only other program that was running was the
Aerosoft Airbus X Fuel Planner.
5. I started the same way I start most flights.
· On the right-hand CDU, select the "Turn Around State" from the Aircraft State list. Then switch to the "Load and Fuel" page.
· On the Aerosoft Airbus X Fuel Planner utility, press the "Generate Loadsheet" button to transmit the data. In the CDU, press the "Init Worksheet" button to receive the data in the aircraft.
· To begin loading fuel, press the "Load Fuel" button in the CDU. The label changes from orange to flashing green to indicate fuel loading has started.
6. About 5 seconds after pressing the Load Fuel button the error window will appear. Its exact wording is the same as that shown in this thread's title.
7. After viewing the error log, you're asked if you want to restart Couatl? If you answer Yes, then an endless loop begins: Couatl restarts, the message that the airport cache has been loaded appears, then the message about the "addon <unknown> is causing the Couatl Scripting Engine to restart" appears again and the whole thing starts over.
8. Answer No to end the loop and the fuel loading proceeds normally. But all Couatl and GSX entries in the FSX Addon menu will have disappeared. Note that the GSX menu is not opened at any time during this startup process.
I investigated a bit more and discovered a few other things...
1. The fueling-related error occurs for any Aerosoft Airbus A320/321, including both CFM and IAE models. (I don't own the NEO or the A318/A319, but I would bet the error happens with them as well if they use the same fueling programming.)
2. The specific values on the loadsheet (pax count, cargo weight, and fuel amount) don't matter at all. If the steps described above are followed, the error occurs.
3. Checking the "Auto Load with Aircraft" box on the
Airbus X Fuel Planner doesn't matter. The error occurs when the Load Fuel button is pressed, as described above.
4. If the "Start Boarding" and/or "Load Cargo" buttons are pressed first, no error occurs. It's only after the "Load Fuel" button is pushed that the error occurs.
5. The error does
not occur if the "Load Instant" button (to instantaneously load fuel, pax, and cargo) is pressed. It only seems to happen when the refueling truck would be called, judging by what normally happens when no error is seen. That would be logical since the last part of the error log mentions
Vehicle a couple of times.
6. The fueling error occurs at every gate between 101 and 118 in the LIMC scenery I used. It has
not occurred at any of the other gates that I've checked, but I haven't checked all of them.
7. It isn't just the Aerosoft Airbuses that experience problems at gates 101 through 118. No matter what type of aircraft is used at those gates (PMDG B777, iFly 737/747, ConcordeX, etc.), when the GSX menu is opened it is the
wrong menu. Instead of the usual gate-related list (Deboarding, Catering, Fueling, etc.), the menu that appears is for arriving aircraft, with each runway and the various types of parking spots.
8. Obviously, I haven't experienced this problem at any gate at any other airport with any aircraft. Otherwise I would have posted sooner.
I hope this amount of detail helps nail down the cause of this particular error message. I'm no expert on how FSX and GSX programming work together, but I see two patterns in all of this:
- Some data for Gates 101 through 118 in this particular LIMC scenery is wrong or missing. That causes the wrong GSX menu to appear when ANY aircraft is sitting at any of those gates.
- The programming for the Aerosoft Airbus seems to need the incorrect or missing information to take care of "live" refueling. Without it, the error described by others appears.
I just happened to use the wrong aircraft at the wrong gate of the wrong airport, or I wouldn't have had any problems.
