P3Dv3.exe APPCRASH cites MV_F-4E_sys.dll
Posted: Wed Oct 26, 2016 8:58 pm
I updated F-4E to run on P3Dv3.4.
When I started P3D & loaded F-4E, within 10 seconds of the cockpit view being on the screen I would consistently get a P3D AppCrash message
The Fault Module was given as: MV_F-4E_sys.dll
I have P3D on a P drive & I located MV_F-4E_sys.dll there. The file is described as:
MV_F-4E_sys.dll 10/7/2016 12.23 pm 2,529 KB P:\Lockheed Martin|Prepare3D v3\gauges
The Milviz F-4E .exe file, vA1.161007 that I downloaded for the F-4E update is showing as having 355,960 KB
I am wondering if the .dll is corrupt or whether anyone can spot anything that is wrong with the KB of the .dll or .exe?
This morning I moved MV_F-4E_sys.dll to another drive, tried loading the F-4E again, & now it works, can be flown.
Bit of a head scratcher.
My questions are:
Should MV_F-4E_sys.dll be back where I found it on the P drive?
Am I losing any F-4E functionality by quarantining it on another drive?
How do I fix the .dll if it is corrupt?
Thanks
When I started P3D & loaded F-4E, within 10 seconds of the cockpit view being on the screen I would consistently get a P3D AppCrash message
The Fault Module was given as: MV_F-4E_sys.dll
I have P3D on a P drive & I located MV_F-4E_sys.dll there. The file is described as:
MV_F-4E_sys.dll 10/7/2016 12.23 pm 2,529 KB P:\Lockheed Martin|Prepare3D v3\gauges
The Milviz F-4E .exe file, vA1.161007 that I downloaded for the F-4E update is showing as having 355,960 KB
I am wondering if the .dll is corrupt or whether anyone can spot anything that is wrong with the KB of the .dll or .exe?
This morning I moved MV_F-4E_sys.dll to another drive, tried loading the F-4E again, & now it works, can be flown.
Bit of a head scratcher.
My questions are:
Should MV_F-4E_sys.dll be back where I found it on the P drive?
Am I losing any F-4E functionality by quarantining it on another drive?
How do I fix the .dll if it is corrupt?
Thanks