by TheKezStrel » Wed Dec 23, 2020 4:17 am
FGCOM Testing Server update 2020/12/23 02:00
More progress has been made with regard to the stability of my FGCOM Testing Server, with thanks to lru, one of our IRC chatroom participants this evening.
I have had to downgrade the base operating system to one that runs a 32bit system and not x64(amd) system. This is to enhance functionality and stability of the current client software architecture.
Base Asterisk version has been lowered and is more stable with all FGCOM v3+ external instances that I have personally tested so far.
Using the Internal FGCOM on build 2020.1.3 still has the three frequency change issue and still disconnects. Both my tester this evening and myself were having audio issues with the built in version. When running external FGCOM on windows, this produced the best personal results. All versions I have tested seem to switch channels correctly, though FGCOM Client 3.4.0 built Feb 15 2015 has had the best stability and compatibility so far with regard to long connect times with no audio going over the VOIP link and Frequency switching.
FCGOM -Testing server is in ALPHA STAGE for diagnostics and testing.
I invite you all to try and use the server at test airports EGXW (RAF Waddington) and EGLL (Heathrow) with an external FGCOM client that is provided with your FlightGear install and share your results. Using the built in FGCOM is slightly trickier and still has force crashes at present. Nevertheless, you are welcome to try and give feedback.
If you are already set up for using FGEXTEND with mumble, you can run an external FGCOM instance straight away.
If this will be your first time setting up for FGEXTEND or an external FGCOM, please add the line
--telnet=5401 --generic=socket,out,2,127.0.0.1,6661,udp,fgcom
to your startup settings in the FlightGear Launcher.
Run External FGCOM
For me on Windows ( yeah i know!) my shortcut is this, with my callsign added at the relevant spot without the square brackets.
"C:\Program Files\FlightGear 2020.1.3\bin\fgcom.exe" --server=fgcom.ddns.net --host=127.0.0.1 --port=16661 --callsign=[MAX 7 CHARACTERS AND SHOULD BE YOUR MULTIPLAYER CALLSIGN] --username=guest --password=guest
You should have a command window open with FGCOM loaded.
Run Your FlightGear Session.
Available global frequencies are
EchoTest (910.000)
Music Box (911.000) - to check if you can hear the audio stream from the server
Air2Air 1 (122.750)
Air2Air 2 (123.450)
Airfield Frequencies are
EGXW Waddington Departure 123.300
EGXW Waddington Tower 125.350
EGLL Heathrow Information 128.075
EGLL Heathrow Tower 124.475
EGLL Heathrow Ground 121.900
EGLL Heathrow Director 134.975
EGLL Heathrow Delivery 121.975
These are the only frequencies I have loaded at the moment, with more to be added if stability is good. Also looking at setting up a more permanent server should this work.
Good luck, and I look forward to hearing your experiences.
Kez
Currently developer of the new FGCOM server. Testing server fgcom.ddns.net is available. Select fgcom.ddns.net in the MULTIPLAYER/FGCOM Dialog box in FlightGear.