Installing MAIW packages in FSX

[avt309947]

I used AI Flight Planner and this is what happens when I open one of the converted traffic bgls. At the same time a window opens asking me if I want to "add the missing airports to airportList.dat based on available information"
Shouldnt the airport codes be four letter?
_____________________________________
Flight Plan 1
Leg 01: No data available for airport "KEF"
Leg 02: No data available for airport "SNN"
Leg 03: No data available for airport "BTS"
Leg 04: No data available for airport "HEL"
Leg 05: No data available for airport "BRU"
Leg 06: No data available for airport "PMI"
Leg 07: No data available for airport "EGU"
Leg 08: No data available for airport "ADW"

Flight Plan 2
Leg 01: No data available for airport "MSP"
Leg 02: No data available for airport "EDF"
Leg 03: No data available for airport "RJT"
Leg 04: No data available for airport "PEK"
Leg 05: No data available for airport "RJT"
Leg 06: No data available for airport "EDF"
Leg 07: No data available for airport "ADW"

Flight Plan 3
Leg 01: No data available for airport "EDW"
Leg 02: No data available for airport "OFF"
Leg 03: No data available for airport "ADW"
Leg 04: No data available for airport "LSV"
Leg 05: No data available for airport "TIK"
Leg 06: No data available for airport "MSP"
Leg 07: No data available for airport "ADW"

Flight Plan 4
Leg 01: No data available for airport "MWH"
Leg 02: No data available for airport "YYC"
Leg 03: No data available for airport "YYZ"
Leg 04: No data available for airport "IAH"
Leg 05: No data available for airport "LAS"
Leg 06: No data available for airport "CLT"
Leg 07: No data available for airport "ADW"

Flight Plan 5
Leg 01: No data available for airport "ORD"
Leg 02: No data available for airport "POB"
Leg 03: No data available for airport "BNA"
Leg 04: No data available for airport "ATL"
Leg 05: No data available for airport "HIF"
Leg 06: No data available for airport "ADW"

Flight Plan 6
Leg 01: No data available for airport "NUW"
Leg 02: No data available for airport "EIL"
Leg 03: No data available for airport "RJT"
Leg 04: No data available for airport "RCQ"
Leg 05: No data available for airport "RJT"
Leg 06: No data available for airport "EIL"
Leg 07: No data available for airport "NUW"
Leg 08: No data available for airport "ADW"

Flight Plan 7
Leg 01: No data available for airport "TER"
Leg 02: No data available for airport "TOJ"
Leg 03: No data available for airport "LGA"
Leg 04: No data available for airport "BOJ"
Leg 05: No data available for airport "OTP"
Leg 06: No data available for airport "EGU"
Leg 07: No data available for airport "EGQ"
Leg 08: No data available for airport "ADW"

Flight Plan 8
Leg 01: No data available for airport "BAB"
Leg 02: No data available for airport "EIL"
Leg 03: No data available for airport "RJT"
Leg 04: No data available for airport "PEK"
Leg 05: No data available for airport "RJT"
Leg 06: No data available for airport "EDF"
Leg 07: No data available for airport "ADW"

Flight Plan 9
Leg 01: No data available for airport "MST"
Leg 02: No data available for airport "INN"
Leg 03: No data available for airport "TXL"
Leg 04: No data available for airport "RMS"
Leg 05: No data available for airport "LJU"
Leg 06: No data available for airport "GKE"
Leg 07: No data available for airport "ADW"

Flight Plan 10
Leg 01: No data available for airport "PIK"
Leg 02: No data available for airport "OSL"
Leg 03: No data available for airport "SVO"
Leg 04: No data available for airport "WAW"
Leg 05: No data available for airport "ORY"
Leg 06: No data available for airport "AMS"
Leg 07: No data available for airport "TER"
Leg 08: No data available for airport "ADW"

Flight Plan 11
Leg 01: No data available for airport "BAB"
Leg 02: No data available for airport "PAE"
Leg 03: No data available for airport "RIV"
Leg 04: No data available for airport "MGE"
Leg 05: No data available for airport "OFF"
Leg 06: No data available for airport "EDW"
Leg 07: No data available for airport "OFF"

Flight Plan 12
Leg 01: No data available for airport "SUU"
Leg 02: No data available for airport "RNO"
Leg 03: No data available for airport "ADW"
Leg 04: No data available for airport "BOI"
Leg 05: No data available for airport "LSV"
Leg 06: No data available for airport "GTF"
Leg 07: No data available for airport "OFF"

