FsXPand FMS help

A few points to pay attention to while installing FsXPand FMS:

First of all, please read readme.rtf, release.rtf, FMS_Getstarted.rtf. And then, there is the manual.

1. This version is modular: you can have Basic, or FMS version, depending on a setting in your registration box. If you buy a license, you will get one for the appropriate version you requested.

2. You may get a message: "FMC machine does not exist. Please create a share to FsClient folder."
If there is not enough permission in your PC to create the share automatically, you have to do it manually. In that case the FsClient 6.0 folder should be shared as 'FsClient' (so give it a name), and for 8 users (ample for the use of multiple clients and maybe other network use like remote administration).
Reason is that from now on, flightplan information needs to be accessible via the network for the FMS. For that purpose, each machine needs the FsClient folder to be accessible eventually as a slave. FsClient will do that if the permissions are adequate, which depends on the system's settings.

You may get an error if the share is not there. There have been such problems in the past. Afterwards, it was found that the user in that case had more than one FsClient installed in his PC.
So before installing a new version, please make sure that the old FsClient is no longer shared!

3. The FMS version will allow the creation of a flightplan using keyboard commands (a CDU is essentially a keyboard) and fly the flightplan using MCP functions, again via keyboard commands.
Future compatibility with CPFlight MCP will be added. A CDU which is a mere keyboard can be used.
With the Basic version, it remains possible to load a FP separately on each ND. Captain and F/O will have to load their own flightplan. And fly it by hand (although it is perfectly possible to simulate an FMS by flying FS in GPS mode automatically).
Both versions: For AIRAC updates, FsXPand 6.0 folder has to be shared as 'FsXPand'. FsXPand will do this automatically if possible. See above.

4. On startup, FsXPand 6.0 will check the availability of all system files required, and check for write permissions on needed folders/shares.
Please make sure that you have sufficient read/write permissions on all folders and files used: you should be logged in on all your systems with the same account, and have full administrator privileges. You may need to check folder ownership as well.
In Vista, it may be needful to install in C:\FsClient 6.0 rather than in the Program Files to avoid any security/permission problem.

If you find anything out of the ordinary, please report.

Hi,

fsgert wrote: With this message, FsXPand cannot find FSUIPC. Is your FSX running before you attempt FsXpand?

Thank You. Does FSX has to run first b4 fsXpand? My other Progs running on the Server and Client using FSUIPC will start up ok but the info from FSX is only available after FSX is running and no error about not finding or anything else about FSUIPC.

Thanks for reporting... and sorry I missed your message.

Hi Matthias
The 800 has a thrust of 27k. FsXPand expects less, modeled after -700 24k at most, using its values for weight and thrust. So a bigger machine will overreact. Especially so if you choose an even lighter aircraft in FsXPand.
You can influence performance in 2 ways:
- Either you make the aircraft heavier than you tell the FMS, whether by increasing the payload and/or FOB,
- Or you derate the engines in the N1 LIMIT menu of the CDU.