AIFPC – AI Flight Plan Compiler/Decompiler for FS9 and FSX RC1

[garfield_x]

Introduction

AIFPC is a program for compiling/decompiling flight plans in the TTools txt format to the native BGL format and vice versa that are used by FS9 or FSX.

Because there is a different in the format of the FS9 BGL files and the FSX BGL one need to choose the compile target (FS9/FSX) before compiling.

The main difference between the FS9 and FSX BGL files is the way the times are stored. Although FS9 BGL files work in FSX you cannot use FS9 and FSX BGL files at the same time in FSX. FSX BGL files do not work in FS9
Another difference between FS9 and FSX is the numbering of the days. In FS9 the week starts on Sunday which has the number 0. In FSX the week starts on Monday with the number 0. So when using FS9 compiled flight plans there is a shift in the days. Flights who would departure on Sunday in FS9 will departure on Monday in FSX.
For this AIFPC has the possibility to renumber the days when compiling the flight plan.

To distinguish between the different BGL files AIFPC can automatically add FS9 or FSX to the end of the BGL file name.

When FS9 or FSX is present on your system (AIFPC looks for the registry key) one can set the output folder to the scenery folder. But also a custom output path can be chosen.

Another feature is the possibility to batch compile/decompile flight plans. Just select more than one flight plan in the selection window.


Installation

AIFPC uses the .NET Framework 2.0 so that must be present on your system.
Furthermore its only unzipping the contents of the zip file in a folder of your choice an run the program by double clicking


Bugs and Comments

This is a first Release Candidate. So there still can be bugs present and maybe one have comments or whishes for the final version.
When finding a bug in the compilation/decompilation process please provide me with the flight plan or BGL file so I can check/solve it more easily.
Bugs and comments can be send to aifs@pvdveen.net

[Alex Barrett]

Thank you Peter!

I'm downloading now. Always appreciate new tools.

Alex

[KaelO]

Hey guys,

Firstly, thanks for the programs your producing, good work.

My question is though, why bother with the FSX format for flightplans? Aside from the different day/numbering system, I don't see an advantage. From what I understand FSX compiled flightplans won't display if there isn't a parking spot available at either the departure or arrival airport. This is a significant disadvantage in my opinion. At least with the FS9 style .BGL format you can see all the aircraft, worst case scenario the aircraft will disappear after landing.

Am I missing something or is there another advantage to the FSX style?

Cheers,
Kael

[garfield_x]

I think you mean that the TDB compiler would not compile a flightplan if there is not the right parking space present.

That has nothing to do with compiled BGL files in FSX. So i think you misunderstand it.

[garfield_x]

An other reason not to use FS9 BGL files is that also the boat traffic files do not work when an FS9 BGL is present.

Using only FSX compiled files these work perfectly.

[gadgets]

Thanks, Peter. Being able to generate FSX flight plans from TTools format files is going to save a lot of people a lot of time. Too bad it wasn't around a month ago when I converted CYYJ to FSX. But, at least, I'll be able to keep the two versions in step now with a single source file.

Don

[garfield_x]

New version available. Solved a bug due to some regional settings.

[BASys]

Hi Folks

Peter -
Thanks for your excellent utility.

Could you possibly please add
a)
The ability to use single common lists for each of airport & aircraft.
Rather than specifically requiring the filenames to match the flightplan filename.

b)
Error trapping to match, rather than an unhandled exception error.

Many thanks
ATB
Paul

[garfield_x]

Could you possibly please add
a)
The ability to use single common lists for each of airport & aircraft.
Rather than specifically requiring the filenames to match the flightplan filename.


What you mean by this?

[BASys]

Hi Folks

Pater -
Say I have 3 sets of flightplans -

flighplans_a.txt
flighplans_b.txt
flighplans_c.txt

Currently,
your applet requires all the following to be present -

aircraft_a.txt
aircraft_b.txt
aircraft_c.txt

airports_a.txt
airports_b.txt
airports_c.txt

Can it be modified to work with just -

aircraft.txt
airports.txt

i.e.
a single list for each, covering all airports, and all aircraft.

HTH
ATB
Paul

[garfield_x]

