Olli31

I also have several ctd's with a319. Partially without error report! The a320 works perfectly!

No! Sometimes it is after the pushback or on the way to the runway or after the start. The A320 works fine!

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

Will make a system check. Have P3D since version 4.1 updated only the client. Is that a possibility for the mistake?

I have now tried about 15 flights with the current version of A320. Each flight ends at different positions between pushback and first part of the climb in the CTD! Mistake is at different airports. No error message in Event Viewer or AppCrashView! The A319 works mostly. But I have had the same problem for 5-6 times.

On the arrival side of the MCDU all runways are suggested which 33 are missing. It does not exist. It is available on the departure page. NavData 18/08 is installed. LICR from RFSCENERYBUILDING is installed.

Hast du auch alle Informationen in die MCDU eingegeben? ZFW? Habe irgendwo gelesen das man alles ausfüllen muß und es dann funktioniert. Bei mir läuft alles ohne Probleme.