|
Post by peter on Dec 23, 2017 13:27:31 GMT -5
Hello Andy,
to solve the shift-F8 problem, can you send us the panel.cfg file (located in Simobjects\Airplanes\Name of your Plane\panel\ )?
I just learned that the flight dispatcher has been removed from the administrator that you can launch from within the simulator. However, you can access Flight Dispatch using Admin.exe . In the long run, the administrator will only be accessible from outside the simulator.
That's a mistake in the 1.8.0 installer. It will be added in 1.8.1. Sorry about this.
You can simply delete the FSCaptain folder.
Best regards, Peter
|
|
|
Post by andyjohnston on Dec 26, 2017 8:36:30 GMT -5
Should I wait for the new installer? I have looked in my various folders and discovered that it's making the change to aircraft in the FSX install rather than the P3Dv4 one.
|
|
|
Post by peter on Dec 26, 2017 8:46:17 GMT -5
Hi Andy,
could you let me know the exact filename of the FSCaptain installer that you downloaded?
Peter
|
|
|
Post by Travis on Dec 26, 2017 18:44:00 GMT -5
Hello Andy,
There won't be a new build for several weeks.
We will target you for some initial test builds, since your situation looks very different for us - it appears that you have FSX and P3D4 both in a containing folder... but there is no defined P3D4 path in your registry... however there is a P3D3 path that also points to the same containing folder!
So to run the FCDU installer properly until then, when the main dialog appears... if its pointing to the FSX path, just change it to your P3D4 path.
Regards,
|
|
|
Post by andyjohnston on Dec 26, 2017 21:50:20 GMT -5
File name was FSCaptain_SC-64.zip. Yes, I have a folder at C:\MSFS where all my flightsim stuff is installed because if it goes under the default program files folder, you have trouble editing files.
|
|
|
Post by Travis on Dec 27, 2017 1:56:28 GMT -5
Andy,
You're correct to keep all add-ons outside of the Program Files (X86) folder, but until now we've only seen totally separate simulator installations... such as mine...
F:\FlightSim\ <-- [FSX] L:\P3D2\ <-- [Prepar3D]
However I'm thinking that your lack of a Prepar3D4 registry key combined with a presence of both Prepar3D3 and FSX registry keys have 'bum-fuzzled' the FCDU Installer.
(The Admin seems to know where it's at.)
So if you run the FCDU Installer and see the "FSX" path, then I would suggest that you simply change it to the "P3D4" path and continue from there.
Also, I would encourage you to ignore any lack of an FSCaptain uninstaller. If you ever want to 'uninstall' it, just delete the FSCaptain folder along with the FCDU gauges. There's nothing else we add to anyone's system....
Regards,
|
|
|
Post by andyjohnston on Dec 28, 2017 9:13:14 GMT -5
Okay, when installing I did point it to the P3D4 folder. I guess I'll just delete FSCaptain as it doesn't seem to work.
|
|
|
Post by Travis on Dec 28, 2017 17:08:04 GMT -5
Sorry that you're giving up Andy!
While we see you installed to a folder named "P3D4", your Windows Registry does not have an install location for Prepar3D Version 4. Our Administrator can work around that lack of information, but our FCDU Installer couldn't.
I had hoped to work on a fix for that next month, but without you to test such I won't have an audience....
Regards,
|
|
|
Post by andyjohnston on Dec 29, 2017 20:14:58 GMT -5
If you would like me to remain engaged for testing, I will gladly do so.
|
|
|
Post by Travis on Dec 30, 2017 19:14:51 GMT -5
Hi Andy,
Yes - we would like to give you some test builds (of the FCDU Installer to begin with) once we can figure out why your Installer is looking at your FSX folder while your Admin knows to look at your P3D4 installer.
Expect a private build (via email) within a few days after the new year begins.
Regards,
|
|