But the flightplans will be still be flightplans_a.txt, flightplans_b.txt?

So when u compile the fp's for a you also get in your BGL all airpots and all aircraft, even those who are not used in that flightplan at all.

Isn't that a strange way of working?

A program like ACA2005 will find then a lot of errors for aircraft not used in the FP

[BASys]

Hi Folks

So when u compile the fp's for a
you also get in your BGL all airpots and all aircraft,
even those who are not used in that flightplan at all.

Peter -
Surely not. :eek:

The only references that should get compiled,
are those called by the F/P.

I'd certainly hope the latter was the case. :)

ATB
Paul

[garfield_x]

I do not know what u used until now, because TTools just add all airports and aircraft that are in those files. It does not looks which airports and aircraft are used and only add those. The same applies to AIFPC.

[BASys]

Hi Folks

I do not know what u used until now,
because TTools just add all airports and aircraft that are in those files.
It does not looks which airports and aircraft are used and only add those.
The same applies to AIFPC.

Peter -
I am very surprised.
I hadn't been aware that was the case.



Does that mean
each f/p will behave entirely independently ?

e.g.
If I create 5 sets of F/Ps,
each containing destination airport AAAA

Then in each of the 5 airport.txt files
give different sets of lat/long coords for AAAA

Will the 5 aircraft go to 5 different AAAA locations ?



If not
then what's the point of including redundant data ?

Or am I missing something ?



PS
TTools must check whats used for airport & aircraft,
as it throws an error for any missing.



ATB
Paul

[garfield_x]

No they will go to the same airport. Because the airport is defined in FS itself too.

The lat/lon values are used to calculated the route/sector transitions eq. the place where an aircraft is at a certain time. So giving wrong values the aircraft start at a wrong point/place in FS and will not arrive at the right time on the destination and will certainly disappear. (or maybe will never appear, or just popup at the airport)

Adding allways all the airport to a FP is a giant overhead. There are 24000+ airports. (A small FP which only visits 10 airports will have 24000+ airports in the BGL.)
FS has to read all tha data and have to process it. So its is certain an performance drop maybe not when flying, but certainly when starting a flight and FS has to load all the FP data.

TTools and AIFPC only checks if an airport in the FP is present in the airport list, (same for aircraft) otherwise it can not do the sector calculations, whci are needed to be present in the BGL file.

[gadgets]

Peter, your decompiler "saved my bacon" yesterday. After spending the afternoon updating my CYYJ flight plans from mid-2006 vintage to the present, I initiated what I thought would be the final compile (with tTools, since your compiler had a little problem - now fixed). Immediately upon clicking the "Compile" button, my flight plan file disappeared from the screen and, as far as I can tell, completely from my computer. What to do to save the afternoon's work?

I checked the destination folder and found that the file had successfully compiled. I ran your de-compiler and, voila, I had a new flight plan file.
Thanks!

However, from that experience, I would offer one suggestion. The default time format output from AIFPC is HH:MM:SS. Apparently, the times are randomized slightly in the compiled flight plans since only a few came back with departure time on the even minute. So, for clarity, I would suggest the default format be changed to HH:MM - with the time rounded to the nearest minute - or a user option for that format be provided.

Thanks again,
Don

[garfield_x]

Strange that the flightplan disappeared. I do nothing mare then reading that file, not copying/moving etc.

Between compiles/decompiles time can differ a littel bit due to rounding errors. Also the when not using the @ symbol the arrival time is calculated from the departure time and the speed stetting, so that can differ too.

I will look for the removing of the seconds (always found it curious that seconds were used :) )

[gadgets]

Peter, I was using TTools at the time, not AIFPC. (I only mentioned that problem to "set the scene" for AIFPC "to the rescue".)

Sorry for the confusion.

Don

[BASys]

Hi Folks

Peter -
Had a couple of issues when compiling with AIFPC.

1) Failed Compile
See screenie.
May I email you a zip of the source files ?

Compiles ok with TTools.
Airport count: 543
Aircraft count: 16
Flight plans: 23 Legs: 753



2) File Locks
Not releasing file-locks for f/p, airport, & aircraft files
following a failed compile.

