F-4J Version for P3d V3

Locked
Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
F-4J Version for P3d V3

Post by Chris Sykes » Tue Apr 04, 2017 9:56 pm

Hi, Purchased through Just flight yesterday in their/your sale and have downloaded the installer from their site tonight. This has been installed to P3D V3.4 but upon loading the sim it crashes. The version installed/downloaded is 1.161120, is this the latest version?

User avatar
doodlebug
Posts: 1642
Joined: Sun Feb 19, 2017 2:49 pm
Location: LYX>YUL
Re: F-4J Version for P3d V3

Post by doodlebug » Tue Apr 04, 2017 10:05 pm

You have the latest release, but they should have given you a patch for P3D v3.4.22.
Send me your proof of purchase (address in sig) and we'll send it to you and get you on the support forum also.

Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
Re: F-4J Version for P3d V3

Post by Chris Sykes » Tue Apr 04, 2017 11:03 pm

Sent PoP

Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
Re: F-4J Version for P3d V3

Post by Chris Sykes » Tue Apr 04, 2017 11:10 pm

Just double checked and I'm running 3.3.5 btw...

Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
Re: F-4J Version for P3d V3

Post by Chris Sykes » Wed Apr 05, 2017 1:01 am

Hi an update quickly...
Running as admin/normal doesn't make any difference.

First error is a .net runtime event 1026
Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0020001, exception address 7760A882
Stack:

Next is an Application error 1000
Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31
Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d
Exception code: 0xc0020001
Fault offset: 0x000da882
Faulting process ID: 0x4160
Faulting application start time: 0x01d2ad9ed8e375d3
Faulting application path: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: beb2f69d-f0ba-48a3-8012-9dfcc1160d79
Faulting package full name:
Faulting package-relative application ID:

Next a windows error reporting Event 1001
Fault bucket 108794797332, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 3.3.5.17625
P3: 5758bb31
P4: KERNELBASE.dll
P5: 10.0.14393.953
P6: 58ba586d
P7: c0020001
P8: 000da882
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB556.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_c3d322d960a4d25576c96ed933e6853dcd1f8dc8_0da7cb94_1eb5ca46

Analysis symbol:
Rechecking for solution: 0
Report ID: beb2f69d-f0ba-48a3-8012-9dfcc1160d79
Report Status: 0
Hashed bucket: 57bdda66cb90456f2aa288aa7ff127cf

Another Application error 1000
Faulting application name: Prepar3D.exe, version: 3.3.5.17625, time stamp: 0x5758bb31
Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d
Exception code: 0xc000041d
Fault offset: 0x000da882
Faulting process ID: 0x4160
Faulting application start time: 0x01d2ad9ed8e375d3
Faulting application path: D:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 05000f40-cfab-439d-9465-4aaf3e474f6f
Faulting package full name:
Faulting package-relative application ID:

Then a last Windows Error reporting Event 1001
Fault bucket 108793394803, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 3.3.5.17625
P3: 5758bb31
P4: KERNELBASE.dll
P5: 10.0.14393.953
P6: 58ba586d
P7: c000041d
P8: 000da882
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBAD.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_5a2dc0d01745c680a069bafe6a49558c169c59_0da7cb94_3845de6a

Analysis symbol:
Rechecking for solution: 0
Report ID: 05000f40-cfab-439d-9465-4aaf3e474f6f
Report Status: 0
Hashed bucket: c1600c97b9c221d76c7683ff7d81ede5

I have done the delete the 2x DLL's from the gauges folder and reinstalled the patch sent via email.

Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
Re: F-4J Version for P3d V3

Post by Chris Sykes » Wed Apr 05, 2017 1:07 am

Just reading other posts and tested with the Sys.dll's // out in the panel and the sim hasn't crashed!

Raptor
Posts: 411
Joined: Wed Feb 26, 2014 3:07 am
Re: F-4J Version for P3d V3

Post by Raptor » Wed Apr 05, 2017 1:49 am

I believe the F-4s only fly in 3.4.22

I may be wrong though

Krazycolin
Site Admin
Posts: 1728
Joined: Mon Sep 08, 2008 4:18 pm
Re: F-4J Version for P3d V3

Post by Krazycolin » Wed Apr 05, 2017 3:21 am

only working in the latest of the latest (P3D)

Chris Sykes
Posts: 8
Joined: Sun Dec 04, 2011 1:26 am
Re: F-4J Version for P3d V3

Post by Chris Sykes » Wed Apr 05, 2017 10:47 am

Ah Ok Ill have to update then, been meaning to just never got round to it.

Hamilton
Posts: 42
Joined: Sun Apr 23, 2017 4:57 pm
Re: F-4J Version for P3d V3

Post by Hamilton » Mon Apr 24, 2017 6:32 pm

Raptor wrote:I believe the F-4s only fly in 3.4.22

I may be wrong though

No I´ve testes both versions latest and 3.4.22.19868, same crash MV_F4_Sys.dll and with the newest crash MSVCR90.dll. :9

JonathanBleeker
Posts: 3446
Joined: Sat Mar 13, 2010 7:38 pm
Re: F-4J Version for P3d V3

Post by JonathanBleeker » Mon Apr 24, 2017 6:41 pm

The next update will require v3.4.22 for sure but it is not out yet. There was a crash that slipped under the radar by behaving in a similar way to the P3D crash that was actually related to our hardware mapping system for joystick inputs.


Locked

Return to “McDonnell Douglas F-4 Phantom II Support Phorum”