Just Flight Traffic 360 is installed into a subfolder of SimObjects, and an entry relating to this is made in SimObjects: Give it a try and let me know how it goes.
If you go to Edit / Options in FSHostClient and enable "Log debug messages", you can see all the aircraft files being loaded when it first connects to Prepar3D. FSHostClient uses this to find all the Prepar3D aircraft files, so this version should load all the aircraft correctly as well. I also changed the location in the registry where Prepar3D stores its own install directory. >dir /a/b c:\windows\winsxs\manifests\x86_* You should see lines like the following indicating that you have 9.0 installed (and perhaps several other versions as well):
#After install fsx acceleration pack simulator won't start Pc
Just save the file somewhere on your PC (the FSHostClient install directory might be a good choice, but it doesn't matter) and double-click it to run it. I'm also attaching an updated version of my test script "check_fshostclient.bat" to the bottom of this post, so you can check which versions of SimConnect you have installed. \redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi You can find the installer for it here, under your Prepar3D directory: If FSHostClient is unable to start, it's most likely because you don't have SimConnect 9.0 installed. This is the version that was installed with FSX SP2 and FSX Acceleration Pack. In Prepar3D v4, it appears that they've changed it so that SimConnect 9.0 is now required. Note that previous versions of Prepar3D worked with SimConnect 5.0, which was the original version released with FSX.
I'm still working on a new version of FSHostClient that can dynamically load different versions of SimConnect.dll, but in the meantime I've created FSHostClient 1.5 beta 4, which should work with Prepar3D v4: So the key here is which FS you're currently running, not which FS versions you have installed. Eventually what should happen is that FSHostClient loads the particular version of the dll that your FS needs, and they start communicating. This way, you can start FSHostClient first if you want, and then start FS afterward. After it's tried all versions of the dll you have on your PC, it'll wait a second, and then try the whole search over again. At that point, FSHostClient will try the next dll it finds, and see if it can connect to FS. However, if FSHostClient loads a version of the dll and then it can't find any Flight Simulator running, one of two things is happening: 1) you haven't started FS yet, or 2) the FS you're running requires a different version of the dll so they can't communicate. At that point FSHostClient knows where to look in the registry to find the other info it needs, and off it goes. If you have any flavor of FS running, it'll answer and send back info to FSHostClient to say which one it is. Then it'll load the first one, and try to use it to connect to Flight Simulator using SimConnect. Then once it's running, it scans your PC (specifically the C:\Windows\WinSxS directory) to find out which versions of the dll you have installed. The idea is to change FSHostClient so it's not tied to a specific version of the dll, so it'll start up even if you don't have the dll installed at all. If you don't have that version on your PC, FSHostClient won't start up at all. Right now FSHostClient requires a specific version of SimConnect.dll. My plan is to make FSHostClient work with FSX, FSX:SE, and Prepar3D, even if they're all installed on the same machine, and even if you have different versions of them.