can someone, somewhere help me with this,

i've done everything it tells me to do, and read the faq's in the readme, i've converted the traffic files to fsx, turned traffic settings to 100% but i still have no traffic, i do however have the scenery.

i appreciate it's probably already been asked elsewhere, but it's bugging me now

thanks,
Adam

Because of the difference in parking spot sizes between the system make sure that the parking spots in FSX are at least half the wingspan from the aircraft.cfg file.
We produce the packages for FS9 which means we set the parking spots so that the mdl size fits, which FS9 uses, this means that the FSX parking spot requirements can, and often do, be different.

is there any way i could go about doing that, (any specialist software required??)

As the airport file is an AF2 file then you can use afcad. Another and more modern freeware utility is ADE9X.

A payware tool would be AFX but that is not necessary in this case.

Hang loose, bud, I'll take a look at it this weekend, and send you a revised version. I had similar issues with another base, NAS Corpus Christi I think, and the T-34s.

ok, i'll wait a bit before trying to get my head around the whole afcad issues

Well, it is kinda complicated but not extremely hard -- you kinda get the hang of it, but it takes a couple saturdays of fidding with it, and for some it is frustrating.

For my part, I would welcome a few more FSX users here that could work on converting a few more of these MAIW FS9 bases. So if you have an interest, please consider. Go look for Airport Design Editor v 1.5 (there are updates, but this will is the base version) by Scruffyduck. Go register at FSdeveloper, Jon Masterson (scuffyduck himself) is over there, as are many of the MAIW master scenery creators. It's a nice creative outlet and I enjoy it -- and after a few airbases you start to get good at it. You also will need sbuilder X 1.3... also available over there. In fact for building the landclass and terrain exclusions and flatten polygons, I find this easier and faster. Was a bit harder initially to figure out, though, when getting started, but now I am able to get around pretty quickly. For some of these airbases, that have the objects already placed, I find those polygons are really all that are needed.

OK, I'll be back here with an update on Pcola.

Ripcord

Firebird wrote:Because of the difference in parking spot sizes between the system make sure that the parking spots in FSX are at least half the wingspan from the aircraft.cfg file.
We produce the packages for FS9 which means we set the parking spots so that the mdl size fits, which FS9 uses, this means that the FSX parking spot requirements can, and often do, be different.

Note this from the aircraft.cfg file --- wing span is pretty big.

[airplane_geometry]
wing_area = 400 //Square feet
wing_span = 57.2 //Feet
wing_root_chord = 5.4 //Feet

I use meters for my parking areas, so 57.2 feet is about 17.434 meters. The parking radius of the T-6A parking areas in the AF2 file are set at 10.06 meters. So unless I am confused, this ought to be enough. I'll experiment with some trial and error and report back.

Hmmm, I do not think that the parking areas are the issue here. There are mil combat spaces that are 44 meters in radius, and nothing parks here. Nothing at all, not T-6A AI or any other for that matter.

ok, will look into the software, but starting to get a bit confused, this is the first pack i've had problems with, so i will be looking forward to getting my head round this

OK if the parking slots are rules out, then taking into account that I don't have FSX, the most obvious causes for this are either duplicate afcads or that the traffic file hasn't been converted.
There are other causes, i.e. aircraft not found, but it might be worth using ACA2005 and/or ACA2007 to see if there are any obvious errors with either the aircraft or the plans.

i know i converted and deleted the fs2004 traffic file, so the mystery of the missing Pensacola Texans continues...

I'll take a look for duplicate afcads, only question i have, is where are they found???

Firebird, I completely agree. It is not the parking spaces. It also not the elevation, I went thru and adjusted that. I'm getting other military AI (non-MAIW) landing there now.

Dont believe that the duplicate AFCAD thing is the culprit here. Though I do have some other KNPA in the addon scenery folder it is a separate folder and not activated.

I also note that I have no T-6A Texans at Pax River either.

When I look at the traffic bgl in AIFP2, it says that all these aircraft are NOT available for FSX. Not sure what is the cause of this, but I believe this is the issue at hand.

adamp89 wrote:i know i converted and deleted the fs2004 traffic file, so the mystery of the missing Pensacola Texans continues...

I'll take a look for duplicate afcads, only question i have, is where are they found???

Generally they will be found in the addon scenery folder -- just do a search for KNPA in your FSX folder and look at all the results.

Somewhere there is a utilities that checks for duplicate AFCADs as well... don't recall right offhand which one that is.

adamp89 wrote:I'll take a look for duplicate afcads, only question i have, is where are they found???

Duplicate afcads can be found in any folder that you have activated in your scenery.cfg file. This is precisely the reason why you have to keep a tidy structure. Please note that I am not saying that you don't or even that you have a duplicate my comment here is meant purely as a general information point.

An idea does occur to me here. It might be that you have some old exclude files for the airfield in your system. I had that once before where some excludes for Warton and Wattisham, wiped out any parking slots for my scenery. It took me ages to find that one out.

This is why it is important to remove all old scenery files when adding new ones, or at the very least inactivate them.

An idea does occur to me here. It might be that you have some old exclude files for the airfield in your system. I had that once before where some excludes for Warton and Wattisham, wiped out any parking slots for my scenery. It took me ages to find that one out.

Interesting. Let's check this too. There is an MAIW_KNPA_exclude file, which was in my MAIW Exclusions folder. Ah, and I see there are two other files in that folder, called Pensacola Exclude Default 1 and Pensacola Exclude Default 2. These last two come with the scenery package... so I had them in there twice. I'll remove all three of these files in the MAIW exclusion folders and see what happens.....

OK, i forgot i had a duplicate afcad locator on my computer, but i will have a look for the excludes too, this may be tomorrow though as i don't have access to my fs computer. thanks for the help,

Adam

I figured out why I could not see the aircraft in AI flight planner 2... I had recently deleted and regenerated by fsx.cfg file, and thus the simobjects/MAIW entry was gone. Pulled up the FSX MAIW instruction guide again, and repeated that step. Now when I open those flight plans, AIFP sees all the aircraft.

Actually this solves a number of mysteries that I've had here in recent days.... now let's see if this solves the problem at KNPA.

Nope, no joy.

so all everything that's been tried doesn't work/ doesn't make sense, so I'm beginning to think it's just one of those things for fs9 that just wont work in fsx.

Does any FSXer have the Pensacola T-6s working? Is this just a case of finding the error or is it a model that won't show in FSX?