by wagnerw » Wed Dec 11, 2013 10:11 pm
Good evening,
Time for me to jump in, sorry, I did not know, that I might be needed.
We are facing several problems because of incompatibilities between the tools. Clement, please correct me, if I am wrong!
At first: The new server fgcom.flightgear.org is downward compatible, supports the old and the new version of FGCOM.
The FGCOM 3.0 client is sending sometimes slightly different frequencies as before. These new values are not supported by the old FGCOM server. So the old servers will not accept it.
The new server accepts old and new fgcom frequencies.
OpenRadar is prepared to support FGCOM 3.0. But, currently this support is not active, because there are many ATC contacts comming in with older versions. As I said above, only the new server suppports old and new fgcom clients. We tried it but had many troubles because of the small incompatibilies.
Changing this compatibility from old to new, means too, to use a different source for the frequencies of the airports. This is the reason that you Ross still have only one frequency available. FGCOM 3 will really bring some more for EHAM.
So for you, it should work to tune OR to fgcom.flightgear.org and set the frequency manually. So you will work on the new server. You will have to ask all incomming traffic to set their FGCOM clients to the new server too. Then you will be able to talk. It is not required to use the new FGCOM client , but you can use it (as much as I know it).
A final solution to these problems is to ask everybody to forget the old servers and use the new one. Until now, fgcom3 was in a beta/RC stage for me. Is it really ready for being used? Is the server stable (ok it is up for 80 days now) and has enough bandwidth to be used by everybody, Clement?
If so, people should be invited to change at a specific day on all possible ways, latest when FGFS 3.0 comes out.
Wolfram