F-4E CTD in P3D 3.4.9

[flyboy7798]

I get a CTD as soon as the sim loads the virtual cockpit. AppCrashView says its the fault module is MV_F-4E_Sys.dll. Anyone got any ideas?

V/R

Jim

Windows 7 Professional 64 Bit SP1, Intel i7-950 3.06GHZ 8M LGA 1366, 12 GB DDR3/1600 NHZ RAM, ASUS Sabertooth X58 2-Way SLI/Crossfire, USB Sata 3.0, ATX Intel, 1x Gigabyte Nvidia GeForce 1060GTX, 1x EVGA Nvidia GeForce 580GTX 1.5 GB PCI-E (Dedicated to PhysX), 1x EVGA Nvidia GeForce 430GT 1 GB PCI-E 16X, SLI/Crossfire disabled, 1x 256GB SSD 2.5 SATA MLC, 1TB SATA III 7200RPM 3.5 HD.

[Krazycolin]

Every time P3D is updated, we have to update the F-4. Patience please

[k4cz0rpl]

Hey.So I have a the latest veriosn of F4 E/J/S. (161120)

Im trying to figure out what going on, coz airplane do not work with P3D 3.4
Here is some info:
Version=1
EventType=BEX
EventTime=131256440042163744
ReportType=2
Consent=1
UploadTime=131256440042843783
ReportIdentifier=a8d29a8d-bcfc-11e6-97ad-d43d7ef1c4c8
IntegratorReportIdentifier=a8d29a8c-bcfc-11e6-97ad-d43d7ef1c4c8
WOW64=1
Response.type=4
Sig[0].Name=Nazwa aplikacji
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Wersja aplikacji
Sig[1].Value=3.4.14.18870
Sig[2].Name=Sygnatura czasowa aplikacji
Sig[2].Value=581239e2
Sig[3].Name=Nazwa modułu z błędem
Sig[3].Value=MSVCR90.dll
Sig[4].Name=Wersja modułu z błędem
Sig[4].Value=9.0.30729.6161
Sig[5].Name=Sygnatura czasowa modułu z błędem
Sig[5].Value=4dace5b9
Sig[6].Name=Przesunięcie wyjątku
Sig[6].Value=00031484
Sig[7].Name=Kod wyjątku
Sig[7].Value=c0000417
Sig[8].Name=Dane wyjątku
Sig[8].Value=00000000

As u see Msvcr90.dll is causing error but:
1.That file do not exist in my system
2.Its part of MS VC 2008-ive reinstalled and still no file in windows/system32
3.Im gonna try soon to repair windows installation to get the file.
4.I have lots of MS VC installed.(2005.2008(4 different version) 2010 2013 2015)

So here is what is happening.I can start sim choose F4E load airport and as soon i click on any switch I get error msg:Creation failed - check if sound file is available.
I was uninstalling,maunaly removing Phantom ctd and reinstalling and it dosent help.
Problem of GaugeSound.DLL?
Version=1
EventType=APPCRASH
EventTime=131256515326703418
ReportType=2
Consent=1
UploadTime=131256515327193446
ReportIdentifier=3027290c-bd0e-11e6-a889-d43d7ef1c4c8
IntegratorReportIdentifier=3027290b-bd0e-11e6-a889-d43d7ef1c4c8
WOW64=1
Response.type=4
Sig[0].Name=Nazwa aplikacji
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Wersja aplikacji
Sig[1].Value=3.4.14.18870
Sig[2].Name=Sygnatura czasowa aplikacji
Sig[2].Value=581239e2
Sig[3].Name=Nazwa modułu z błędem
Sig[3].Value=GaugeSound.DLL
Sig[4].Name=Wersja modułu z błędem
Sig[4].Value=0.0.0.0
Sig[5].Name=Sygnatura czasowa modułu z błędem
Sig[5].Value=3eb140e0
Sig[6].Name=Kod wyjątku
Sig[6].Value=c0000005
Sig[7].Name=Przesunięcie wyjątku
Sig[7].Value=00001725
DynamicSig[1].Name=Wersja systemu operacyjnego
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Identyfikator ustawień regionalnych
DynamicSig[2].Value=4105
UI[2]=F:\P3Dv3\Prepar3D.exe
UI[3]=A fatal error occurred.

F4J/S I cant even load at the aiport coz as soon i hit fly now P3D is crashing with MSvCr90.dll
Yesterday I had most of the crashes with MV_F-4E_Sys.dll but i found some files on forum.

Any idea?

[JonathanBleeker]