Flight Plan 13
Leg 01: No data available for airport "CYS"
Leg 02: No data available for airport "ADW"
Leg 03: No data available for airport "TOL"
Leg 04: No data available for airport "ADW"
Leg 05: No data available for airport "SDF"
Leg 06: No data available for airport "CNW"
Leg 07: No data available for airport "MGM"
Leg 08: No data available for airport "CYS"
Leg 09: No data available for airport "FFO"
Leg 10: No data available for airport "ADW"
Leg 11: No data available for airport "CBM"
Leg 12: No data available for airport "FFO"
Leg 13: No data available for airport "ADW"

Flight Plan 14
Leg 01: No data available for airport "BFT"
Leg 02: No data available for airport "ADW"
Leg 03: No data available for airport "DLF"
Leg 04: No data available for airport "NQI"
Leg 05: No data available for airport "NGP"
Leg 06: No data available for airport "ADW"
Leg 07: No data available for airport "NZY"
Leg 08: No data available for airport "HMN"
Leg 09: No data available for airport "CVS"
Leg 10: No data available for airport "CYS"
Leg 11: No data available for airport "RDR"
Leg 12: No data available for airport "BFT"
Leg 13: No data available for airport "ADW"

The leg reference numbers in this message refer to the the text or traffic file, shown along the right-hand edge of the leg editor list box.
The following airport(s): ADW, AMS, ATL, BAB, BFT, BNA, BOI, BOJ, BRU, BTS, CBM, CLT, CNW, CVS, CYS, DLF, EDF, EDW, EGQ, EGU, EIL, FFO, GKE, GTF, HEL, HIF, HMN, IAH, INN, KEF, LAS, LGA, LJU, LSV, MGE, MGM, MSP, MST, MWH, NGP, NQI, NUW, NZY, OFF, ORD, ORY, OSL, OTP, PAE, PEK, PIK, PMI, POB, RCQ, RDR, RIV, RJT, RMS, RNO, SDF, SNN, SUU, SVO, TER, TIK, TOJ, TOL, TXL, WAW, YYC and YYZ are not in "AirportList.dat".

[Firebird]

Which particular package is this for? It looks like the conversion has removed the first letter of the airfield. This would explain why the flights aren't showing up.

Have you got the latest version of AIFP 1.6.35? If you think that that is causing the problem then try FP_FS9_FSX from here http://aifs2.pvdveen.net/?page_id=5

[Greg]

There's nothing wrong with those codes, but they are IATA codes not ICAO which flightsim uses.

AMS=EHAM Amsterdam, BRU=EBBR Brussels to name a few.

[avt309947]

Success!

I converted all FS9 files using FP_FS9_FSX and all is perfect. Strange that it didnt work with AIFP.

I hope that this is of use to others who are having problems seeing traffic and I would like to thank
Steve for helping. Its much appreciated

Rgds

Adrian

[Firebird]

Phew! That was a tough one to work out. Glad we could help.

[avt309947]

I spoke too soon!

When I re add my FSX WOAI traffic files to the converted MAIW files in scenery/world/scenery, I only have MAIW traffic showing. When I scan the scenery/world/scenery folder with AIFP for any FS9 files, it lists all of the converted MAIW files as FS9. I assume that if these files are still recognised as FS9 that is why Im not seeing the WOAI FSX files.

Any further help would be appreciated

Rgds

Adrian

[Firebird]

That would be correct. Do your converted bgls have the fsx extention, i.e. xxxxxxx_FSX.bgl?

[avt309947]

Yes all converted bgls have_FSX.bgl suffix

[Firebird]

So I as I understand it, according to AIFP, FP_FS9_FSX fails to convert the flightplans to FSX properly and says that FSX flightplans are FS9.

Somehow, I doubt this to be true as somebody would have complained by now and I converted one and compared the text files and the days have been altered. So I think there is another problem. I think that AIFP assumes that any file that doesn't have '//FSXDAYS=TRUE' from the top of a flightplans.txt file is automatically an FS9 file.

I think you have two options, either persist with using FP_FS9_FSX, and trying to find what traffic file(s) hasn't been converted or try to solve the AIFP issue.

Now going back to when you converted the bgls using AIFP can you confirm that all of those had'_FSX' suffixes and that you moved them into your \Scenery\World\Scenery folder and removed all the FS9 files?

If so then I would suggest continuing with FFF. My guess is that its a file that is not in the usual global place. Do a file search for 'Traffic_' on your FSX hard drive to see how many don't have the '_FSX' suffix, from any folder.

[avt309947]

