sshotick

this fixed the issue, thank you :)just out of curiosity, how did installing a new repaint affect this? i didnt even touch the contact points when installing the repaint...just seems kind of odd to me that it would work fine before but not after, and then be an issue with something i never even changed.Sam

i know, im dredging up an old topic, but now i have the same problem and the feelthere CRJ forum no longer exists....so what is the solution to this issue?Sam

I've just about had it, it worked fine at first then all of a sudden i start getting fatal exception errors on the splash screen. I've tried fresh installs in a completely different place and in the same place, ive tried "repairing" the installation which does nothing as far as i can tell...and i really miss FSX...any ideas whatsoever would be greatly appreciated here is the error text:EventType : BEX P1 : fsx.exe P2 : 10.0.60905.0 P3 : 44fd0a92P4 : multiplayer.dll P5 : 10.0.60905.0 P6 : 44fd0f33 P7 : 00047c21P8 : c0000409 P9 : 00000000Hope someone can explain it or at least point me in a direction on where to look for a solution, thanks much!SamI've found several people with the exact same error message but no one has offered a real solution other than one related to a program called TuneBite, which i dont have...

in METARs and such, clouds are reported in AGL as opposed to MSL, but flight simulator seems to put them at MSL. I was flying of south central Canada, which is rather flat and ActiveSky had registered some low clouds, something like SCT007, and the clouds were sunken into the ground...i realize the weather system of flight sim is rather complex, but is there some way to change this so that it reads METARs correctly or is it pretty much something to live with?Sam

i dont mean to resurrect an extremely old topic, but i seem to be having this issue too with FS9...fresh off the skewed ND problem, its not real time that im having an issue with...its the speed of time versus the flight sim clock. it started when i did an EWR-MCO flight in 1.7 hours (no traffic, no wind, so i thought i might have been lucky)...but now im flying a much longer flight, KMCO-EHAM and ive covered almost 3000 miles in 4 hours (by the FS clock)...how can this be? then i did a little counting and the difference between decimal minutes is not 6 seconds as it should be...its more like 9 seconds. just to confirm i tried setting the timer back to 0 on the clock. and sure enough it counts away minutes each time the second hand goes around, but the flight sim clock takes about a minute and a half of real time to go 1 minute.this is all on sim rate 1X, i have FSUIPC registered, and recently fixed the now-famous skewed ND problem with the registry fixer from Flight1 as suggested here, that works beautifully, but could the program have edited something else and change the time rate or something?

woohoo! still dont know what was wrong with it, but it works now. my 737 and 747 are sprung from the hangar.Thank you times a million :)

i sent in my report tooSam

FS9 versions too? i can email it to you tonightSam

yeah, ive had the problem with FS9, both the 747 and 737 have the same problem, i havent tried the 747X (and at this rate wont be)...i got several months of enjoyment out of both aircraft, so much that they were all i would fly. the last time either of them worked was just before thanksgiving with the 0711 AIRAC file. I never got the 0712 AIRAC as i was out of town and away from my flight sim computer...when i got back i upgraded to the 0801 AIRAC right off the bat, and then went to fly and the problem was there. i then tried rolling back to an older AIRAC i had and got the same issue still. im not sure if the AIRAC is related, but its the only thing that changed between working aircraft and non-working aircraftboth my 737 and 747 have remained grounded ever since...

ok, we get your point that you think its add-on scenery...and it may very well be for some people, but what about those who dont have add-on scenery installed? i think we need to quit dodging the real questions and stop placing blame on supposed add-on scenery.heres the real question...how do we fix this issue if we dont use add-on scenery/AFCADs/etc?as stated before, other planes with FMCs work just fine, without issue, working off the same magdec.bgl file (i presume). this is an issue with PMDG aircraft ONLY...and happens on both the 737 and 747 for FS9, as well i understand the 747X which i dont own or have tried. the LDS 767, or Flight1 ATR or MD-80 are not affected at all and work beautifully.

ok, but what about those of us, like ive asked before, who dont use add-on AFCAD's? and the only add-on scenery i use is FS Global and the aircraft worked just beautifully hand-in-hand and in perfect harmony for as long as i had them UNTIL i installed the 0801 AIRAC file (up from the 0711 file)...i then rolled back to an older AIRAC file and the same problem persisted....the AIRAC is the only thing that changed between working fine and not working at all, the problem literally came up overnight.Here are a couple pictures, i set up a flight (just to/from and a departure runway for simplicity) from KSEA-KORD...here i am in the PMDG 747 FS9 version at the end of 34R at KSEA...everything looks nominal, right?then here i am after a roll to the other end, as you can see im still on the center of the runway, but check out my track? according to it im well right of the centerline, or even the runway for that matter...obviously im not.

