Network FCDU issue - RESOLVED

[Rustydog]

Hi,

I use the FCDU on a networked pc. In 1.8.2 everything works as it should and has done for ages.
When I update to 1.8.3 then I get self test fail. revert back to 1.8.2 and everything works again.
Remade the FCDU shortcut to make sure it was pointing to the right place.
Any ideas? Thanks
Regards Steve

Edit      All firewalls and antivirus disabled.

Edit      Looking at the logs the FSroot path is wrong. How do I change this. Ok figured that one.

Edit      The 'running from' path is wrong in the log, I cant find where to change this to the correct path. Any help would be appreciated. Thanks.

[Travis]

Hi Steve,

I'm not certain if this has been resolved (as the thread title indicates) or not....

If it's not resolved, or if you have any questions, email me your most recent FCDU and FSCaptain log files and I'll take a look.  I will need at least one of both logs!

Best,

[skycamel]

Hi Steve,
me too, I would like to know if it's resolved or not and if so how?
I'm about to (finally) update to 1.8.3 and I also use a networked FCDU.
So it would be nice to know in forehand what to expect.
Cheers

[Travis]

Skycamel,

My guess (my hope!) is that the biggest of the "New Features" is showing up in an untested (network) environment.

There are several new entries in your profile.cfg file - the one that I'll remind everyone cannot be posted in the forum!

These new entries allow for Out Of Simulator installations by letting FSCaptain know where to look for certain things.

See, going all the way back to Version 1.0 FSCaptain has lived in the root folder of simulators.  So it always knew where to find other files, such as \SimObjects\ and the MakeRunways files.

The 1.8.3 Installer should write the correct paths to the three "ROOT" entries - but it will do so with local absolute values.

So if your P3D5 is installed at "P:\P3D5\", that's what would be written for each "ROOT" entry.

However... if you're working remotely then you'll have to manually edit those paths to use the Network Share component that you use for other items.  E.g., "\\P3D-PC\P3D5\"

Please know that there was no testing of using Network Shares during development - I don't have a reliable 2nd PC, since Lucy's old PC went on the blink.

I'll close with the note from the README about these values.  There are three "ROOT" entries, and a fourth entry titled "SUPPORTS" which notes which simulator version is being supported.

Best,

-- Initial work in supporting an out-of-simulator installation, including new values for profile.cfg:
  + FSROOT is now deemed to be the folder into which \FSCaptain\ is installed.
  *  E.g., if your FCDU.EXE is located at "E:\P3D5\FSCaptain\bin\FCDU.EXE", then FSROOT should be "E:\P3D5\".
  + SOROOT is the primary root folder where SimObjects (fixed-wing, rotary and vehicles) are found.
  + MRROOT is the folder where MakeRunways generates its output files (runways.txt, f5.csv, g5.csv, r5.csv).
  (For in-simulator installations, these ROOT values will be identical to one another, and will usually be the root folder of the simulator.)
  + SUPPORTS is a value which determines which simulator is being supported:
  *  The value for FS9 is 1.
  *  The value for FSX (boxed) is 10.
  *  The value for FSX (Steam) is 11.
  *  The value for Prepar3D v2 is 20.
  *  The value for Prepar3D v3 is 21.
  *  The value for Prepar3D v4 is 22.
  *  The value for Prepar3D v5 is 23.

  The FSCaptain installer should write the correct values itself, but for now these values may need to be manually edited.

[Travis]

I wanted to note something separate from all of that....

If you're having problems with a Networked FCDU, then restart everything and try running the FCDU.EXE locally just to test the connection, etc.  You can minimize the simulator and press FCDU buttons up to the point of Pushback.

If a local FCDU can't connect properly, there's a problem that goes beyond a Networked FCDU.

Don't forget to send FCDU and FSCaptain log files.  Without them, I would be flying blind in trying to diagnose anything.

Best,

[Rustydog]

Hi Travis and Skycamel,

You hit the nail on the head Travis. Although I had read the readme etc. it hadn't sunk in.
So the only problem was the paths and once I had figured the correct ones then all is working over the network.
I did have one minor bug which was having icing conditions when getting in the cockpit and the FO told me of this. The only problem is I hadn't logged in yet so he wasn't aboard. Once aboard he repeated his warning. Not a biggie just an eye brow raiser.

Keep up the good work

Regards Steve

[Travis]

Steve,

Thanks for the confirmation, as well as your kind words.

I seem to recall that I wanted to move the "FO Sees Ice" call earlier in the startup process so that it could occur if one were making an offline flight.

My guess is that when you logged in, the flag which notes that such a call has been made was reset.  Thus the duplicate call was made.

I'll look for that when I'm next in the FCDU debugger.  I'm currently trying to make Scenery Scanner work well with MSFS while not affecting all other simulators.

The work is going well, but I need data from lots of MSFS Captains-to-be so I can find all the possible "corner cases."

Best,