Allgemein (keine Supportanfragen)

6394 topics in this forum

  1. Pinned topics
    • 0 replies
    • 2652 views
    • 3015 replies
    • 141893 views
    • 0 replies
    • 6856 views
    • 3 replies
    • 8429 views
    • 0 replies
    • 8953 views
    • 1 reply
    • 14499 views
  2. Topics
    • 5 replies
    • 160 views
    • 0 replies
    • 105 views
    • 3 replies
    • 254 views
    • 2 replies
    • 142 views
    • 2 replies
    • 425 views
    • 5 replies
    • 360 views
    • 7 replies
    • 373 views
    • 10 replies
    • 480 views
  3. Service Pack

    • 6 replies
    • 359 views
    • 1 reply
    • 352 views
    • 1 reply
    • 403 views
    • 1 reply
    • 298 views
    • 1 reply
    • 427 views
    • 9 replies
    • 508 views
    • 0 replies
    • 292 views
    • 22 replies
    • 890 views
    • 8 replies
    • 721 views
    • 0 replies
    • 463 views
    • 2 replies
    • 634 views
  • Posts

    • I have the problem on every flight with the A319 it comes to the CTD.
      P3D v4.3 and Windows 10Pro are newly installed.
      A319 v1.1.0.0
      What can I do?       Version=1
      EventType=BEX64
      EventTime=131822974696528826
      ReportType=2
      Consent=1
      UploadTime=131822974701714626
      ReportStatus=268435456
      ReportIdentifier=03351e56-6dd3-48df-87f1-0d0c967ef9d1
      IntegratorReportIdentifier=ca15487d-d2ad-4d8b-9468-95fcecfece53
      Wow64Host=34404
      NsAppName=Prepar3D.exe
      OriginalFilename=Prepar3D.exe
      AppSessionGuid=000005dc-0001-0009-f638-ab304954d401
      TargetAppId=W:0006d08646099bc9fd2fb428d4a6f162fbde00000904!0000d5fc0d7ce97f85830080d86c7b00cc081e7b7730!Prepar3D.exe
      TargetAppVer=2018//06//21:23:18:59!2d5e49!Prepar3D.exe
      BootId=4294967295
      TargetAsId=576
      UserImpactVector=271594288
      IsFatal=1
      Response.BucketId=4f9e6d06e4ff41b41aac3ee78b29d1a4
      Response.BucketTable=5
      Response.LegacyBucketId=1921980305173500324
      Response.type=4
      Sig[0].Name=Anwendungsname
      Sig[0].Value=Prepar3D.exe
      Sig[1].Name=Anwendungsversion
      Sig[1].Value=4.3.29.25520
      Sig[2].Name=Anwendungszeitstempel
      Sig[2].Value=5b2c3263
      Sig[3].Name=Fehlermodulname
      Sig[3].Value=Airbus_ECAMD2D.dll
      Sig[4].Name=Fehlermodulversion
      Sig[4].Value=1.64.0.201
      Sig[5].Name=Fehlermodulzeitstempel
      Sig[5].Value=5b4ca9fd
      Sig[6].Name=Ausnahmeoffset
      Sig[6].Value=000000000016fbfc
      Sig[7].Name=Ausnahmecode
      Sig[7].Value=c0000409
      Sig[8].Name=Ausnahmedaten
      Sig[8].Value=0000000000000002
    • Out of curiosity, what will the paint kit for the A330 look like? Will it be like the A320 ones or is it going to be similar to something like PMDG's or QualityWings?
    • Hello,   probably the servers have been busy as it worked now just fine. Thanks for your reply. Danke.   Cheers
    • Interesting.  What I can tell you is that I use the P3D command for Autopilot Master Off and it works fine. In fact it's worked fine throughout the Beta and all release and test versions.   If you haven't tried to bind your button to the P3D Command above, please give it a try.  If you just have to had it assigned in FSUIPC (noting that we only recommend using P3D Controller assignments, particularly for trust levers) then you'll have to reach out to Pete in the FSUIPC forum.   Best wishes my friend!  
    • This is a known issue with Chaseplane, and I've spoken to them about it.  It's not an easy fix to do, so we'll have to live with this for the time being.  I've been flying the this version of the Bus now for quite a long time, and found it easy to get used to.   Now, if you're not using Chaseplane then please let us know!   Thanks for writing in.   Best wishes.