Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About pdavies

  • Rank
  • Birthday 06/19/1983

Profile Information

  • Gender
  • Location
    Washington, USA
  • Interests
    My family, flight instructing, flight simming, spotting, guitar, music

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. No, this is normal. While a VOR produces a lateral bearing in omni(many)directions and your VOR instrument can be adjusted to a desired bearing, an ILS produces one lateral bearing. In airplanes there isn't an instrument dedicated to the ILS - you use your VOR. There are, however, VOR instruments that only have a localizer needle and not a glidseslope needle, meaning that they could only be used for a non-precision localizer approach with no vertical guidance.
  2. Carb heat has nothing to do with visible moisture, actually. Even a small percentage of moisture in dry air can condense in a venturi in a carburetor. I will readily admit I haven't read the POH for the DC6, but in the C150 I fly any time the RPM is outside of the green arc, carb heat is necessary. This is effectively any time you are on the ground and when you are on your descent and approach. Just my two cents.
  3. No kidding - when I saw the fading I thought, no way did they model hypoxia, but sure enough - they did! Obviously the remedy is to descend or turn on oxygen, but since autopilot is on and you can't see anything to change the autopilot, that is a difficult task! If you leave the F9 button pushed on you get a glimpse of the cockpit and can toggle between F9 and scrolling around the view until you can see what you need to push. Leave F9 pushed in and you should be able to move controls a little bit to begin a descent. I got down lower and sure enough the cockpit went normal again. Obviously this isn't how real hypoxia works - once you're out you're out, but hey, I didn't feel like exiting the sim and starting again!!
  4. Yep, just had the same problem. Easy enough, if you know to check for it!
  5. Spend my money wisely!! You earned it, as always! I haven't even downloaded it but I will already thank you for enfusing your love for this bird into the simulation. We will enjoy it for many years, and many flights to come!
  6. Just my two cents, but we need a good CRJ. They're everywhere in the real world, and no where in the sim world. The airlines in the US are pulling profits again because of (and at the expense of) the regionals. They're pivotal. And when you think about it, they're pretty awesome little planes. Just my humble opinion.
  7. Update: Uninstalling the 777 as recommended by PMDG, reinstalling, then deleting the RAAS folder in the root P3D folder allows the sim to start. Haven't tested RAAS yet, but I have a feeling it won't work.
  8. Hey Everyone - I've had a ticket open with the guys about this, but I want to see if anyone else has had the same problem. As normal, I'm at my wits end! I had everything working fantastic with my older version of P3D, and then out of nowhere I tried to open it again for my next flight and I got the BEX error. Opened the ticket, we came to the conclusion that it was time for a fresh install. So I decided to upgrade to P3D 3.2 to get the better performance, so I have been working on the fresh install today. I install P3D, everything works great. Install the 777 and now I'm getting the BEX error. Nothing else installed, so in my mind it has to be the 777? I'm out of ideas? Here's the text for the BEX error: Problem signature: Problem Event Name: BEX Application Name: Prepar3D.exe Application Version: Application Timestamp: 56df48ce Fault Module Name: RAASPRO.dll Fault Module Version: Fault Module Timestamp: 55eeb0fc Exception Offset: 00013fd8 Exception Code: c0000417 Exception Data: 00000000 OS Version: 6.1.7601. Locale ID: 1033 Additional Information 1: c060 Additional Information 2: c060bb203b05c28a11d4a20d2498325a Additional Information 3: 4078 Additional Information 4: 407846c6f1d517c89132c172e2e28516 Because the fault module name is RAASPRO.dll, it really makes me think it's a RAAS problem. Previously I had installed the RAAS update while troubleshooting the 2.0 version but it didn't do anything. I think it must be a wacko unique problem because this shouldn't happen with a fresh install and a new download from PMDG. HELP! Thanks, guys!
  • Create New...