Fsbuild-2 Flight Planner

Hi to all people. I'm new in the forum so I'd like to introduce myself firs of all. I'm Riccardo from Italy.

I have the following problem on exporting for flightplan Wilco boeing 737 for FS2004. I know the problem was just discussed in other post, but seems not solved. The problem is in the output data generated from FSBuild. Let's go now:

Just keep a simple flight from Venezia to Rome Fiumicino LIPZ-LIRF.

The outputed data from FSBuild in

C:\Programmi\Microsoft Games\Flight Simulator 9\FeelThere\CustomDB

is LIPZLIRF.u10 (note the minus U) and this is the text:

[Origin]
ident=LIPZ
type=1
latitude=45.505400
longitude=12.352000
[Destination]
ident=LIRF
type=1
latitude=41.800400
longitude=12.239000
[Route]
gspd=0
countOfPoints=14
Wpt.00.ident=D041B
Wpt.00.type=4
Wpt.00.latitude=45.542900
Wpt.00.longitude=12.400400
Wpt.01.ident=D119G
Wpt.01.type=4
Wpt.01.latitude=45.456500
Wpt.01.longitude=12.519500
Wpt.02.ident=D119N
Wpt.02.type=4
Wpt.02.latitude=45.400900
Wpt.02.longitude=12.654000
Wpt.03.ident=CHI
Wpt.03.type=3
Wpt.03.latitude=45.071200
Wpt.03.longitude=12.281500
Wpt.04.ident=ROVIG
Wpt.04.type=4
Wpt.04.latitude=44.924000
Wpt.04.longitude=11.897600
Wpt.05.ident=FER
Wpt.05.type=3
Wpt.05.latitude=44.814500
Wpt.05.longitude=11.616200
Wpt.06.ident=VALEN
Wpt.06.type=4
Wpt.06.latitude=43.937000
Wpt.06.longitude=11.533200
Wpt.07.ident=RESPU
Wpt.07.type=4
Wpt.07.latitude=43.683400
Wpt.07.longitude=11.560100
Wpt.08.ident=AMTEL
Wpt.08.type=4
Wpt.08.latitude=43.220400
Wpt.08.longitude=11.608400
Wpt.09.ident=BOL
Wpt.09.type=3
Wpt.09.latitude=42.618400
Wpt.09.longitude=12.048700
Wpt.10.ident=D169X
Wpt.10.type=4
Wpt.10.latitude=42.224000
Wpt.10.longitude=12.139800
Wpt.11.ident=BOL33
Wpt.11.type=4
Wpt.11.latitude=42.075900
Wpt.11.longitude=12.173700
Wpt.12.ident=MIKSO
Wpt.12.type=4
Wpt.12.latitude=42.024300
Wpt.12.longitude=12.185700
Wpt.13.ident=LIRF
Wpt.13.type=1
Wpt.13.latitude=41.800400
Wpt.13.longitude=12.239000

it's wrong! Infact if a load LIPZLIRF in COROUTE field in the FMC then it says me ROUTE NOT LOADED. Instead If I load the flightplan in FS2004 with default flightplanner, then write LIPZLIRF on FMC and then click on FMC LSK at ROUTE REQUEST the plan is loaded into FMC correctly. So I re-save it like LIPZLIRF and FMC generates a LIPZLIRF.U10 (note the upper U and not minus u10). Now you can recall it from COROUTE and works fine. If you then open with notepad the LIPZLIRF.U10 plan this is the correct output:

