Hyde wrote in Fri Sep 23, 2011 12:15 am:... and run 777-200ER but FG never start up. fgrun might not take any parameter.
So I type command /usr/local/bin/fgfs --telnet=9321 and this time FG starts with default c172p and KSFC airport.
Unfortunately, due to the fact that those aircraft have custom APs, FGFSCopilot is NOT compatible with them. I've done most testing with the 787, Rallye, and Cessna Caravan. Anything with the generic AP dialog should be compatible, even helis.
Hyde wrote in Fri Sep 23, 2011 12:15 am:O.K. then where should I double click? I double clicked FG but nothing happened.
I'm not familiar with java program so this may be a stupid question but..
This is me assuming that you get icons on a Desktop or some sort of similar interface to work with. In Windows, simply double-click on an icon to open the program it represents. In this case, it would be the JAR file named "FGFSCopilot16". But, since I know you don't use Windows, I'm going to assume you run programs from a terminal command. In that case, it won't be as simple as double-clicking. Sorry to confuse you.
Hyde wrote in Fri Sep 23, 2011 12:15 am:I first run the fgrun. (FlightGear Launch Control 1.5.2)
Then change Executable: from /usr/local/bin/fgfs to /usr/local/bin/fgfs --telnet=9321 and run 777-200ER but FG never start up. fgrun might not take any parameter.
Strange thing is, this is the exact thing I do, only with a Windows file path, obviously. FG runs perfectly fine on my machine, and I happen to know of someone who got it to (sorta) work on his Linux machine. Let's just say it didn't work quite as expected, and I may have a few more bugs to squash, which I can't find any evidence of on my machine. Whether the user was filling in the correct data or not, I do not know, but for the things he claimed were happening, I can only assume he entered the wrong data.
Anyway, I'm currently trying an alternative to getting FGFSCopilot connected to FG.
EDIT: I've found it! Turns out that adding "--telnet=9321" to the executable was just a quick and dirty hack. Here's how it should be done. You need to add the following command:
--telnet=socket,in,5,localhost,9321,tcp.
To do this in FGRun, go to the last page, click Advanced...>Input/OutPut. Click New. Select the telnet protocol, the socket medium, the in direction, and port 9321. Since we're using telnet, make sure tcp is selected. And the hostname is localhost. Any frequency (Hz) of 5 or less should be fine. The program is a bit of a good-sized chunk for an addon, and will take a few seconds for each execution. So, if it doesn't seem to want to run at the frequency you specify, that's why. And don't worry if that happens. I've written in latency compensation factors and such to deal with it, making autolanding possible.
Let me know if that fixes the problem. If it does, I will update the README for the next release, which as usual, will be more awesome than the last release.