Error example -
FILE NOT COMPILED: flightplans_odg_ukez_bhl.txt



3) Window Titles
Error dialog has the same title as parent window,
hence unable to capture active window screenie.



Back to my earlier query.
TTools does support dissimilar filenames.



HTH
ATB
Paul

[garfield_x]

Yes please send me the source files so i can have a look of what went wrong.

My email adress is in the documentation

I dod not know that TTools uses these files that way. I'll check that.

[BASys]

Hi Folks

Peter -
Please see your email.

Many thanks
Paul

[garfield_x]

I finally found the bug in the FSX compile pfffff

New test version added.

[garfield_x]

Already a newer version

This version also changes the ICAO codes which changed from FS9 to FSX.

It uses a txt file for that that can be modified by the user.
Structure of the file is:

old ICAO,new ICAO,lat,lon,height

[gadgets]

Peter, welcome back.

I have confirmed that I can compile for both FS9 and FSX without error. However, the compiled files (which are about the right size) still don't generate any traffic in either FS9 or FSX. The flight plan file is unchanged from the version I sent you earlier.

Compiling the flight plan file with TTools does result in the intended traffic.

Sorry I can't report better news,
Don

[garfield_x]

Grrrr Don. I'm not sure whats wrong then.

I have completely recompiled all my FS9 FP's to FSX, and all aircraft are visible in FSX.

You are sure you have not an other FS9 bgl file in FSX? So that the FSX BGL file is not used?

Is it only this FP? or all FP's?

i will look again with a hex viewer whats the different between the two files.

[gadgets]

No, there are no other traffic bgls in the FSX scenery folder.

Please note that the same situation occurs with FS9 as well - no AI of any kind in sight.

Is anyone else experiencing similar difficulties? Anything you can think of that I can do to help resolve this problem?


I'll send my FP source and te two compiled files to you via e-mail.
Don

[garfield_x]

The latest RC version is available

[garfield_x]

New version.

* Solved a bug when using repeat times from 1 and 2 hours.
* AIFPC will remember last 5 used output path in a combo box
* No warning anymore when duplicate airports were added due to the changed FSX list .

[Irishman]

An other reason not to use FS9 BGL files is that also the boat traffic files do not work when an FS9 BGL is present.

Using only FSX compiled files these work perfectly.

...and this is exactly why I was thrilled to find this thread a few days ago. I dowloaded the decompiler and love it! Now I have all of my WOAI (and others) without losing the boat traffic. Thanks!!!

[Bell_209]

You're a legend, Peter! Thanks very much for this tool!

[Emile]

Hello,
I receive following error when I try to build a flight plan .
Any recommendations?
Thanks in advance.

[garfield_x]

please attach the flightplan too, then i can see what is going wrong

[Green_Hornet]

Hi! When I convert a flight plan everything goes great. When I try and run the FP FSX throws an error saying "Can not read file.". Fsx then closes. When I compile the same FP for FS9 no error. Any Ideas?

FSX Deluxe, SP1, Windows XP Pro 64, and Newest version of AIFPC.

[garfield_x]

can you send me the txt files for the flightplan?

[Emile]

Hello, please find the requested files
Thanks in advance
Emile

[garfield_x]

Airport RJBT has an error in the lat/lon values (there is an extra ' )

[Emile]

Hello Garfield_X,
Thanks for your help, solved...:D
I love this product.:)

[jvile]

Peter

Reading through all this I only see one reference to "@"

My question is what does AIFPC do with the "@" during the FS9 to FSX type compiled FP?

I have been doing studies in FSX when the @ is present vs not present using TTool FP's and everything we know about FS9 also occurs in FSX. This includes no AI materializing into the AI Visual Zone and the popping up of all AI Panes at the Parking Stands.

I don't want to go back to the early days of FS9 TTool FP's and reopen the @ discussion but some of us (Reggie, MRAI, myself) did a tremendous amount of work to get @ timing controls working correctly in respect to Aircraft.txt speeds that must be used.

Are you recommending remove @, bring the Aircraft.txt back up to TAS vs IAS in a compiled TTools FP and then convert over to FSX?

[garfield_x]

Jim

