So I should download and install "MagDec_Update.rar" before using PFE?

Obviously!! Then run your sim so that it updates. Put the update in the correct position of your add-ons. Then run makerwys then run PFE.Your problem is not with PFE. It is your own setup and your flightplan software.vololiberista

What happens if you go back to the default magdec file? And how do default aircraft behave? Make a flightplan with the default flightplanner, load it up in a default aircraft, what happens?Also, can you attach the flightplan that's showing in the capture? So the iFly .FLTPLAN file.

Hi-I went back still the same. The default aircraft doesn't have FMC so I can't check about the waypoints. However this does happen to "all" other aircrafts such as PMDG 747 and MD11.-What I did was adding the flightplan manually (by hand) into the FMC,the problem still occur.

I suggest then, if you are certain, you take it up with the PFE developer on the On-course Software forum:http://www.ocs-suppo...orums/index.phpJohn

Yes for your suggestion,I already have a topic at PFE support forum and waiting for supports over there :(

Ok I've just tried to install it again. This time it is much clearer.Install the base package and then install the Voice Pack Extension Set.After that, I don't touch anything in PFE. Just load Fs2004,start my flight by adding flightplans and then..it happens .. again.

The default aircraft doesn't have FMC so I can't check about the waypoints. However this does happen to "all" other aircrafts such as PMDG 747 and MD11.-What I did was adding the flightplan manually (by hand) into the FMC,the problem still occur.

The default aircraft don't have an FMC, that's right, but that is not the point. If you make a flightplan with the default fligthplanner, similar to the plan that's giving you trouble, and load that into the GPS Receiver and fly it fine without problems, it's an indication that the sim is fine... If even the GPS Receiver looks messed up, so is the sim or at least portions of it.Sounds more and more like a Navdata issue to me. Perhaps reinstall the various navcycles.Can you still attach the iFly plan that shows in the capture, assuming you exported it from FSBuild. Or give the plan you're inputting manually, so we can check.

Install the base package and then install the Voice Pack Extension Set.After that, I don't touch anything in PFE.

What did you do to remove it? Also, does it actually install files to the main simulator folder? Modules maybe? And older version of one? FSUIPC?

The problem is not PFE! It is your navigation data input. Sort that out and you'll be able to have a properly controlled flight.vololiberista

Do you have this prerelease installed of FS Build (or laster version)?http://www.fsbuild.com/dl/Fsbuild24017_Upd.exeIt installs over your 2.3 (if not using NAVIGRAPH it will convert 2.3 to 2.4 including the 2010 13th AIRAC Navigrah data) or 2.4 version if earlier than 2.4.0.17. There was a correction made with interpreting and exporting Navigraph data.Did you ever have FSX installed? If so check your registry FS9 path with this free Registry Checker/Repair tool from Flight1:http://www.flight1.com/view.asp?page=libraryto insure your PMDG gauges are being pointed to FS9 correctly for magdecl and other data files. FSUIPC now used this registry path for its auto installer.FSUIPC has nothing to do with planning but you can get the base version 3.99 from:http://www.schiratti.com/dowson.htmlas well as makerwys 4.41 or later if you think older versions were placed by your PFE install.Interim updates of both can be found on page links at:http://forum.simflight.com/forum/142-download-links/

The default aircraft don't have an FMC, that's right, but that is not the point. If you make a flightplan with the default fligthplanner, similar to the plan that's giving you trouble, and load that into the GPS Receiver and fly it fine without problems, it's an indication that the sim is fine... If even the GPS Receiver looks messed up, so is the sim or at least portions of it.Sounds more and more like a Navdata issue to me. Perhaps reinstall the various navcycles.Can you still attach the iFly plan that shows in the capture, assuming you exported it from FSBuild. Or give the plan you're inputting manually, so we can check.What did you do to remove it? Also, does it actually install files to the main simulator folder? Modules maybe? And older version of one? FSUIPC?

-I just check. Fs is fine,waypoints going fine so this is pretty much navdata issues.-Which navcycles do you mean? This happens to all the routes that I've tried but this is one of them.EGGD BCN N864 WAL L10 PENIL L70 BAGSO BAGSO3R EIDWIf I uninstall it in window, my FS still messed up. I have to restore my system to the point before installing PFE.

Do you have this prerelease installed of FS Build (or laster version)?http://www.fsbuild.c...ld24017_Upd.exeIt installs over your 2.3 (if not using NAVIGRAPH it will convert 2.3 to 2.4 including the 2010 13th AIRAC Navigrah data) or 2.4 version if earlier than 2.4.0.17. There was a correction made with interpreting and exporting Navigraph data.Did you ever have FSX installed? If so check your registry FS9 path with this free Registry Checker/Repair tool from Flight1:http://www.flight1.c...sp?page=libraryto insure your PMDG gauges are being pointed to FS9 correctly for magdecl and other data files. FSUIPC now used this registry path for its auto installer.FSUIPC has nothing to do with planning but you can get the base version 3.99 from:http://www.schiratti.com/dowson.htmlas well as makerwys 4.41 or later if you think older versions were placed by your PFE install.Interim updates of both can be found on page links at:http://forum.simflig...download-links/

-Yes, I have the latest version of FSBUILD :)-I don't install FSX and my registry path for Fs9 is correct.-I downloaded and ran the latest 4.45 of makerwys and also have the latest FSUIPC.