You are running the sim as admin? As in right click on it, select Properties->Compatibility and make sure the checkbox Run This Program as administrator is checked.

[k4cz0rpl]

Yes its running in admin mode.
My question is:
Should I have some sound for Phantom in P3d/Sound/Milviz?

So far I have sounds in model itself.
F:\P3Dv3\SimObjects\Airplanes\Milviz Phantom II\F4EXML_Sounds
F:\P3Dv3\SimObjects\Airplanes\Milviz Phantom II\sound


Is there a file that should start with P3D xml or dll.cfg? Maybe Im missing some entry or something? No idea

OK more questions?
Panel.Cfg for F4E
[Window00]
Background_color=159,159,159
size_mm=820,459
window_size_ratio=1.000
sizeable=0
position=0
visible=1
ident=70
render_3d_window=0
window_size= 0.416, 0.3658
window_pos= 0.2, 0.2

gauge00=MV_F-4_ACM!MV_F4E_ACM, 10,10,800,439

Bolded text mean that file is not presented in my gauge folder of P3D.
MV_F-4E_Sys
MV_F4E_LT
MV_F-4_ACM those 3 are in gauge folder.

UPDATE
I copy Milviz_Sound.gau from Phantom to Gauges folder and now version F4E is working without sound issue.Lets see whats up with J/S

UPdate 2
No luck to start F4S from P3D menu after hiting fly now.CTD.
IF I choose E/F version then switch to J everything is ok.Choosing to S causing CTD.

[JonathanBleeker]

Can you post the error report please.

[k4cz0rpl]

Jonathan after deleting file msvcr90.dll from C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll phantoms are working great.

[JonathanBleeker]

That's a dangerous thing to do and deffo nor recommended. But so long as you don't get more problems elsewhere....

[flyboy7798]

Well now that we got k4cz0rpl problem solved, I would like to address mine. Its been a while since I was in the cockpit of the phantom. My rig has changed (see below) and I'm on 3.4.18.19475 P3D. I'm getting a kernelbase.dll error:

Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.18.19475
Sig[2].Name=Application Timestamp
Sig[2].Value=5851bfd2
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.479
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58256d37
Sig[6].Name=Exception Code
Sig[6].Value=c0020001
Sig[7].Name=Exception Offset
Sig[7].Value=000da832
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48

... and the last 3 modules that loaded from Milviz is:

LoadedModule[242]=D:\Prepar3D v3\SimObjects\Airplanes\Milviz Phantom II\panel\MV_F4_HW.dll
LoadedModule[243]=D:\Prepar3D v3\Gauges\Milviz_Sound.gau
LoadedModule[244]=D:\Prepar3D v3\Gauges\MV_F4E_LT.dll

The installer is MilViz_F-4_Phantom_II_E_vA1.161007.exe

Any help would be appreciated

[Krazycolin]

If this is the latest version of P3D, then it's not yet supported.

[scottharmes6]

Well now that we got k4cz0rpl problem solved, I would like to address mine. Its been a while since I was in the cockpit of the phantom. My rig has changed (see below) and I'm on 3.4.18.19475 P3D. I'm getting a kernelbase.dll error:

Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.18.19475
Sig[2].Name=Application Timestamp
Sig[2].Value=5851bfd2
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.479
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58256d37
Sig[6].Name=Exception Code
Sig[6].Value=c0020001
Sig[7].Name=Exception Offset
Sig[7].Value=000da832
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48

... and the last 3 modules that loaded from Milviz is:

LoadedModule[242]=D:\Prepar3D v3\SimObjects\Airplanes\Milviz Phantom II\panel\MV_F4_HW.dll
LoadedModule[243]=D:\Prepar3D v3\Gauges\Milviz_Sound.gau
LoadedModule[244]=D:\Prepar3D v3\Gauges\MV_F4E_LT.dll

The installer is MilViz_F-4_Phantom_II_E_vA1.161007.exe

Any help would be appreciated

Hi,

I have that version of the Phantoms, and it will work in P3D V3.4.9. I have not updated my P3D install past 3.4.9 (no hotfixes). TBH there was nothing of great interest (for me) in the hot fixes anyway. P3D now makes the legacy client installers available for P3D V3, so it is possible to roll back. Just FYI

Cheers,

[JonathanBleeker]

I will be updating the F-4 to v3.4.22 soon.

[flyboy7798]

When will it be compatible with 3.4.18.19475 (which I'm currently on) and when 3.4.22.19868?

[Krazycolin]

The F-4's will only be compatible with the latest P3D v3.

[flyboy7798]

Any word on the updates for the E, S, J models?