At this moment AIFPC use the same calculation as TTools used when it finds the @ symbol in the flightplan. (AIFPC uses the same calculation routine as is present in TTools)
So you can still use both methods if you want.

When using the @ symbol the program uses the fixed arrival time and for the sector crossings if calculates the aircraft speed according to the arrival time.

When no @ symbol is present it uses the aircraft speed and it calculates the arrival time (and uses a ground time of 15 minutes as in TTools).

As you see the same behavior using the FS9 bgl files in FSX, then you would also see the same behavior using the FSX bgl files i think.

[jvile]

Thanks Peter

I can work with that

I did notice if I convert to FSX with @ present in FS9 FP's then on a convert/decompile back to FS9 @ was still present so I assumed you kept everything as is on the front side.

I was confirming the @ was not getting flushed out when going from FS9 to FSX when using AIFPC.

[Green_Hornet]

Hi Guys And Gals.
Not sure if you ment me or Emile, but here is the file.

This file was compiled using AIFPC from the "Flightplans_EVAI_Su07_AllegiantAir.txt" file I found on Avsim. Like I said works great if I compile with TTools, but when I use AIFPC. FSX says can't read file and exits. I have to shut down FSX.exe 32 manually tho.
Also file Compiles with no errors using AIFPC.
AFIPC.exe file date is June,18,2007

[garfield_x]

please may i have the txt files too?

[garfield_x]

Thanks Peter

I can work with that

I did notice if I convert to FSX with @ present in FS9 FP's then on a convert/decompile back to FS9 @ was still present so I assumed you kept everything as is on the front side.

I was confirming the @ was not getting flushed out when going from FS9 to FSX when using AIFPC.

Yep, the @ is not removed with compile/decompile runs

[Green_Hornet]

Here are the .txt files.

[gadgets]

Peter, I've noticed a little idiosyncrasy with the latest version of AIFPC. That is, after starting AIFPC, the first couple of times one sets the Output Path, upon clicking on "Compile", the the output path window is cleared and the output is directed to the root folder of the logical disk on which AIFPC resides. After a couple of attempts, the problem seems to correct itself and everything is OK therefater.

EDIT: It seems that if the "Flightplan file/Traffic BGL file" entry if made just before the "Compile" button is clicked, the "Output path" entry is not cleared.

Don

[garfield_x]

Peter, I've noticed a little idiosyncrasy with the latest version of AIFPC. That is, after starting AIFPC, the first couple of times one sets the Output Path, upon clicking on "Compile", the the output path window is cleared and the output is directed to the root folder of the logical disk on which AIFPC resides. After a couple of attempts, the problem seems to correct itself and everything is OK therefater.

EDIT: It seems that if the "Flightplan file/Traffic BGL file" entry if made just before the "Compile" button is clicked, the "Output path" entry is not cleared.

Don

Mmmm How did you set the output path?

[gadgets]

Peter, I set the output path using the browse button to the right of the output path entry box. I also tried setting it using the drop-down capability of that box, but didn't make any difference. Incidentally, the drop-down list records the blank entries.

Regarding my edit to my previous e-mail, I was a bit hasty. Setting the input window first doesn't always sidestep the problem.

Don

[jvile]

Peter

What OS did you use in the develpment of AIFPC?

Just wondering if I should run my new Area-51 ALX computer shipped with Vista 32 in a AIFPC XP2 compatibility mode. I received a BOD but also had Yroute and AITM running at the same time.

I traced the BOD back to Yroute which is not compatible with Vista/FSX. Lost my FSX activation entry in the registry along with FS9/AFCAD entries. The 1722/1603 error MSN patch wasn't much help in this case. Thank goodness for current Reg.reg backups and Vista restore points which I am a firm believer in. Still waiting for Norton to get GoBack working for Vista.

[garfield_x]

Jim

My developer PC is running XP SP2.
Strange, because AIFPC only need .NET 2.0 to be installed, so it should run on Vista without porblems. I will do some test on my Vista PC.

[gadgets]

Peter, another minor problem still exists in AIFPC. That is, the conversion from FS9 days to FSX appears to be backwards. For example, if, in a weekly flightplan, the day of operation is specified as 1 (Monday in FS9), in FSX the aircraft operates on Wednesday (i.e., day 2); it should operate on FSX day 0.

