CFII_Carl

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Turns out the knowledge base over at PMDG solved the issue. Just needed to ensure the PMDG 737NGX was the first and only aircraft loaded in memory at the start. Everything is now working as best as I can tell. Thanks, Carl Wilson Here's the link: http://support.precisionmanuals.com/kb/a112/important-and-nearly-foolproof-steps-to-running-your-pmdg-product-in-prepar3d-v3.aspx
  2. CFII_Carl

    Prepar3d 3.1 and 737NGX

    Yes...that worked. Thank you.
  3. CFII_Carl

    Prepar3d 3.1 and 737NGX

    Good morning...just wanted to let everyone know that I upgraded to Prepar3d 3.1 last night via first deleting the client and content portions of Prepar3d and then reinstalling the updated 3.1 client and content MSIs. All went well, except now the 737NGX is not responding to several "click spots" and I can't release the parking brake either w/ the keyboard, the click spot, or my saitek rudder pedals. Everything work great prior to the 3.1 update. Any suggestions? Carl
  4. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Good idea!
  5. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Sure did...all other aircraft the brakes work as advertised...just not the PMDG 737NGX. Just discovered that I'm also have some "click spots" that no longer work.... LOL...sure did. Seems like the 3.1 update certainly messed w/ the 737NGX.
  6. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Are you using any Saitek products? If so what drivers are you using to control them?
  7. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Yeah...I'm afraid I'll end up doing a complete reinstall as well. I was just curious to see if anyone else was having the exact same problem and how they fixed it.
  8. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Nope...I can see the brakes (red letters) flash, but then it's right back to parking brake on.
  9. CFII_Carl

    PMDG 737NGX and 3.1 Update

    Last night I installed the update for 3.1 (only client and content) and everything seemed to go ok...no big issues to speak of. Then I attempted a flight in the PMDG 737NGX and was going through the preflight process and once I was ready for pushback, I attempted to release the parking brake and it would not turn off. The cockpit click point is there and works, but the brakes will not release, additionally each time I press the brake pedals (Saitek) the brakes (red letters) will flash but immediately come back and stay on. The brakes and everything else works great in all my other add-on aircraft. Any suggestions? Carl
  10. Peter, I tried this and it is now working...the latest scenery I added was the new KAUS by Imaginesim--not sure if that's the culprit or not, but for now...all is working again. Thanks for the suggestion! Carl
  11. Howdy all, Seems like I've run into a bit of a problem and am not sure as to what's causing it. I mostly fly the iFly 737 and have recently updated my AIRAC data to 1411 through Navigraph and it worked as it always does. Now, however whenever I fly I notice that my aircraft heading and the magnetic heading of the runway assigned do not match up...sometimes off by as much as 10 degrees or more....and it doesn't just happen w/ the iFly...it happens w/ all aircraft, just more noticeable in the iFly due to the FMC route is off quite a bit. I have since changed my intersection data and magnetic variation data by changing the magdec.bgl from the latest back to the original off the FS9 CDs. The crazy part is once I change it...everything works as advertised for that sim session only. Once I quit and restart flight sim, the error comes back no matter which magdec.bgl or AIRAC file I'm using. The workaround I'm using now is to change the magdec.bgl prior to each sim session in order for things to function correctly--I've never had to do this before and I'm not sure as to what's causing it. Any ideas? Carl