Halifax CYHZ

[chachey]

Problem with CYHZ

This is the error log:

couatl v2.0 (build 2290)
panic log started on Tue Feb 07 11:08:16 2012
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 306, in checkAirplane
TypeError: 'NoneType' object is unsubscriptable

couatl v2.0 (build 2290)
panic log started on Tue Feb 07 11:08:37 2012
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 403, in onSimStart
  File "couatl\GSX\__init__.py", line 354, in checkOnGroundState
  File "couatl\GSX\__init__.py", line 306, in checkAirplane
TypeError: 'NoneType' object is unsubscriptable

couatl v2.0 (build 2290)
panic log started on Tue Feb 07 11:08:54 2012
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 403, in onSimStart
  File "couatl\GSX\__init__.py", line 354, in checkOnGroundState
  File "couatl\GSX\__init__.py", line 306, in checkAirplane
TypeError: 'NoneType' object is unsubscriptable

couatl v2.0 (build 2290)
panic log started on Tue Feb 07 11:18:39 2012
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 306, in checkAirplane
TypeError: 'NoneType' object is unsubscriptable

couatl v2.0 (build 2290)
panic log started on Wed Feb 08 09:31:42 2012
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 306, in checkAirplane
TypeError: 'NoneType' object is unsubscriptable

And this is the error message I get when I try to load the airport:

The addon <unknown> is causing the Couatl Scripting Engine to restart.
Details can be found in C:/Users/Charles/AppData/Roaming/Virtuali/Couatl.e

Please download and install the latest Stand-Alone Addon Manager from http://www.fsdreamteam.com/sa-addon-manager.

I did this but it made no difference.

All my airports are FSX default, I have no payware or freeware airports.  I can go to CYQM, CYYT, CYYZ and from there using the Ctrl+F12 menu go to a demo airport, I chose KSFO.  All works as advertised and very impressive.  The only difference between CYHZ and the ones that work is that VoxAtc (which I use) has a utility included that updates runway numbers that have changed because of magnetic variation.  CYHZ has been updated by VoxAtc and that is the only difference that I know of between it and the airports that do work.  Also I have to add that VoxAtc uses the correct runway numbers in communications, but does not change the signs by the runways at the airport.  I hope this is a fixable problem because I would really like to use this software.
Thank you for your time,
Charles

[virtuali]

Which airplane you used ?

When the error happens, exactly, at a gate or anywhere in the airport ? I've just checked now with the default A321, and there's no such crash at CYHZ, both when calling GSX at a gate, or from the active runway.

[chachey]

Hi Umberto,

Thanks for the reply.  I used the iFly 736 and the default FSX 738.  The error occurs while the scenery is loading after pressing "Fly Now".  I don't get to the airport.

Regards,
Charles

[virtuali]

Tried to do exactly as you described, with the iFly 737-600 and also with the default 737-800, the airport loads fine and GSX works normally, and there are no errors of any kind in the "Fly Now" screen.

Are you sure you have all default scenery ?

[chachey]

Yes, but as I mentioned in the original post, VoxAtc has modified the runway numbers because the ones from the FSX AFCAD are no longer correct.  That is the only difference I can think off.

Regards,
Charles

[virtuali]

I don't think runway number should be a problem but, have you tried disabling that scenery ?

[chachey]

I wouldn't know how to do that as it was done by VoxAtc.

Regards,
Charles

[virtuali]

I wouldn't know how to do that as it was done by VoxAtc.

There must be its own area in the Scenery Library. Or maybe it installed .BGLs in one of the default folders, like Addon Scenery or Scenery\Global\Scenery.

You might use ADE or the FSX Airport Scanner to see which files are installed for any airport.

[chachey]

Hi Umberto,

Problem solved, I installed a freeware airport which has the updated runways (CYHZ) from Avsim, ran the VoxAtc indexer and runway update utility, reinstalled your Stand Alone addon Manager and bingo, no more problems at CYHZ.  The only thing I can see is it must have something to do with the way VoxAtc updates the runway numbers.  I'm a happy camper, thank's for your patience.

Regards,
Charles