Don

[jvile]

Peter

I have no problems with AIFPC and Vista 32. My version of Vista shipped with .NET 1.2, 2.0 and 3.0 installed.

The BOD was a Yroute problem but was just curious about the OS/.net used during the design of AIFPC.

[garfield_x]

Peter, another minor problem still exists in AIFPC. That is, the conversion from FS9 days to FSX appears to be backwards. For example, if, in a weekly flightplan, the day of operation is specified as 1 (Monday in FS9), in FSX the aircraft operates on Wednesday (i.e., day 2); it should operate on FSX day 0.

Don

OMG :eek: did i add a day in stead of substracting? And you call that a minor problem?

TY DON!!!!!!!!!! Why nobody else mentioned it. :confused:

[BASys]

Hi Folks

Peter -
I had noticed that my traffic didn't appear to be departing as per schedule,
I'd just put it down to FSX :o

A two day offset would explain it. :D

ATB
Paul

[gadgets]

Peter, perhaps others are more problem-tolerant than me.

Re the clearing output window, I have discovered that if I put the desired folder specification into the "lastoutput" value field in the .INI file and then start AIFPC, the output window is NOT cleared and things work as expected. However, if I attempt to specify the folder using the associate browse button, it is cleared upon clicking the "Compile" button sometimes two, sometimes three and, on occassion (I recall) four times before things "settle down".

If one always outputs to the same folder, once set up the problem probably wouldn't be experienced (because the last output folder specification is set up on entry to AIFPC.) This may explain why others haven't yet complained.

Have a great weekend,
Don

[lucclaus]

I mentioned the wrong conversion from FS9 to FSX alreday in this post

http://www.evolveai.com/forums/showthread.php?t=1983&page=3

Either I explained it wrongly or you were so busy that it was somewhere lost "under way"

Rgds
Luc

[garfield_x]

Sorry yes, must have missed that. :(

Will upload the new version soon.

[garfield_x]

New version.

Corrected the days and the output folder problem.

If no problems arrive anymore i will release the first version soon on AVSIM.

Next to do is to made a .NET Assembly of it so people can incorporated it in their own programs.

[garfield_x]

Hi Guys And Gals.
Not sure if you ment me or Emile, but here is the file.

This file was compiled using AIFPC from the "Flightplans_EVAI_Su07_AllegiantAir.txt" file I found on Avsim. Like I said works great if I compile with TTools, but when I use AIFPC. FSX says can't read file and exits. I have to shut down FSX.exe 32 manually tho.
Also file Compiles with no errors using AIFPC.
AFIPC.exe file date is June,18,2007

I cannot repeat the problem here.
Can you post a screenshot of the error?
To which airport you go? At which time?

[gadgets]

Peter, I can confirm that the two problems I reported, i.e., output window and FSX day of week, no longer exist.
Thanks
Don

[garfield_x]

Peter, I can confirm that the two problems I reported, i.e., output window and FSX day of week, no longer exist.
Thanks
Don

:eek: ur sure?? :D

I will wait till you find another one :p

[Joe W]

Where can I find this program, AIFPC? I have looked all over FSDeveloper and on your site for it.
Thanks
Joe W.

[garfield_x]

Where can I find this program, AIFPC? I have looked all over FSDeveloper and on your site for it.
Thanks
Joe W.

4 post above yours, there is a link in the post itself.

[Joe W]

Got it , Peter.
Thanks
Joe W.

[Mace]

Peter,

I am curious. Before you posted AIFPC.zip in Post #57, where could AIFPC have been obtained? :)

RB

[garfield_x]

:) In one of my previous posts.

[JohnG]

Hi Peter,
It might be a good idea for us old duffers to go back to your first post in the thread and point out that it can be found "somewhere down near the end of the thread", as you are reloading it down there each time you change it. Would have saved me many minutes of fruitless searching through the development area:D

[garfield_x]

Hi Peter,
It might be a good idea for us old duffers to go back to your first post in the thread and point out that it can be found "somewhere down near the end of the thread", as you are reloading it down there each time you change it. Would have saved me many minutes of fruitless searching through the development area:D