happens no wind, also i should note that it happens on both the 737 and 747, but not any other FMC-equipped planes (LDS 767 and F1 ATR both work with the same AIRAC just fine) i dont have the 747X, so ive only got experience with the FS9 versions.ive tried uninstalling FSUIPC as someone suggestedi tried updating the magdev.bgl file with one on avsim, same problem to the same extenti can put just a basic to/from and runway in the fmc...start out at one end of the runway in the center, push the throttles up and just go straight down the runway but the map will show me right of centerline by as much as a mile or 2 by the time i reach the end of the same runway. ill post pics tonight when i get back to my fs computer

and then there are those of us (aka, me) who only have one piece of add-on scenery (FS Global) and at one time it worked problem free...in fact it worked problem free in combination with each other for a couple years....this problem literally came up overnight after i installed a new AIRAC (0801), i then rolled back to an older file and still had the issue...and i have ever since.im still pretty amazed there hasnt been a word on the issue from PMDG

i must agree, the LDS 767 and Flight 1 ATR both work just fine for me, its only the PMDG 737 and 747 for FS9 (i dont have the 747X, so i dont know about that one)ive tried everything short of a re-install of FS9 and the aircraft...i tried removing FSUIPC as someone suggested, i tried the updated magdev.bgl file in the avsim libraries, i tried disabling all add on scenery (the only ones i have are the updated time zones and FS Global, and it worked fine in harmony with both those at one time)i think enough people are having this problem and theres been no word whatsoever from PMDG regarding the issue...wheres this so-called "support" in this "support forum"?

it is rather odd that we havent heard a word from PMDG on any of the threads on this issue. both the 737 AND the 747 worked just perfectly until just after the new year and the new 0801 AIRAC. They were all i was flying on flight simulator, i even took the 747 around the world without problems...i rolled back to an older AIRAC file and that didnt fix the problem.as i stated on the other current thread...im beyond frustrated at this point, and even moreso at the lack of input from PMDG themselvesthe other payware aircraft i have run just fine on the newest AIRACs...(Level D 767, and Flight 1 ATR)...i dont understand it

im having the same problem and posted a previous thread about it, to no avail....i tried downloading the .bgl file from avsim as well, and the problem still exists. im beyond frustrated and have been forced to keep both my 737 and 747 in the hangar...prior to this they were all i was flying. it started for me with the first AIRAC of this year, and has continued since then. the previous AIRAC i had installed was the November 2007 update, and even rolled back to one prior to that and the problem still existed.Sam

this looks like another case of a misaligned ND...see our outher posts on this board about it...i discovered earlier that with my runway on the ND (a runway i am sitting in the middle of) i would start my takeoff roll and by the time i got to the other end of the runway, even though i was right on centerline, the ND showed me far to the right of the runway edge even...as for a solution im at a total loss, this is the 3rd place ive posted the same issue and nothing has worked yet....not even a complete reinstall and a rollback of my AIRAC

>If it helps, though, I'll say that we've paid some more>attention to this issue for our upcoming Service Release, so>it should feel a bit tighter now.what about the 737 having the same problem? i dont have the 747X and im having the same problem. I'm running both the 737 and the 747 for FS9

thats the thing i havent added any scenery or anything...the only add-on i have scenery-wise is FSGlobal and theyve worked hand in hand for quite a while, this problem didnt arise until i installed the latest AIRAC. then i tried rolling back to a previous AIRAC and the same problem, so something in there changed...last time i flew it before christmas it worked fine and then when i got back i immediately installed the AIRAC and the problem showed up...nothing else changed in between thereif it were a magnetic deviation problem, wouldnt it have come up gradually over years of time and not just in the matter of 2 months of AIRAC updates?i also just tried the 747 again and apparently it too has caught the bug...

I'm having the same problem i think...i installed the latest AIRAC (0801) and all of a sudden the plane is misaligned, i didnt change anything else. I have the 747 too and it works fine as you said, and did install them in order. I've attached a picture of what my panel looks like when this happens...a couple notes on the picture... the autopilot is on, but at the time when i took the picture i was troubleshooting the problem and had CMD B on and just for testing reasons, winds are totally calm. there is no offset put into the FMC either.what happens is that the plane will not track the desired path, in the picture the plane is actually flying towards DBS, but will not cross or touch the pink line. as it nears DBS, it will make a right turn to fly over the fix and then turn back to the left to fly to the right of track to the next waypoint, and so on...the distance i am off track varies usually anywhere from 2-10 NM. ive posted this same issue several places to no avail so far so any ideas would be appreciated greatly :)Thanks,Samhttp://forums.avsim.net/user_files/183828.jpg

i had a very similar problem at STL when landing today. its not that the headings and courses are different, its that the ILS doesnt even lead to the runway...i was flying the 12L ILS there and flying it down the chute perfectly, but ended up having to pull up quickly after realizing it was leading me to a point somewhere north of the airport, parallel to the path i was supposed to be on. i had to pull up the GPS, and zoom in, and only then did i realize what a complete mess STL is, and i assume its not the only one. ILS's leading everywhere, and only 1 of them leading to a runway (the 12R loc happened to lead to 12L, probably by sheer coincidence)