CTD on engine start in FSX SE

[mjordan73]

I have done a clean install using the MilViz F-4SJ Phantom II vA1.170721_JS.exe installer, and also taken the update provided via MVAMS (not sure how to find out what version that is, but it was downloaded last night). Both those versions then CTD during automated engine startup (CTRL-E). Also neither version has the plane in a started up state if I select 'Ready to Fly' in MVAMS (the crash occurs in both 'Ready to Fly' and 'Cold and Dark' modes).

Event viewer shows this...

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MV_F-4J_Sys.dll, version: 1.4.0.8, time stamp: 0x59abe253
Exception code: 0xc0000005
Fault offset: 0x00033dcb
Faulting process id: 0x3bdc
Faulting application start time: 0x01d32e64da7b146a
Faulting application path: E:\Program Files (x86)\SteamLibrary\steamapps\common\FSX\fsx.exe
Faulting module path: E:\Program Files (x86)\SteamLibrary\steamapps\common\FSX\gauges\MV_F-4J_Sys.dll
Report Id: e7e36976-6259-4be0-8317-18d89896f057
Faulting package full name:
Faulting package-relative application ID:

I am running FSX SE on Windows 10. I have DX10 Fixer, other aircraft add-ons (Aerosoft F14X, PMDG 777) and also scenery add-ons (Orbx Eng/Sco/Wal, FTX Global Base & Europe) and Rex Soft Clouds and Airports HD.

[JonathanBleeker]

Try reinstalling the update, but this time select FSX SE side by side instead of stand alone.

[mjordan73]

Try reinstalling the update, but this time select FSX SE side by side instead of stand alone.

'Side by side' is not an option in the 170721 installer or the 170908 upgrade via MVAMS (you get a choice of FSX/FSX SE standalone and Prepar3d 4).

I've tried uninstall followed by reinstall already. I tried reinstall without uninstall also and that also blows up at the same point. A previous installer I had (MilViz_F-4SJ_Phantom_II_vA1.170426_JS) however works OK. Updating from 170426 to 190908 via MVAMS results in a CTD when the first engine to start up hits about 100rpm. So it would seem to be an issue with MilViz F-4SJ Phantom II vA1.170721_JS and the 170908 upgrade.

Its also worth noting that 'ready to fly' doesn't work in 170426 either and requires user input to start up.

[JonathanBleeker]

Unzip these into your gauges folder: https://www.dropbox.com/s/5lg1l3347kki9 ... E.zip?dl=0

Regarding the ready to fly, is the engine running in your default flight?

[mjordan73]

Unzip these into your gauges folder: https://www.dropbox.com/s/5lg1l3347kki9 ... E.zip?dl=0

Regarding the ready to fly, is the engine running in your default flight?

Thanks. I didn't realise engine state was inherited from the default flight (nor that my default flight was C&D as I never use it).

The replacement DLLs worked a treat also and all is working fine now. I assume the updated DLLs will find their way into subsequent installers?

[JonathanBleeker]

What's happening is that for some reason, even though it installs into FSX SE, the installer seems unable to select the correct dll set for SE. As a result it installs the version for FSX Acceleration which is not compatible and it crashes. I am still investigating this.

[mjordan73]

What's happening is that for some reason, even though it installs into FSX SE, the installer seems unable to select the correct dll set for SE. As a result it installs the version for FSX Acceleration which is not compatible and it crashes. I am still investigating this.

Thanks for the explanation. I guess worst case scenario is back to the multiple selectors for the various incarnations of FSX? If it helps with your debugging then I did have FSX Acceleration installed on my machine in the past so maybe its returning a false positive match for that (it's long since been uninstalled and the install folder is definitely gone, but I have no idea whether it's left something behind in the registry or similar).

[MDIvey]

I Have similar setup and have the same problem as above... which your gauge download above fixed. I'm also getting the same with the E model. Could I have a replacement SE "E" gauge set to tide me over until you get to the bottom of this. Many thanks.

I should add E is basic version not ADV, and all 3 F4 are used without Tacpack in SE.

Regards Matt Ivey

[JonathanBleeker]

F-4E files for FSX SE.

https://www.dropbox.com/s/jrcy37rgiljft ... E.zip?dl=0

[MDIvey]

Thanks Jonathan

Matt