Or put the download in te first post :)

But i need to do some documentation and then i think i wil release it on AVSIM.

[Mace]

:) In one of my previous posts.

I looked though all of your previous posts, twice, and did not see it. ;)

I must be losing my skillz.

[JohnG]

Or put the download in te first post :)

But i need to do some documentation and then i think i wil release it on AVSIM.

Darn, I didn't get time to "beta" it. Better luck next time!

[bkircher]

what does it mean when i get this error?

error compiling aircraft file. aircraft030528.txt is not an aircraft file?

im a noob at this new tool.

thanks for the help!

[Emile]

Hello,
in my opinion the name of the file must be Aircraft 030528.txt
There must be a space or _ between Aircraft and the "rest" of the name.
Hope it helps.

[xr219]

Hi Peter,

I sent you an email last week regarding some problems with memory errors using traffic bgls compiled with AIFPC.

I sent the same files over to DanHK who is also using FSX. He compiled the bgl from the text files which I sent to him and emailed me back the traffic bgl. this one works perfectly. There is no difference in file size of the two compiled bgl.

I'm pretty sure Dan, is running Windows XP, but haven't been able to confirm as he seems to be away. I'm on Vista x64. I've just created a virtual PC and loaded XP onto it. I'll test AIFPC on there and report back.

[xr219]

It is indeed the x64 problem. As Dan pointed out you have to specify the processor type at compile time, so that seems to be the trouble. Never mind though, I have my XP Virtual PC which has been merily comipling traffic all afternoon.

Thanks for a great tool!:D

[garfield_x]

Seems that i have to make a x32 and x64 program for this.

[Regulate]

I cannot seem to get the aircraft to show up in FSX using the AIFPC compiler. I have experience using TTOOLS, and never had a problem, so I can't figure out what I am doing wrong.

I am using AIFPC version 1.2007.6.18. I am running FSX in Vista Home. Right now, the only AI traffic I have is all from World of AI. When I use the WOAI installer, I install into the "target" FSX, and it works fine. So I have several WOAI bgl files in my scenery file that work.

Now, when I try and compile an FS9 flightplan into an FSX bgl file using AIFPC, and place it in the FSX world/scenery file, it does not show up in the sim. Should the compile target in AIFPC be FSX? FS9? I have the boxes checked "convert fs9 airports to FSX" and "renumber fs9 days to FSX days". I have tried both ways. The flightplans I am trying is for ExpressJet. I copied the aircraft title line and placed it in the aircraft text file like this

// ExpressJet Airlines
AC#6177,200,"EvolveAI ERJ-145XR ExpressJet Airlines"

This is the exact title of the aircraft itself. Then I compile the flightplans (tried both for FSX and FS9). Both compile just fine. I have tried putting each bgl file into the sim, but the aircraft are a no show. I have plenty of AFCAD parking at the test airport KONT, which is their hub. The parking spot radius is fine, and BTA is the parking code in the aircraft config and in the AFCAD.

Any idea what I am doing wrong? Since I am using these plans in conjunction with WOAI plans, should the target be an FSX.bgl since I am flying in FSX?

Thanks
Brian S.

[GrahamS]

Hi Brian

You have given the answer to your problems in your own post. You have WOAI aircraft showing up, but clearly you don't realise that WOAI use ttools FS9 type traffic files, not native FSX traffic files. So your WOAI traffic files are over-riding your AIFPC converted files which are not showing. The way forward is either stop using AIFPC, or convert the WOAI traffic files using AIFPC to FSX standard.

FSX will only show one type of traffic file at any one airport, so if you have an FS9 traffic file active then no FSX type traffic will appear.

[garfield_x]

Graham is right. You cannot mix FS9 and FSX type BGL files.

But yo can easily convert all your WOAI files into FSX. If you do not let AIFPC add an FSX to the file name, the WOAI installer still can delete the file if you are delete an airline.

Only be sure to recompile new WOAI bgl files when u install new or updated packages.

We are busy to look to produce native FSX files for the WOAI packages, and there will be an update feature for already installed BGL files.

[Capt Fuzzy]

Thank you Peter!

