64 bit version - P3DV4.1

[azragod]

Hi all, 

I have been flying with FSCaptain for years with FSX and P3DV1-3.4. 

I migrated last year to P3DV4 and 4.1 and waited impatiently for a compatible FSCaptain version... So far so good, v.1.8.0 went out. 

And such a disapointment....

1) Installer is looking for the FSX dll.xml which has nothing to do with P3D... I had to manually create a fake folder and after, manually modify my P3D dll.xml so installer could arrive to it's end. 
2) Aircrafts installed outside the native simobjects folder (like A2A or FSLabs) are totally ignored from administrator. 
3) Internal FCDU installer doesn't work at all outside P3D folder... (I tried to install it in external simobject folders for FSLabs A320 and it made some erratic aircraft types for every airbus variations regarding to tail numbers - like some PA-28 based airbus.... )
4) Using external FCDU, FSLabs a320 is recognised but still not listed in th administrator... So there is not any flight planning possible. 
5) So I tried to start a flight via the external FCDU. It worked but it will generate constant errors with sound files "not found" (which are currently at the right place indeed...)
6) Cancelling these errors popping up every 5 seconds will make boarding process to continue but.... It will crash the simulator once it ends...
7) Seeing that 64bit version is really far from working, I tried to uninstall all, and surprise !!! There is no uninstall programm or process.... Needed to erase everything manually to recover my original files.

So. Thanks for your job guys but you obviously have a mass of work to make FSCaptain usable for P3D 64bit version !!!!

Regards. 

Lionel

[Travis]

Hi Lionel,

First, we'd like to see the FCDU, Admin and Installer logs for your attempts.

After 1.8.0 was released, we began to receive reports from some Captains who don't have the 'standard' Lockheed Martin registry key... so we are not able to determine that we're in P3D4.

We're working on a different way to determine this. It was never mentioned during our long public beta process, and we're not sure why.

Otherwise the Administrator and FCDU Installer are able to see aircraft outside of the internal SimObjects folder for Captains who have the LM registry key.

We check both CURRENT_USER\Software\Lockheed Martin\Prepar3D v4\AppPath as well as \SetupPath - can you tell us what (if anything) you have in CURRENT_USER\Software\Lockheed Martin\Prepar3D v4? You could do so safely via email.
----

The FSLabs A320 for P3D4 is doing something that causes certain of our file locations to not be found. Peter has a fix that works for him, but we need to contact FSLabs before we try to deploy the fix.
----

I just installed the SC-64 full installer into a dummy folder, and the uninstall program was in what should have been my simulator's root folder (UninstallFSCaptain.exe). I can't explain why it would not have been dropped into your system....

Best regards,

[Travis]

Hello Lionel,

Please read Peter's post in this thread which seeks interested FSL A320 Captains for a test of a workaround until a new version of the aircraft is released.

Best,