Hi!

 

I have reinstalled my PC and reinstalled also my FS9 from my backup.

 

When I chech my airports and AI traffic I wonder what the hell? Not one of my AI aircraft

 

will land and taxi to gate on KJFK. I checked my AFCAD and it's OK.

 

So, what could possibly be wrong?

 

Anyone, any idea?

 

Grateful for any tip.

 

Thanks.

 

Hans Hermansson

Sweden

What is your traffic application, if any. How did you install FS from backup. Did you restore your FS9.cfg? Did you change the Win version?

 

Is it just kjfk giving you the ai problem?

 

If you just restored your FS9 folder without an FS9 install on the new system, you are probably missing some registry entries. To get the correct registry entry try this free repair utility from:

http://www.flight1.com/view.asp?page=library

In VISTA or Win 7 you will need to right click on the .exe and select a program access level of running as an admin, different from a user account level.

 

Can you take off from KJFK? Can you see ai on the ground?

 

You need to insure that the afcad you use is in the proper order in your scenery library and there are not any higher priority scenery conflicts. You also need to check that your scenery paths are current in the library. If there was a disk assignment change that could be a culprit with add-on scenery.

 

Find scenery.cfg in your FS9 folder. Mine is in "H:\Program Files\Microsoft Games\Flight Simulator 9\Scenery.CFG" . Make a safe copy of it, then examine it in wordpad and look at the paths. I have a JFK add-on and it looks like this in scenery.cfg:

 

[Area.209]

Title=FRF-KJFKv7

Layer=201

Active=TRUE

Required=FALSE

Local=..\..\..\CommonAddonScenery\FRF-KJFKv7

Remote=

 

Your layer number and area numbers will be different.

 

You need to insure that where you keep your KFJK afcad is in that file. Using afcad221 (just for viewing) if you open the desired layer for the afcad for KJFK and clilck file\properties you should get the full path.

 

traffic files are compiled originally from an airports list, aircfraft list, and schedule list. multiple traffic files are kept in folder scenery\world\scenery under your FS9 folder. traffic030528.bgl is the default FS9 traffic file. Many traffic apps replace that with a traffic.bgl file possibly with a unique file name.

 

Let us know how you make out. I can get into a free diagnostic for you to try that analyzes your scenery.cfg and checks priorities.

Hi again!

 

and thanks a lot for reply.

 

I forgot to mention that AI traffic works at KJFK; planes take off alright, but when they land they just

 

roll a bit down the runway and then just pop and vanish; all of them, not just some.

 

I checked my AFCAD and the traffic file and they seem alright.

 

But I'll try the repair gadget you recommend.

 

Again, thanks a lot!

 

Hans Hermansson

Sweden

The solution recommended in the later double post should work.

 

FYI: Disappearing landing ai means either no parking is available or there is no contiguous taxi path to an available parking spot of the minimum size for the aircraft.

 

FS is also known when you start running a flight ai within a certain time window play catch-up to their ai schedules. This means a heavy cluster of ai taxiing for departure and a few minutes later a cluster of ai arrivals.

 

There are two free utilities that can help:

 

In FSX utilities get aismooth version 1.2 aismooth_v120.zip. It works in FS9 as well. You can set the landing interval for ai on final and space them out according to your preferences. By spacing them out it helps with parking and also allows FS to interleave ai in the the take-off queue relieving ground congestion. When necessary aismooth places ai in a holding pattern at a distance set in preferences. (I use default.) ai in holding may disappear if too long a hold is necessary but in my opinion smooth approaches and ground operations have priority for the visual aspects and operation of the user aircraft.

 

Another utility is FS9 Configurator version 1.6 the latest fs9cfg16.zip. Among its many features it can modify FS9's ai engine successfully to allow you to adjust landing roll speed and taxi speed. By increasing taxi speed just a very little bit it helps with alleviating taxiway congestion for ai to vacate the runways. Increasing taxi speed too much gives a choppy cartoon effect and aircraft will slide around corners and off taxiways.

 

Both of these utilities in concert help with airport local operations efficiency.

 

aismooth requires FSUIPC3 (for FS9) but will register itself automatically as a freeware application so there is no need for user paid full fsuipc registration unless you want its many other features. If it does not have it you can get the latest full and patch versions with links here:

 

http://forum.simflig...pdated-modules/

 

These and your fixes to the afcad for more parking should help with the congestion problem.

 

Can you tell us which version of KJFK you are using and if you are using the traffic app afcad or the one for add-on scenery if used. You should use the afcad type file AF2_, AFX_, or ADE thart came with the add-on if you have one.

 

Also freeware ADE is safer to use with these files. AFCAD will strip out and/or corrupt these other types furnished with recent add-ons.

 

http://www.airportdesigneditor.co.uk/

 

For your purposes make a backup of any afd type file then use its file/open airport from .bgl, browse to the file and open. After editing save as a project so you can correct things if needed by editing the project. Then compile to a .bgl. Change the extension of the existing afd type file to make it ineffective.

 

ADE by default will negate default airport comm frequencies. If the existing files you edit do not have them listed (such as AF2_ files which do copy them) you may have to reimport them from the default airport. A List/Comms will tell you if they are in the edited file. An FS test will tell you if they are working. I find that some projects rely on the default comms to be passed through. ADE has a more complete fault finder.

 

A few airport projects have dead-end taxiways and loops. These might be used for ai ground vehicles or special cases of ai marine vessels in scenery.