-Which navcycles do you mean? This happens to all the routes that I've tried but this is one of them.EGGD BCN N864 WAL L10 PENIL L70 BAGSO BAGSO3R EIDWIf I uninstall it in window, my FS still messed up. I have to restore my system to the point before installing PFE.

The Navigraph navcycles. Even though you have the latest versions, redownload and reinstall them, that might trigger something. As for the plan, it may be nothing, but it is BAGS3R, not BAGSO3R. At least, with 1102. I'll check it in the iFly.Edit: route works just fine in iFly 2.1 with 1102.

The Navigraph navcycles. Even though you have the latest versions, redownload and reinstall them, that might trigger something. As for the plan, it may be nothing, but it is BAGS3R, not BAGSO3R. At least, with 1102. I'll check it in the iFly.Edit: route works just fine in iFly 2.1 with 1102.

I copied this route into FSBUILD and of course had to make some changes in there for it to work (both SID and STAR)This route was fine before installing PFE.Even if I admit this fault isn't because of PFE, installing it,however, mess my FS up.I guess my luck has ended :(

I copied this route into FSBUILD and of course had to make some changes in there for it to work (both SID and STAR)This route was fine before installing PFE.Even if I admit this fault isn't because of PFE, installing it,however, mess my FS up.I guess my luck has ended :(

You wil find tht PFE will discount wypts that a. are too close together and b. Too close the strt and finish of the flightplan. Read the documentation!!!!!!!!!!!!vololiberista

You wil find tht PFE will discount wypts that a. are too close together and b. Too close the strt and finish of the flightplan. Read the documentation!!!!!!!!!!!!vololiberista

Yes I've read it,twice actually. But I don't know why it affects my aircraft's speed (look at the picture in FMC, 0.3 mach) and if it discounts waypoints then how can I managed to land when the trans are messed up

