Jörg,
jomo wrote in Wed Dec 18, 2013 8:48 am:I hope he is keeping up his good services until your service has proven to be something better.
I wouldn't say that my "service" is better, but that the "features" available on fgcom.flightgear.org are better.
A developper is here to implement new features and fix bugs.
A hoster is here to host a project and provide a quality of service.
I am a developper, not an hoster.
Similarly, FGMS (the flightgear MP server) has been developped by a developper, but his project is hosted by a couple of hoster.
So please, don't ask me to provide a "quality of service", I'm not the good person for that, however you can ask me to fix bugs and new features.
fgcom.flightgear.org is better because:
* You are able to check if you are correctly connected to the server in real time (
http://fgcom.flightgear.org/ )
* You are able to check who is currently connected to the server in real time (
http://fgcom.flightgear.org/ )
* You are able to look at the history of your session (
http://fgcom.flightgear.org/history.php )
* You are able to know which airports/frequencies is the most used (
http://fgcom.flightgear.org/stat.php )
* You are able to record an ATIS message on the server like it's done in real life
* You are able to listen an ATIS message on the server like it's done in real life (you can test the feature at LFML - 125.350MHz)
* The problem about wrong frequencies is solved (e.g 127.320MHz vs 127.325MHz)
* fgcom.flightgear.org uses the last apt.dat file from X-Plane
* Because fgcom.flightgear.org uses the last apt.dat he is synced with the upcoming FlightGear version (v3.0 in february 2014)
* Because fgcom.flightgear.org uses the last apt.dat he has a lot of new frequencies / fixed frequencies (e.g EHAM)
* fgcom.flightgear.org uses the Speex codec: it reduce the bandwidth usage and improve the audio quality
* fgcom.flightgear.org is ready for the 8.33KHz and has already almost all 8.33KHz frequencies ready to use (e.g at EDDS 118.805)
Ok this was only the advantage on server side, now the advantage on client side:
With FGCom 3.0:
* You can use 123.450MHz (
http://mapserver.flightgear.org/git/?p= ... 66d422f7bc )
* You can record an ATIS message on fgcom.flightgear.org (e.g ./fgcom -f120.825 -aLFMV )
* The range is calculated dynamically depending on your altitude
* The maximum range is 100nm like the MP protocol
* You can download FGCom 3.0 for Windows 32/64bits and Linux 32/64bits (no need to compile it anymore)
* You can run FGCom 3.0 without command line at all (FGCom 3.0 standalone provide a run_fgcom.[sh | bat] file that you just need to double-click)
* The default server is no longer "fgcom.flightgear.org.uk" (out of service since more than 1 year)
* FGCom 3.0 standalone is shipped with the FlightGear installer (no need to install FGCom + FlightGear because FGCom is automatically installed with FlightGear)
* The callsign sent over UDP by FlightGear is handled by FGCom 3.0 and used by
http://fgcom.flightgear.org/* FGCom 3.0 is integrated in FlightGear 3.0 (this is certainly one of the better feature that a lot of people was waiting for)
I'm sure I forgot some other advantages but I think the list is already enough long.
All of these doesn't make it better ? Can you tell me where you are seeing something wrong with all these new features/bugfix ?
I'm ready to improve all the work I already done. You just have to tell me "Hey Clément I found a bug: the ???? is not working as expected, can you fix it please ?"
fgcom.flightgear.org is running since 87 days now, he has handled 31 days of continuous user connections (
http://fgcom.flightgear.org/stat.php ) This make me think that my work is stable and ready to be used by everybody, but like I said, the fgcom.flightgear.org server has to be hosted on a professionnal hosting.
I have some other features in mind like:
* Recording FGCom conversation and make them available for download, that way a user can listen his FGCom session after his flight
* Stream FGCom conversation on web, like it's done on liveatc.net
* Show up on MPMap who is using FGCom
* Show up in FlightGear multiplayer list who is using FGCom
But for now I'm waiting to see if all the new features I've implemented on server side + client side are used before continuing to add more features. (Also I would ask if these feature make sense to the community, is it wanted ? do you think it's a cool features ? or you don't think these features will be usefull ? )
Jörg, feel you free to ask me if you have any question about all these new features, if you don't understand some of them or if you don't know how to uses them.
I'm ready to take the time to explain you more deeply all the improvement I done on FGCom (server/client side)
I hope all the months I spend to make FGCom (server/client side) better is appreciated, I done a lot of work, I added a lot of features, I fixed a lot of bugs (100nm limitation, 123.45MHz usable, fix the ATC mode in FGCom client....)
Regards,
Clément