You understand correctly. Whilst the converted files have FSX suffixes, AIFP sees them as FS9, though I take your point that others would have experienced the problem if it were the case which means Im doing something daft.

Yes I did remove all FS9 files when I converted using AIFP. The files had FSX suffixes and I did move them into scenery/world scenery, and as soon as I get home, I will most definitely look for rogue FS9 Traffic files in other folders as it looks more and more like it may be the solution.

Thanks Steve

Rgds

Adrian

[avt309947]

Removed one or two suspect files found in other folders, but no difference. Placed WOAI files only in scenery/world/scenery which worked perfectly. Then added four MAIW files which immediately stopped the WOAI files from working. I even had a go at attempting to convert all the WOAI files using FP_FS9_FSX to match the previously converted MAIW files but they would not convert as the files are already FSX!

[CelticWarrior]

The flightplan files which you think you've converted to FSX format haven't been converted, this is the reason your flights aren't showing up. You can't mix FS9 format flightplan files with FSX format flightplan files. Either your WoAI files are in FS9 format or your MAIW files are. It's one or the other

[petebramley]

Celtic

Hi there, I have a quick question for you:

Am currently working through loading up all the MAIW packages onto my shiny new Vaio. Once I have completed this and checked that they all work as they should I wish to install all of the WOAI packages released so far. Can I load direct into FSX via the WOAI installer or do I need to convert the files first. Reason I ask is that on previous copy of FSX loaded on a spare Vista PC I installed direct with the Installer. Does this load them up in FSX or FS9 format

Regards

[DeepSea-Two-One]

You can point the WoA installer to unpack and install the package files in FSX. I'm not sure if the aircraft will install in a folder off the FSX root named \Aircraft or if they will be installed in \SimObjects. The traffic files will be installed in \Scenery\World\Scenery.

The WoA Installer uses TTools to create the Traffic_xxxx.bgl file - so it will be FS9 format only.

[DeepSea-Two-One]

You understand correctly. Whilst the converted files have FSX suffixes, AIFP sees them as FS9

AIFP checks the .BGL file structure to tell if the traffic file is FS9 or FSX. If AIFP says it is still an FS9 format - then you can be sure AIFP is reporting that correctly.

Peter's FP_FS9_FSX utility is old - over four years old. Some of the changes which Don has made in AIFP are to address issues which surfaced in AIFP early versions. Early versions of AIFP had Peter's decompiler/compiler for FSX. Peter's documentation for FP_FS9_FSX also notes several things which can cause a file can fail to convert correctly.

One issue I've had with some MAIW traffic files and flightplans go back to the early days of AIFP testing when some of the MAIW flight plan writers were working with Don. Because TrafficTools does only minimal error checking - there were things being done by the MAIW flight plan writers which were technically illegal according to the SDKs and to the coding documentation Lee Swordy provided to Don. But they worked in the MAIW traffic files, and the compiled with TTools.

Rather than disable much of Don's error checking - he created a special mode for compiling TTools source files and converting FS9 traffic files to FSX - the Compile in "Raw" mode option. Basically that disables the AIFP error checking and compiles the traffic file exactly as written.

If you have trouble converting, or with a supposedly converted MAIW Traffic_xxx.bgl - go back to the original source .bgl and convert it in the Raw mode to an FSX file. (You are going back to the original Traffic file from the MAIW install for each conversion attempt - are you not? Trying with one file several times with different converters is pretty much a guarantee to mess it up completely. Always use the original source file for each attempt to convert.)

That almost always works.

Occasionally you will have to modify the Airports.txt and Flightplans.txt file for certain airport changes between FS2004 and FSX before the file will compile correctly.

Don's AIFP does a great job of giving error messages, but sometimes too much information.

[CelticWarrior]

Pete,

As long as the files were previously converted to FSX format, yes. The WOAI installer doesn't convert the files, it merely installs them to a location you specify within the FSX file structure.

All I ever do is throw all the files into the same folder and let AIFP do it's business when I click on the check for FS9 files button.

Hope that goes a little way to answering your question

[Firebird]

I am not saying that the gen that you guys are giving is inaccurate but if that is correct then I do have one question.

As I understand it it, if you have a mix of FS9 and FSX traffic files then only the FS9 ones show up. Is this correct?
If it is then surely if anything the WoAI ones, FS9?, would show up but the MAIW ones, FSX, would not.

I ask purely from a learning curve here, or have I misread something?

[CelticWarrior]

That's the theory. In practice I've found that it can vary.

[Firebird]

OK, so it might be that his WoAI plans need converting then.

[petebramley]

Celtic

Many thanks your reply will give it a try and see what transpires