[Origin]
airport=LIPZ
[Destination]
airport=LIRF
[Route]
countOfPoints=10
Wpt.00.ident=CHI
Wpt.00.type=3
Wpt.00.latitude=45.071800
Wpt.00.longtitude=12.281381
Wpt.00.via=UM859
Wpt.00.disco=0
Wpt.00.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.00.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.01.ident=ROVIG
Wpt.01.type=4
Wpt.01.latitude=44.923889
Wpt.01.longtitude=11.897500
Wpt.01.via=UM859
Wpt.01.disco=0
Wpt.01.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.01.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.02.ident=FER
Wpt.02.type=3
Wpt.02.latitude=44.814500
Wpt.02.longtitude=11.616333
Wpt.02.via=UZ902
Wpt.02.disco=0
Wpt.02.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.02.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.03.ident=VALEN
Wpt.03.type=4
Wpt.03.latitude=43.937222
Wpt.03.longtitude=11.533056
Wpt.03.via=UM738
Wpt.03.disco=0
Wpt.03.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.03.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.04.ident=RESPU
Wpt.04.type=4
Wpt.04.latitude=43.683611
Wpt.04.longtitude=11.560000
Wpt.04.via=UM738
Wpt.04.disco=0
Wpt.04.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.04.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.05.ident=AMTEL
Wpt.05.type=4
Wpt.05.latitude=43.220278
Wpt.05.longtitude=11.608611
Wpt.05.via=UL995
Wpt.05.disco=0
Wpt.05.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.05.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.06.ident=BOL
Wpt.06.type=3
Wpt.06.latitude=42.618417
Wpt.06.longtitude=12.048722
Wpt.06.via=
Wpt.06.disco=0
Wpt.06.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.06.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.07.ident=BOL33
Wpt.07.type=0
Wpt.07.latitude=42.618417
Wpt.07.longtitude=12.048722
Wpt.07.via=
Wpt.07.disco=1
Wpt.07.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAAAIAAAAAAAAAAAAAAA=
Wpt.07.trm=AAAAAAAAAAAXAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.08.ident=MIKSO
Wpt.08.type=4
Wpt.08.latitude=42.024444
Wpt.08.longtitude=12.186667
Wpt.08.via=
Wpt.08.disco=0
Wpt.08.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.08.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Wpt.09.ident=LIRF
Wpt.09.type=1
Wpt.09.latitude=41.800278
Wpt.09.longtitude=12.238889
Wpt.09.via=
Wpt.09.disco=0
Wpt.09.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.09.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=


So, Ernie can you fix them if it's not just done? Thanks a lot

Riccardo

I can't really fix it, because I don't have the Wilco 737 product.

Others tested for me, and said it worked, and that's what we went with.

If you say it doesn't work then we have to determine what in the file is either missing or what it does not like.

Again I cannot do this as I do not have the Wilco 737 product.

Its not so simple to look at the file and see what is wrong, just like that.
Its a trial and error process unless the developer provides us with the file format.

Lowercase .u, and uppercase .U makes no difference with filename, so that isn't it. Its something inside the file itself.

What I would do 'if' I had the product is manually edit the file that FSB created, compare the differences making changes, and see what the Wilco product will accept by trying to bring the FSB file more inline with the file you exported from the Wilco 737.

Some lines probably can be excluded, like for example...

Wpt.00.vnav=AAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB8AAAAAAAAAADPLV50AAAAAAAAAAA=
Wpt.00.trm=AAAAAAAAAAARAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=


That's probably binary or encioded information, we would not have anyway. so remove those first, and start from there.

One difference I do see is at the top, where it says [Origin] and [Destination]

It uses the keyword Airport= wheras FSB is using ident=

see if that nmakes a difference.

I'm willing to help, but I need someone who has the product to check and test what it will accept and what it won't accept before we can code an acceptable solution.

Regards.
Ernie.

Thanks a lot Ernie

Same Feelthere 737 export files here, they're different from the FSBuild export files.

Now have FSX SP2 installed on Windows7 RC 7100 x64, this runs really stable,

BUT Feelthere 737 new Crashes FSX when trying to load a FSBuild 737PIC export file

did change ident= to airport=

I'm having the 'known' 737PIC bug, that I can only 'Route Request' a flightplan 1 time when I load FSX, after that I get a 'missing plan' error

so being able to load a FSBuild exported plan would come in really handy

Anything you can do about this still?


p.s. After exporting the flightplan, FSBuild does Not mention this in the Log Window List (does everything else)

thx
m tjoeng

FSX SP2 FSBuild 2.3 Feelthere 737PIC WIndows7 RC7100 x64