Ok after alot of messing around it seems to be working. I repaired some registrys and deleted lots of unused files and seems to have done the trick. I hope this problem doesn't happen again because it's been a pain in the backside. Thanks too everyone who helped with suggestions.Sam

Ok after alot of messing around it seems to be working. I repaired some registrys and deleted lots of unused files and seems to have done the trick. I hope this problem doesn't happen again because it's been a pain in the backside. Thanks too everyone who helped with suggestions.Sam

Could you be more specific as I'm having the same problem

Adding to what John said earlier, the default GPS receiver gets its info from the sim. So if you have an airport with a runway at position so-and-so, then the GPS receiver should show your position correctly if your aircraft is sitting at one of the runway ends. Navigraph gets its info from the real world. Usually, the sim is pretty accurate, but in case of the capture in the opening post, it could just be that the Afcad is wrong and that iFly shows the runway in the correct position... So the solution would then be to move the airport/runway to the correct real world position with your Afcad editor of choice.

Also, whenever you run into problems that may be .bgl related, it may be a good idea to delete all scenery.dat files from your FS installation. Sometimes one or more end up getting corrupted (when they can't keep track of (small) scenery changes for example) and then they can cause all kinds of weird things. Upon restarting the sim, it will rebuild the files and in doing so solve .dat file related problems.Jure mentions moving the magdec file. Well, that move will trigger a rebuild of certain scenery.dat files (source folder and destination folder). So moving it may not have been the fix, but instead the resulting rebuild of possibly corrupted scenery.dat files.This is no exact science, but it's helpful to know when it's time to troubleshoot.:(

Thanks Mike I'm following your suggestions :( Also trying to reinstall iFly :(

If the FS registry path gets screwed up some how, it could affect navigation systems, try and run the Flight1 Registry repair Utility.http://www.flight1.com/view.asp?page=library

After uninstalling any complex game/sim, and prior to re-installing, it should be routine behaviour to run a registry cleaner (Ccleaner is a good free one that clears out other orphan files as well). Games & sims can leave all sorts of clutter behind that affects how the re-installed version runs. It also avoids having to manually poke around in the registry..:(

I'm almost giving it up. It's been a week since this happens and I still can't find a way to solve it. At PFE the support goes very slowly and I still can't find my answers over there yet.It makes me thinking I have to either install PFE and not using iFly or the other way.

If PFE messes up iFly and that's a big if, why not install PFE first, then the iFly 737? Worth a try.

If PFE messes up iFly and that's a big if, why not install PFE first, then the iFly 737? Worth a try.

Thanks I'll try this and report back.At iFly forum one member confirm their iFly works well with PFE. So it's another dead end to me :(

Thanks all and especially to Mike for your help :( I can't solve this so I'm going to reinstall my FS to fly again, should take about a day but should be lots faster than solving this "weirdo problemo":(

I wish you well with that endeavor.:(

Thanks all and especially to Mike for your help :( I can't solve this so I'm going to reinstall my FS to fly again, should take about a day but should be lots faster than solving this "weirdo problemo":(

Just a polite hint . . . I know it is easy to be wise after the event.System Restore is not a backup system, although you have been regarding it as such. As soon as you have installed your fresh version of FS, take a proper backup. And when you have added your extras, do the same again. Do so regularly, too. It is much easier to solve problems with a proper backup to fall back on.System Restore, as far as I understand, only restores your configuration/driver files to an earlier condition - it doesn't change/add/remove other files so would leave your Flight Simulator in a condition that will not be as it was before, and could cause problems. I don't believe SR is intended for use in any situation other than when your Windows setup is not working properly.Hope all goes well this time, by the way.John

Just a polite hint . . . I know it is easy to be wise after the event.System Restore is not a backup system, although you have been regarding it as such. As soon as you have installed your fresh version of FS, take a proper backup. And when you have added your extras, do the same again. Do so regularly, too. It is much easier to solve problems with a proper backup to fall back on.System Restore, as far as I understand, only restores your configuration/driver files to an earlier condition - it doesn't change/add/remove other files so would leave your Flight Simulator in a condition that will not be as it was before, and could cause problems. I don't believe SR is intended for use in any situation other than when your Windows setup is not working properly.Hope all goes well this time, by the way.John

Oh so that is what it does :( So now I'm more confused about the cause of my problem because everytime I use SR,it works. Oh by the way, SR also make changes in regedit.exe right? /Thanks for your hint on backing up Fs2004. You meant backing up the whoole folder Flight Simulator 9?

Preferably you install FS9 to a separate partition if not drive. If you want a proper backup of that, make an image using a program such as Acronis' True Image. Or make sure you have a complete copy of everything. Personally, I use SyncBack by 2BrightSparks to maintain an exact copy of all my important data on an external drive.