Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

Crashing on Approach

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Crashing on Approach

    Hi everyone,

    I've had two instances now where my QOTS is crashing (the aircraft, not the software) on approach. Yesterday it was just after ToD and today turning on final. The aircraft appeared to me to be properly configured (flaps, gear, IAS etc) but it suddenly switched to the external view and reset the scenario. There was no message on the cut screen before resetting (like "Crash" or "Overstressed Airframe").

    This is very frustrating. Does anyone have any ideas?

    Cheers
    Warwick Finch
    YSCB

    #2
    Hi Warwick,
    Unforunately, there is insufficient information here to help you. You need to include as much information as possible about the Sim version, the aircraft and its configuration, scenery etc you were using each time. The fact that it has happened twice at different stages of flight suggests it might be a problem with your PC's settings or hardware, but nobody will be able to say for certain until they have more information from you.

    I suggest you make sure your OS, graphics and hardware drivers, Sim software and addons etc are all up to date then see what happens on your next few flights. If your issue is repeatable in the same PMDG aircraft type every time then you can always ask for help in another post or, alternatively, submit a support ticket to PMDG.
    Michael Codd

    Comment


      #3
      Just turn off the crash detection. Don't ask me why, because I have no idea, but there's some sceneries out there that have an invisible wall around the airport, so it's entirely possible you just crashed into one of those.
      Captain Kevin

      Kevin Yang

      Comment


      • Michael Codd
        Michael Codd commented
        Editing a comment
        Sometimes it is easy to forget to mention one of the more likely causes! Thanks Kevin.

      #4
      Hey guys, I think Kevin might be onto something. I flew the exact same flight plan with the PMDG 737 and experienced a CTD this time. I feel that the Orbx Sceneries for NZ might be corrupt or something. I'll try revalidating them and fly in and out of NZCH in a Cessna to see what happens there.

      Cheers for all your help.

      Warwick
      Warwick Finch
      YSCB

      Comment


        #5
        Always crash detection off in P3D/FSX. It doesn't work very well. After that you should have no problems.
        André Hansson

        Comment


          #6
          Warwick I had that with ORBX NZ sceneries - hope that turning off crash detection helps for you

          Adrian Howe
          Adrian Howe

          Comment


            #7
            Originally posted by Maarp View Post
            Hey guys, I think Kevin might be onto something. I flew the exact same flight plan with the PMDG 737 and experienced a CTD this time. I feel that the Orbx Sceneries for NZ might be corrupt or something. I'll try revalidating them and fly in and out of NZCH in a Cessna to see what happens there.
            I only thought about it because years ago, I was at an airport, and when I switched to external view, I saw a huge black wall for a second or two before it disappeared, as it was trying to load the texture. Not sure why it was there, but it was there long enough for me to know that it was there. So you're better off just leaving crash detection turned off. You can pretty much tell if you had a bad landing or not.
            Captain Kevin

            Kevin Yang

            Comment


              #8
              If you take off from runway 02 at NZCH you will hit an invisible wall 2 or 3 miles out on runway heading which will reset P3D. There’s also an invisible wall around NZAA somewhere. I’m not sure where exactly that one is. As mentioned above, ensure crash detection is turned off.



              Bruce Ross
              Bruce Ross
              Dunedin
              New Zealand

              Comment


              • Traian Vuia748
                Traian Vuia748 commented
                Editing a comment
                Can you be more specific on details regarding altitude crossing at 2 or 3 NM from NZCH off rwy 02? I tested 737 and 747 with crash detection on and mesh resolution at 2 and have no issues at all that will reset P3D or hesitations. I have ORBX installed but no Sceneries for NZ Nort or South.

              #9
              Righto, I've re-downloaded and installed the Orbx sceneries for NZ North and South as well as switching off the crash detection in P3D. I flew a short flight into NZCH with the PMDG 737 using the same STAR and Approach as my previous flights and it worked. On at least one occasion there was a hesitation in the simulator (a freeze for maybe a second or two) which might have been a scenery glitch that could have resulted in a crash previously.

              This is only a sample size of one so it isn't definitive but is interesting nonetheless. I'll refly the full flight with the 747 on Wed (tomorrow is super busy!) and see how I go.

              Still, I'm pleased to not have to worry about this as much.

              Cheers

              Warwick
              Warwick Finch
              YSCB

              Comment


                #10
                Happened to me as well, climbing out of Santiago, about drove myself nuts trying to figure out what was going on until someone mentioned crash detection. It had been off for a while and I had deleted my cfg file which reset all of my settings, and I forgot to turn it back on. What an ordeal!!!
                Zsolt Szivak

                Comment


                  #11
                  P3Dv4.5 is known to pause at random and usually only for a few seconds while it is running. This effect is more noticeable when it appears to be loading into memory some complicated addon scenery near the aircraft's position at the time. However, judging by most of the reports I have read this graphics behaviour Is affected by the speed of a user's PC and the type of graphics card they have; and the good news is that this unwanted behaviour is apparently very much improved in P3Dv5.
                  Michael Codd

                  Comment


                    #12
                    Traian Vuia748 ORBX NZSI & NZNI seem to create some invisible areas within their scenery which causes, in my case, P3D V4.5 to crash and reset back to your default aircraft and airfield. I got caught out when flying on the NISOM4Q SID off runway 02. Just before the first waypoint P3D reset. I couldn't fathom it out until I asked on a forum and was told about these invisible walls. I always had "Ignore Crashes" ticked but for some reason it "unticked" itself. I put that down to "just computers". I really can't be more specific than that. I mention the Nisom4Q departure, but be aware that that SID is no longer. The Civil Aviation Authority of New Zealand updated that SID on 21 May this year. The equivalent SID is now MUKVO1P. For your info, you can get all departures and arrivals for New Zealand from this site; http://www.aip.net.nz/NavWalk.aspx?section=CHARTS If you're into Australian flying from this site; https://www.airservicesaustralia.com...cChartsTOC.htm

                    Cheers
                    Last edited by Bruce R; 28Jul2020, 00:31.
                    Bruce Ross
                    Dunedin
                    New Zealand

                    Comment


                      #13
                      Originally posted by Bruce R View Post
                      Traian Vuia748 ORBX NZSI & NZNI seem to create some invisible areas within their scenery which causes, in my case, P3D V4.5 to crash and reset back to your default aircraft and airfield. I got caught out when flying on the NISOM4Q SID off runway 02. Just before the first waypoint P3D reset. I couldn't fathom it out until I asked on a forum and was told about these invisible walls. I always had "Ignore Crashes" ticked but for some reason it "unticked" itself. I put that down to "just computers". I really can't be more specific than that. I mention the Nisom4Q departure, but be aware that that SID is no longer. The Civil Aviation Authority of New Zealand updated that SID on 21 May this year. The equivalent SID is now MUKVO1P. For your info, you can get all departures and arrivals for New Zealand from this site; http://www.aip.net.nz/NavWalk.aspx?section=CHARTS If you're into Australian flying from this site; https://www.airservicesaustralia.com...cChartsTOC.htm

                      Cheers
                      Hi Bruce, it's your simulator unticking itself and not mine, so don't blame me! LOL. I haven't tried your SID, but it is almost certainly a Navigraph issue because if you don't have a renewal subscription your FMS NAV database will not be current.
                      Michael Codd

                      Comment


                        #14
                        Originally posted by Michael Codd View Post

                        Hi Bruce, it's your simulator unticking itself and not mine, so don't blame me! LOL. I haven't tried your SID, but it is almost certainly a Navigraph issue because if you don't have a renewal subscription your FMS NAV database will not be current.
                        Hello Michael. I'm scratching my head over that comment. I'm not putting the blame on anyone about anything. I'm 99.99% certain Warrick's problem is as I've described. So far it seems to have worked. In my reply at #8 Traian Vuia748 asked me to be more specific. In my message at #12, I was endeavouring to be just that.

                        With regards to Navigraph. I don't agree with you there. One didn't need to be flying any SID or STAR for P3D to reset. You just had to be at that spot. I'm not sure about altitude but I was caught out at roughly 3000'. I do have a Navigraph subscription, as well as an fsAreodata one and everything is on the current AIRAC. That's how I knew the NISOM4Q departure is now MUKVO1P

                        Regards
                        Bruce Ross
                        Dunedin
                        New Zealand

                        Comment


                        • Michael Codd
                          Michael Codd commented
                          Editing a comment
                          Sorry, I wasn't accusing you of anything and it was meant as a joke anyway. My comment about the Nisom4Q SID was simply in response to you saying it wasn't there any more - nothing more - so no harm done or intended.
                      Working...
                      X