I'm downloading now. Always appreciate new tools.

AlexI only got one question, downloading it from where?
I see no links for it here any where...

[colin_d]

Graham is right. You cannot mix FS9 and FSX type BGL files.

We are busy to look to produce native FSX files for the WOAI packages, and there will be an update feature for already installed BGL files.
Hi Peter,

Eagerly awaited! That will save me a lot of converting work!
AIFPC is manna from heaven!

Regards

Colin

[Shrikharan]

I just migrated from FS2004 to FSX and just got to know about this program. Where to I place the BGL output file after compiling to FSX format?

Does this totally replace the existing FSX traffic or does it adds to the default FSX traffic?

If the file replaces the entire default traffic then how do I add to the existing traffic instead replacing it with the compiled version.

Many thanks

Shri

[ugo1]

Hi

I'm trying to compile the schedule under Vista 64 bit and when I try to load FSX I have an error message saying that is impossible to read the file. It occur when enable the directory where are store the traffic files (all in FSX format) compiled witjh vista 64 bit

Regards

Ugo

[Shrikharan]

Please help. I am able to compile and decompile with the AIFPC. I decompiled the trafficAircraft BGL file, from the FSX/scenery/world /scenery folder and added an aircraft into the AircraftAircraft decompiled file thus:

AC#120,477,"Airbus A380-800 Sri Lankan"

Then made a flight plan by adding to FlightplansAircraft file the following line:

AC#120,4R-MGX,34%,8h,IFR,00:21:00,03:18:37,320,F,0438,VIDP,0 4:21:00,07:18:37,310,F,0439,VCBI

And recompiled and then placed the new TrafficAircraft_FSX BGL file into its proper place back to the FSX/scenery/world /scenery folder

But my aircraft did not appear at the VCBI airport at or before the departure time (at 00 hours 21 minutes). Where did I go wrong?
Thanks

Regards
Shri

[xr219]

Hi Ugo,

The program isn't compiled for x64 so doesn't run properly. I use a 32bit XP Virtual machine, which runs in a Microsoft Virtual PC environment on my Vist x64. I then copy the copiled machines from one to the other.:)

Hi

I'm trying to compile the schedule under Vista 64 bit and when I try to load FSX I have an error message saying that is impossible to read the file. It occur when enable the directory where are store the traffic files (all in FSX format) compiled witjh vista 64 bit

Regards

Ugo

[ugo1]

Hi Ugo,

The program isn't compiled for x64 so doesn't run properly. I use a 32bit XP Virtual machine, which runs in a Microsoft Virtual PC environment on my Vist x64. I then copy the copiled machines from one to the other.:)

Hi,

I solved using the Win Xp partition for now. :)

Ugo

[jordanal]

Seems that i have to make a x32 and x64 program for this.

I too now have FSX crashing on AIFPC generated bgl's compiled on a newly rebuilt WinXP_x64 rig. I have already let Peter know through e-mail communiction as well and confirmed that it is my x64 environment.

Passing through the forum, hoping for an update, the quote above made me wonder; if a x64 switch is needed for the compiler, couldn't a simple option be added to the AIFPC UI that allows the user to select/enable x64 compatibility and when checked, the proper switch is supplied to the compiler? I don't pretent to be a developer, nor imply the ease of integrating such options, just wondering aloud if this was an alternative to supplying a seperatly (x64)-compiled program.

Since converting to WinXPx64, which runs great, I now have to copy the decompiled files over to my wife's 32-bit Vista laptop, compile them, and send the converted bgl's back to my FSX (x64) machine. It works, but at the rate WoAI is dropping packages lately, it is a nuicance.

Man, the conviences of things we miss when upgrading OS's... Like the 'ol saying, you never really appreciate the little things in life, until their gone.

[garfield_x]

Seems that i have to make a x32 and x64 program for this.

AIFPC- AI FlightPlan Compiler/Decompiler V2010 released.

This version can be used on X86 and X64 OS versions.

This new version can be downloaded from http://aifs.pvdveen.net/

[scott967]

Thanks for the update. Does this mean work is coming on ACA2010 :)

scott s.
.

[cooldude]

:(:confused:mcafee site advisor says its malware