10-12-2017 update

[Rimshot]

Hi fellas,

I'm in te process of a complete reinstall of my OS and Prepar3D v4.1 and all my addons. Just now I installed my Prepar3D v4 compatible aircraft. I have an issue however with the installation of the 10-12-2017 update; the installer, that I downloaded fresh from the thread on your forum, won't recognize my P3D v4 installation. Instead it prompts it cannot find FSX. When I point it to Documents\Prepar3D v4 addons\A2A it won't continue because of incompatibility. Any ideas what I'm doing wrong?

[shortspecialbus]

When I did this the other day, I was prompted to select a sim, and I picked P3Dv4 and pointed it at my A2A install location without issue. Are you not getting this prompt or did you perhaps select FSX at it by chance? That would explain things, if the message about not finding FSX you stated is what it indeed said.

-stefan

[Rimshot]

When I did this the other day, I was prompted to select a sim, and I picked P3Dv4 and pointed it at my A2A install location without issue. Are you not getting this prompt or did you perhaps select FSX at it by chance? That would explain things, if the message about not finding FSX you stated is what it indeed said.

When I run the installer it checks my system configuration and then tells me it can not find a valid FSX installation. I'm not getting an option to select a simulator.

[shortspecialbus]

Just to ensure that you're not accidentally downloading an older file somehow, can you try this download? (copied/pasted from the A2A thread)

http://www.a2asimulations.com/downloads ... _12_17.zip

-stefan

[Rimshot]

Thanks Stefan. I tried your link, but as it is a direct copy from the thread here at the forum from which I also downloaded the file it makes no difference unfortunately...

[bladerunner900]

I have FSX: Steam and P3D v4 installed at the moment, so I assume this is why I get this menu after starting the installer.



Steve

Edit: Although, I guess it depends how "intelligent" the installer is. By that I mean, perhaps it's just giving me all the options and isn't detecting anything installed at all. In which case there could be a problem with your P3D installation.

[Rimshot]

That's what I would expect to see even with only one simulator installed, as in my case P3D v4.1. I have no clue why the installer behaves the way it does on my system.

[bladerunner900]

Ha! Ninja'd while editing my post.

If it's a 'dumb' installer then it's probably a faulty entry in the Windows registry for P3D and you may have to start from scratch. Sorry.

Steve

[Rimshot]

In the registry (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 and Computer\HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3D v4) the path is set correctly. Other installers find my Prepar3D directory flawlessly...

[crippy]

This may sound stupid, but be sure you are downloading / installing the P3Dv4 file. There are two downloads from the A2A store you can get if you happen to buy both. Also may sound stupid but be sure you bought the correct P3D version of the aircraft as both FSX and P3D versions are available for sale.

[shortspecialbus]

Thanks Stefan. I tried your link, but as it is a direct copy from the thread here at the forum from which I also downloaded the file it makes no difference unfortunately...

Yeah, sorry - I was hoping you had somehow gotten an old file. A long shot, but worth a shot.

Good luck!

-stefan

[Rimshot]

This may sound stupid, but be sure you are downloading / installing the P3Dv4 file. There are two downloads from the A2A store you can get if you happen to buy both. Also may sound stupid but be sure you bought the correct P3D version of the aircraft as both FSX and P3D versions are available for sale.

Thanks, I can understand why you would say that. But I have used the correct P3D v4 installers for my A2A aircraft.

[Rimshot]

Hi fellas,

My last post in this thread here, just to let you know all is working as it should. The problem was that when I installed the updater I did this right after installing my aircraft. Then the installer behaved like I described above. The solution is to simple for words; I fired up and closed Prepar3d. When I ran the updater after that it gave me the option to select a simulator.
Ofcourse this all makes sense; without actually running the sim the A2A aircraft are not added to the addons.cfg file. The updater probably checks this file as well when it does its system configuration check. Well, I'm of to the virtual skies in my Comanche. Have a good day all and thanks for your input