Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Posts posted by clearjet

  1. I know this is an old thread, but I'd like to add my 3 cents...


    Many CTD's are caused by Access Violations pertaining to .dll files.  When you get a CTD look in the Event Viewer/Windows Logs/Application section for an Error. If you see one something like this,

    Faulting application name: Prepar3D.exe, version:, time stamp: 0x60db69bf
    Faulting module name: mso20win32client.dll, version:, time stamp: 0x61847493
    Exception code: 0xc0000005
    Fault offset: 0x0000000000071021


    That is an Access Violation as indicated by 0xc0000005.


    I had these constantly.  Here is my fix.

    Right-click the Start button and go to System.  On that page click on Advanced System Settings on the right side. Click on Settings in Performance.

    Click on the Data Execution Prevention tab.

    Windows defaults to the first option for "essential Windows programs".  Select "Turn on DEP for all programs and services except those I select".


    That was my fix for P3D v5.2.22.27615 in Windows 10.


  2. On 4/14/2020 at 3:22 PM, breakinghbts said:

     But the bottom right option is something like step climb altitude. I use 2000 as I understand thats the US step climb profile. The rest of the world uses 4000? i believe. 


    The only time there is an issue with this, is if its a VERY long flight, and ur a/c is loaded with fuel. The auto step climb will not climb past the MAX operating alt, listed on the CRZ page of the FMC. So if by the time it gets to say 380, ur max is 390.then later in the flight ur max changes to 41 or 420, the a/c will no longer step climb. (this 'issue' hasnt affected my flights in any significant way)



    For the Step size, just put ICAO.  The system will calculate the proper step size taking into account max altitude and other things like going from FL390 to FL430 which is a 4000 foot step.

  3. On 1/3/2017 at 12:55 AM, 77west said:



    Not nice to get personal or point out nationality.




    Any explanation of exactly what the problem is, apart from "it does not work" ?? The more info you give, the more likely someone can help you.




    No, I and many others use GSX with no problems with the 777, 737NGX, and many other addons.

    Wow...  you must frequent the FSDT forums because you did exactly the same thing...

  4. They go off at 10K as normal after TO, but they come on at 18K on the descent.

    I verified the setting in the CFG for "Fixed Landing Lights: 10K Feet" but I did just notice another setting of "SOP2 Force TL Flow to 10K" and it set to NO.  I just set it to Yes and we'll see what happens.



  5. Hello,

    After doing the RTFM for both FS2Crew and PMDG, I was wondering if there is a setting that I am missing regarding the landing lights activating above 10K. 

    Shortly after descending through the transition level (FL180) and pressing STD, the FO turns on the landing lights.  I see the orange 10K/TL procedure occurring in the window.  

    I have verified that the option is set to 10K in the PMDG options. I don't see the issue in the 777 or 747.

    P3D v5.2.22

    Thanks in advance, 


  • Create New...