April 21, 201214 yr sorry for asking the same question as above, is this the one that happens with an add on that out of the blue goes off track and holds into circling pattern? Thanks in advance
April 22, 201214 yr Author ok, i have completey given up hope. the sim that i have been adicted to for years i can no longer use. i have tried everything to no avail. by placing the magdev file in its own scenery folder and placing it at the top of the library seems to have fixed one problem. while sitting on the ground lined up with the runway, the DG or ND now shows correct runway alignment and heading. before the two did not match, now they do. however once airborne everthing is incorrect. flying any aircraft with a ND moving map display (i.e. PMDG 747, ifly 737, etc) the map is incorrect. the ND is in track up mode (which is correct) but in order to track the course (the magenta line should be straight up on the display) you have to have 15 degrees of crab (no wind). so in order to keep the aircraft symbol in the course, the course is misplaced (not straight up and down). i have also tried the flight1 repair tool with no success. have no idea else what else to do. very very frustrating. David Myers
April 22, 201214 yr The advantage of putting a copy of your original file at the highest level is that, like almost all scenery files, it will over-ride any lower files and thus over-ride any scenery that has put modifications in and stuffed your system up. It saves spending a lot of time identifying the culprit. John It doesn't "override" other scenery files because it is a like for like replacement and therefore should reside in the same directory as the original having replaced it. And, therefore if it "does cause problems is easily replaced by the original supposing that you have backed it up! vololiberista Super VC10 into LOWI with PF3 at a cinema near you https://www.youtube.com/watch?v=298UDyNmgUA
April 22, 201214 yr ok, i have completey given up hope. the sim that i have been adicted to for years i can no longer use. i have tried everything to no avail. by placing the magdev file in its own scenery folder and placing it at the top of the library seems to have fixed one problem. while sitting on the ground lined up with the runway, the DG or ND now shows correct runway alignment and heading. before the two did not match, now they do. however once airborne everthing is incorrect. flying any aircraft with a ND moving map display (i.e. PMDG 747, ifly 737, etc) the map is incorrect. the ND is in track up mode (which is correct) but in order to track the course (the magenta line should be straight up on the display) you have to have 15 degrees of crab (no wind). so in order to keep the aircraft symbol in the course, the course is misplaced (not straight up and down). i have also tried the flight1 repair tool with no success. have no idea else what else to do. very very frustrating. I have noticed the same thing with the iFly 737. But if I use a basically similar ND in the LevelD 767 or Flight1 ATR it tracks perfectly. What I find with the iFly 737 (don't have PMDG 747 sorry) is that everything performs exactly as it should except the visible tracks on the map display don't perfectly line up with the actual track the aircraft is flying. For me it's no big deal - it's a small discrepancy and as far as the sim is concerned, I'm on track. If it gets me to my destination, it's working! :) The real issue is the one you've solved - if you are sitting on the runway and the runway heading and your aircraft heading is the same, you're good to go... My guess is that the discrepancy you're seeing with the 737/747 has to do with the sim using different (older) data to the data being used by the specific FMC of those aircraft. Maybe someone else can comment? I'm really a steam gauge kind of guy
April 22, 201214 yr The PMDG fs9 models are sensitive to the correct registry entry path for FS9 as fixed by the flight1.com registry entry as previously provided here as a link to a tool. I don't know about the ifly but make sure your fsuipc3 is up to date from here: http://forum.simflight.com/topic/66139-updated-modules/ in case the PMDG installed an earlier version. Some models have a true/magnetic heading switch for using true headings within polar latitudes. For navaid landings problems look at this but consider pros and cons: http://forum.avsim.net/topic/336155-magnetic-variation-updates-for-fs9-and-fsx/
April 23, 201214 yr Not sure if this will help, but recently I had a similar problem. With the default flight at KSEA the heading is 340 degrees. On the aircraft it showed 360 degrees. After thryng the magdec thing & many other things, I finally read somewhere that someone had had this problem after installing a new scenery. So I then disabled all my addon sceneryes & that fixed it. It took quite a while to determine which one it was but I finally did. The offending scenery was in the Middle East! I have no idea how unrelated sceneries can affect each other but the do. I would suggest try uninstalling newer sceneries first. I really hope this solves your problem - I know how frustration it can be with FS
April 25, 201214 yr Author thankd Brian. do you remember which middle east scenery was causing the problem? David Myers
April 25, 201214 yr Hi, I was the OP mentioning the MEastern scenery problem. Sorry cannot remember the exact scenery, but think it may have been some to do with Egypt and/or Jordan. This problem manifested itself whilst flying a PMDG737, the ND track display instead of being North was skewed and the plane symbol was also at some strange angle. There were some aircraft where this effect didn't appear. But in the PMDG the plane was flying arcs between waypoints. If you have the SceneryConfigEditor installed and set up. Then it's a simple trial and error procedure to identify the culprit. Initially dis-enable all scenery, excepting default of course. Set yourself up in the Cesna at EGNS for e.g and fly to EGGP, then try the same flight using a sophisticated plane, PMDG737. If you now dont have the problem, try repeating the flight in which the problem became apparant, all should be Ok. Now the tricky bit, particularly if you dont have SCE or similar. You will know which scenery you have had for a long time with no problems, so you can now go ahead and re-enable those. Try the last flight again just to ensure, the problem has not returned and then gradually re-enable the remaining scenery. As I ,over the years have had numerous problems I have a saved "Default Startup" situation saved as above ( Cessna/EGNS/clear skys/no traffic). Which I invoke whenever I'm putting new scenery or planes etc into FS and this is made to be the default flight.This ensures that if anything goes badly wrong with the new Install and FS shuts down at least it will start up again to allow investigation and i t only adds a few minutes to then goto where you want. Regards JohnT
April 26, 201214 yr I had the same problem and found that a scenery file was causing it. In my case it was an Austin Texas scenery from Mach 1. If you have this one try deactivating it. Otherwise you may have to systematically deactivate scenery to find the culprit! Good luck! Al Kaupa Digital Storm purchased 8/17/2011; Win7x64: Asus P8P67 Deluxe; Intel i7 2600K@3,9 GHZ; nVidia GTX 560Ti; 8GB DDR3 1600 Corsair Dominator; Power Corsair HX 750W; Samsung 850 EVO 500GB SSD; 300GB WD VelociRaptor; 1TB Seagate.
April 26, 201214 yr Why not just do an explorer search for magdec.bgl on your FS and scenery drives to see where those files are located and their date properties. I think that could be a good starting point.
April 27, 201214 yr I saw this problem with a scenery file in a project I was doing. You can see it with the windsock pointing in the wrong direction for the wind you set up, in addition to any aircraft mag compass. I found the file (had nothing to do with any thing magnetic or bearings at all). Thing is moving the file into different scenery folder would correct it. It looks to me like a flat-out bug in FS9. In my case the causing file was a set of water fills which I replaced by water LWM3 polys and that stopped the problem without moving files around. scott s. .
Create an account or sign in to comment