Engine does not start, even in auto mode. No clicks or sound

[speedy70]

FSX sp2? I thought you said you were running P3D?

[Nick - A2A]

FSX sp2? I thought you said you were running P3D?

Chris - I think the OP was just querying that he needed to install the "FSX-SP2-XPACK" version of SimConnect. However, sounds like all versions are properly installed.

Norbert - you mentioned earlier that the Accu-Sim update won't run because it detects your P3Dv3 installation as v4. Have you previously had a copy of P3Dv4 installed on the same machine?

Also, as I mentioned on page one, are you loading a default P3D aircraft before switching to the Comanche?

Thanks,
Nick

[Lewis - A2A]

Norbert - you mentioned earlier that the Accu-Sim update won't run because it detects your P3Dv3 installation as v4.

I am not sure technically how that is even possible, and points to a very weird P3D core installation?

[Nick - A2A]

Yeah, something seem a bit odd doesn't it? I checked, and the updater successfully detects and updates my P3Dv3 installation, even with P3Dv4 installed on the same drive.

I wonder if repairing the "Prepar3D v3 Academic Client" in Windows is worth a try?

Nick

[NPleyer]

What can be weird on the P3D installation? Everything else is running perfectly.
Anyway I have already run the repair twice. Just for this A2A aircraft.

[Lewis - A2A]

Can you give us more details about your installation, its weird because from a technical POV its essentially impossible for P3Dv3 to be detected as P3Dv4 unless you once had v4 installed, had some registry errors or other tweaks that have caused some very strange system behaviour. Are you using migration tools for example, these are a big no no and will cause some very very strange issues that from top of my head could be the only way you would get P3Dv4 issue in a P3Dv3 installation.

thanks,
Lewis

[NPleyer]

I am using the migration tool but uninstalled it and reinstalled the aircraft. With no effect!

[Lewis - A2A]

Ok it sounds like the migration tool has potentially runined your installation, this is a known issue with the tool and is why its recommended to never use it by developers. A reinstall and total clearence of the tool with total wipe might be the only way to fix things. But for sure its looking like the migration tool has done something to cause your sim to be detected as an entirely different piece of software.

thanks,
Lewis

[NPleyer]

And what do you suggest?

[Nick - A2A]

I think Lewis suggested above that a complete reinstall of P3D (and then the A2A Comanche) now that you've removed the migration tool is the best option. I guess you could try repairing the P3D client again, if you haven't already done this.

I'm not familiar with the Flightsim Estonia Migration Tool, but if it has an option to restore original registry settings (or similar), this may have been a better bet than just uninstalling it.

Nick