GOOD INFO!
I did install it as admin but I run it on Win10...with no antivirus except the Windows one. Which might be the culprit. Or Windows Defender. OR Windows Firewall
I'll have a proper "session" and then I'll get back with my latest "exploits".
Oh and regarding your question "did it find the correct v4 installation folder for you or did you need to type it in?".
It DID find it...so that's odd (or not very odd at all).
-----------------------------------------
UPDATE
Alright, now I've tried the new installer.
It differs slightly (7 bytes smaller) when comparing it to the old installer (I use "Beyond Compare").
Now when I look, I
do find the four AAS_ sound files under sounds, but only
two under SimObjects\Misc folder:
AAW_Tracer and
AAW_Missile respectively.
As for effects, there are 24 of them in the effects folder.
So things are almost OK. But then again, running the FSCAI.exe gives me this prompt:
Answering Nej (=No) means it gets aborted, answeing Ja (=Yes) results in nothing happening (it won't create the dll).
Now with all I know, I might have messed something up, perhaps I did a crappy uninstall of the old version etc...but this new executable, FSCAI.exe, is clearly dead-set on FSX as opposed to Prepared V4.
HOWEVER, if I create that FSX directory under C:\Users\etc.etc.\Microsoft and then try running FSCAI.exe...I get this:
And the next time I run FSCAI.exe...I get it up and running.
Alrighty, the hour is growing late but having started P3d V4 and then started FSCAI.exe - it seems to be able to find those two AA I've placed in one of my missions.
Starting FSCAI.exe gives me this though.
But I just clicked it away and then it did the connection.
Then the gunners shot my ailerons to hell
SUMMARY: The executable (FSCAI.exe) I get installed is dead-set on using FSX. It works just fine if I play along though...but it's not how I want to run things.
And neither should you. I mean this FSCAI-thing is
ground breaking AWESOME! It deserves better packaging/delivery.
Final note: As I've worked in software distribution/msi-packaging myself, I know too well the pitfalls of setting up an installation. AND I know how extensive testing can foul up things on the tester's side as well.
So let's just agree things are not well on my side for now. Oddly enough, the old FSCAI.exe from FSCaptain had no problems with running together with P3D V4. So I'm reverting to that for now.