Hi jomo,
just did a couple of tests with FGComGUI and FGCom 3.0. Short summary (if people don't want to read all the details):
FGComGUI works fine with FGCom 3.0, apart from the fact that the output is hidden in the GUI. I'll write down what I did.
I downloaded the Win64 package for FGCom 3.0 from
http://fgcom.flightgear.org/download/ and unzipped it to C:/FlightGear/FGCom. I then did the following:
- Open FGComGUI
- Go to Settings, point the exe to the FGCom 3.0 exe (C:/FlightGear/FGCom/bin/fgcom.exe in my case) and set the server to fgcom.flightgear.org
- Set mode to echo-test
- Open http://fgcom.flightgear.org in your favourite browser and make sure you can see it next to the GUI.
- Press "Start" in the GUI and see "guest" appear on the fgcom.flightgear.org list after some seconds.
- Press "Stop" and see "guest" disappear after some time (this can take some 30 seconds, I think the server keeps the connection open to smooth out interruptions).
I don't see any output in the GUI log, but when I copy the command line that's shown to an empty console, I get the usuall output (calls, frequencies, in range etc.). The output/input volume settings are ignored, but for the rest it all works fine. With all three servers: the delta server, fgcom.flightgear.org and fgcom01.flightgear.org.
So, the lack of output in the GUI is misleading. FGCom is just working fine in the background.
When using "Normal mode" in combination with FlightGear, I get the same behaviour. FGCom works fine, but I don't see any output in FGComGUI. Check the fgcom.flightgear.org list to confirm that you're connected. Make sure your COM1 is set to a frequency in range, else you won't be displayed in the list.
Conclusion: FGComGUI works fine with FGCom 3.0, apart from the fact that the output is hidden. I don't know how to build FGComGUI from source, but if anyone does, he/she now knows what to work on. Please give the procedure that I outlined above a try and report if that works or not. If it doesn't work, please indicate at what step, what settings etc., so we can try to find out why.
Next I'll address some of jomo's other comments that I encountered during my tests:
(Even so I would prefer if FGCom-3.3 could be started as easily as it is for FGCom (just type "fgcom").
Works fine here. I can just run C:/FlightGear/FGCom/bin/fgcom (or C:/FlightGear/FGCom/bin/fgcom.exe) and it works without any options or configuration changes.
Later in your posts, you say "just type fgcomgui, that starts FGCom automatically". Is that the same as above? I don't have FGCom starting automatically when I open the GUI. I first need to press "Start"...
Shall a user not be able to work with the "standalone FGCom-3.0" when FGFS is not running? How could you set the airport frequency then?
Not sure what you're asking here, but as far as I could see, you cannot set the frequency in FGComGUI right? You either use OpenRadar or FlightGear for that. And that works fine with FGCom 3.0 as far as I've tested... Or is there a third way to run (the old) FGCom that I'm unaware of?
Cheers,
Gijs