First, in FSBuild, sometimes the length of a SID or STAR label can be condensed since it is limited to 5 characters. By selecting a runway and then clicking the dropdown arrow on the destination airport STAR box you'll see the names FSB offers. In the case of EIDW STAR for 28 and 34 BAGSO3R as noted on the chart becomes BAGS3R.BAGSO3R STAR RWY28, RWY34IF BAGSO TF ROKNAFrom the current Eurocontrol chart in FSBuild becomes:Here using the 1310 NAVDATA is the exported file content (I did not export altitudes from FSB) for the iFLY737:EGGD,EIDW,,29000,,,,,,,-1,,,,,0,DIRECT,3,BCN,0, 51.725556-003.263056,0,0,319.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,DIKAS,0, 51.776945-003.259167,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,05BCN,0, 51.808611-003.256944,0,0,005.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,10BCN,0, 51.891667-003.250556,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,TALGA,0, 51.958334-003.245556,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,NIT25,0, 52.134167-003.232500,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,NITON,0, 52.553333-003.200278,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,OKTEM,0, 52.719445-003.187500,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,WAL35,0, 52.809722-003.180278,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,MONTY,0, 52.892778-003.173889,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,WAL25,0, 52.983334-003.166944,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,REXAM,0, 53.066667-003.160278,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,WAL16,0, 53.129444-003.155278,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,DOGIT,0, 53.172778-003.151944,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,KEGUN,0, 53.192500-003.150278,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,N864,2,WAL,0, 53.391945-003.134444,0,0,006.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L10,2,IOM55,0, 53.546389-003.498056,0,0,309.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L10,2,IOM50,0, 53.594445-003.612222,0,0,308.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L10,2,PENIL,0, 53.616111-003.663611,0,0,308.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L70,2,BABRA,0, 53.627500-003.945278,0,0,277.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L70,2,SOPAX,0, 53.646945-004.452222,0,0,277.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L70,2,RAMOX,0, 53.660278-004.839445,0,0,277.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L70,2,BAG13,0, 53.670000-005.147222,0,0,277.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,L70,2,BAGSO,0, 53.680000-005.500000,0,0,277.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,DIRECT,3,ROKNA,0, 53.656042-005.883031,0,0,268.00000,0,0,0,-1,0.000,0,-1,-1000,-1,000,0,0,0,000.00000,0,0,,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1,-1,17,0,-1000,-1000,0,-------------------which poorly fits the screen - I can only paste it and I don't have this model.Here is the pasted FS9 .pln format:[flightplan]title=EGGD to EIDWdescription=EGGD, EIDWtype=IFRroutetype=3cruising_altitude=29000departure_id=EGGD, N51* 22.57', W002* 43.08',+000622.00departure_position=09destination_id=EIDW, N53* 25.17', W006* 16.11',+000242.00departure_name=BRISTOLdestination_name=DUBLINwaypoint.0=EGGD, A, N51* 22.57', W002* 43.08', +000000.00, waypoint.1=BCN, V, N51* 43.32', W003* 15.47', +000000.00, N864waypoint.2=DIKAS, I, N51* 46.37', W003* 15.33', +000000.00, N864waypoint.3=05BCN, I, N51* 48.30', W003* 15.24', +000000.00, N864waypoint.4=10BCN, I, N51* 53.30', W003* 15.02', +000000.00, N864waypoint.5=TALGA, I, N51* 57.30', W003* 14.44', +000000.00, N864waypoint.6=NIT25, I, N52* 08.03', W003* 13.56', +000000.00, N864waypoint.7=NITON, I, N52* 33.11', W003* 12.01', +000000.00, N864waypoint.8=OKTEM, I, N52* 43.10', W003* 11.15', +000000.00, N864waypoint.9=WAL35, I, N52* 48.34', W003* 10.49', +000000.00, N864waypoint.10=MONTY, I, N52* 53.34', W003* 10.26', +000000.00, N864waypoint.11=WAL25, I, N52* 59.00', W003* 10.00', +000000.00, N864waypoint.12=REXAM, I, N53* 04.00', W003* 09.37', +000000.00, N864waypoint.13=WAL16, I, N53* 07.45', W003* 09.19', +000000.00, N864waypoint.14=DOGIT, I, N53* 10.22', W003* 09.06', +000000.00, N864waypoint.15=KEGUN, I, N53* 11.33', W003* 09.01', +000000.00, N864waypoint.16=WAL, V, N53* 23.31', W003* 08.03', +000000.00, L10waypoint.17=IOM55, I, N53* 32.47', W003* 29.53', +000000.00, L10waypoint.18=IOM50, I, N53* 35.40', W003* 36.43', +000000.00, L10waypoint.19=PENIL, I, N53* 36.57', W003* 39.48', +000000.00, L70waypoint.20=BABRA, I, N53* 37.38', W003* 56.43', +000000.00, L70waypoint.21=SOPAX, I, N53* 38.49', W004* 27.07', +000000.00, L70waypoint.22=RAMOX, I, N53* 39.37', W004* 50.22', +000000.00, L70waypoint.23=BAG13, I, N53* 40.12', W005* 08.49', +000000.00, L70waypoint.24=BAGSO, I, N53* 40.47', W005* 30.00', +000000.00, waypoint.25=ROKNA, I, N53* 39.21', W005* 52.58', +000000.00, waypoint.26=EIDW, A, N53* 25.17', W006* 16.11', +000000.00, Maybe you want to try to paste the iFLY plan (getting rid of any extra line ends - use Wordap in text format and use the regualr iFLY file title.fltplan formatted filename to see what it looks like on your FMC.Now, I don't have PFE (see my banner) but you can now compare the plan files to the pasted file and what you created with PFE installed in your FMC by doing some fiddling with the filename extensions. Be sure when you create the file with the data that you don't overwrite the one you have. You can see if PFE changed any of the data.Now I use the PMDG 737NG. There are two ways I can incorporate the STAR. I can let FSB expand the STAR into waypoints as I did today or I can set an option in FSB to not expand the STAR or I can choose to remove the STAR waypioints from the grid before exporting with the FSB build from grid option. This means I can import all of the plan including the STAR waypoints or just leaver in the transition waypoints and add the STAR in the FMC itself.I also noted several close waypoints in the plan of 1 mile distance. If PFE removes those does it actually remove them from the plan export or leave them in with zero distance. That would be an issue for the PFE developer to check on.Anyway you can also try the plans I pasted in here - no other way to attach files or I would have zipped them - to see if they work for you. I used FSBuild 2.4.17.I hope this helps you perhaps dig out the problem.

PFE uses default flightplans, the iFly 737 uses it own custom plans. So even if PFE messed up the default plan it uses, the iFly plan would remain the same... and it is that, that's showing as messed up in the capture... The question is then, what's wrong with the iFly plan. Manual imput -> iFly or Navigraph support. FSBuild export -> FSBuild support. I think you could also try reinstalling the iFly and its navdata after installing PFE. That may overwrite something back to normal. I mean, how many people have installed PFE after the iFly? Most of the time it's probably the other way around, so who knows...I do think we're slowly starting to beat a dead horse here.:(

@ronzie: my FS hang up when trying to load iFly's FLTPLAN, I trying to figure it out but thanks a lot for your helps :(@FJ Mike:

PFE uses default flightplans, the iFly 737 uses it own custom plans. So even if PFE messed up the default plan it uses, the iFly plan would remain the same... and it is that, that's showing as messed up in the capture... The question is then, what's wrong with the iFly plan. Manual imput -> iFly or Navigraph support. FSBuild export -> FSBuild support. I think you could also try reinstalling the iFly and its navdata after installing PFE. That may overwrite something back to normal. I mean, how many people have installed PFE after the iFly? Most of the time it's probably the other way around, so who knows...I do think we're slowly starting to beat a dead horse here.

-Yes, I wonder about that too. Manual input flightplan or from FSBUILD, the problem still occur.-I've tried to reinstall iFly and AIRAC (even FSBUILD) but still no luck.Something interesting that I've just found out. I tried to load the panel state that I saved before installing PFE and all the informations in the FMC and EICAS show up perfectly without issues. Load back cold and dark, input the same flightplan but now it's messed up.Load back again the saved panel state, it's perfect :Nerd:I will post a video soon to make it clearer

@ronzie: my FS hang up when trying to load iFly's FLTPLAN, I trying to figure it out but thanks a lot for your helps

I did say earlier the combo FSBuild/iFly/Navigraph was not 100% stable yet: http://www.fsbuild.com/forum/viewtopic.php?f=1&t=3912If you can check a plan that crashes your sim and compare it to my findings there, you may discover similarities. That's also why it's important to use the very latest build of FSBuild and not use flightplans exported with earlier versions.

Something interesting that I've just found out. I tried to load the panel state that I saved before installing PFE and all the informations in the FMC and EICAS show up perfectly without issues. Load back cold and dark, input the same flightplan but now it's messed up.Load back again the saved panel state, it's perfect

Think it's time to head to the iFly forums.:(