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

777 CTD with uplink

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

    777 CTD with uplink

    Hi, wondering if anyone can help.

    I’m getting a CTD when using the fltplan uplink. I download the fltplan from simbrief (PMDG format) and when I try an upload I get a CTD.

    Kind regards

    Greg
    Greg Marshall


    #2
    Simbrief is usually very easy to use, but in this case you may have a corrupted flightplan .rte file. Corrupted rte files shouldn't cause a crash but one must rule it out.
    Dan Downs KCRP

    Comment


      #3
      Originally posted by DDowns View Post
      Simbrief is usually very easy to use, but in this case you may have a corrupted flightplan .rte file. Corrupted rte files shouldn't cause a crash but one must rule it out.
      Cheers Dan, I'll try another route and check.

      Greg
      Greg Marshall

      Comment


        #4
        Following this........i am having same issue windows event viewer tells me it has something to do with a gauge this has never happened before.....im stumped

        Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
        Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x5b5f8601
        Exception code: 0xc0000409
        Fault offset: 0x00264c38
        Faulting process id: 0x1ec
        Faulting application start time: 0x01d5c7802cc383f3
        Faulting application path: C:\FSX\fsx.exe
        Faulting module path: C:\FSX\GAUGES\PMDG_777X.DLL
        Report Id: cc6384b4-aa5b-41d9-84bc-b7628ff90b41
        Faulting package full name:
        Faulting package-relative application ID:
        Cheers,
        Ben

        Comment


          #5
          Originally posted by KC135AE View Post
          Following this........i am having same issue windows event viewer tells me it has something to do with a gauge this has never happened before.....im stumped

          Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
          Faulting module name: PMDG_777X.DLL, version: 1.0.0.0, time stamp: 0x5b5f8601
          Exception code: 0xc0000409
          Fault offset: 0x00264c38
          Faulting process id: 0x1ec
          Faulting application start time: 0x01d5c7802cc383f3
          Faulting application path: C:\FSX\fsx.exe
          Faulting module path: C:\FSX\GAUGES\PMDG_777X.DLL
          Report Id: cc6384b4-aa5b-41d9-84bc-b7628ff90b41
          Faulting package full name:
          Faulting package-relative application ID:
          Cheers,
          Ben
          Please add your first and last name signature to your post as per forum rules.
          Contact support at support.precisionmanuals.com and open a ticket.
          Danny Z.Cebis

          Comment


            #6
            Ausflight In the Triple Seven again tonight and same issue again. Event viewer matches your log. I’ve raised a ticket.
            Greg Marshall

            Comment


              #7
              Originally posted by et31 View Post
              Ausflight In the Triple Seven again tonight and same issue again. Event viewer matches your log. I’ve raised a ticket.
              Simbrief saves FPL files as ICAOICAO.rte

              Please rename it to ICAOICAO01.rte and then try uplinking it.

              Example: Rename simbriefs EGLLKLAX.rte to EGLLKLAX01.rte before uplink.
              Leo Cal

              Comment


              • DDowns
                DDowns commented
                Editing a comment
                Leo the 01 or 001 suffix should not be required.

              #8
              Figured this out with the help of a raised ticket at PMDG.

              Please make sure your ADIRU is on and fully aligned prior to doing a route uplink.

              Panel states load with the ADIRU off and unaligned.

              It is a current issue PMDG are looking into. Easy fix for the moment however.

              Also no number is required for example ICAOICAO.rte works fine.
              Greg Marshall

              Comment

              Working...
              X