I've just pushed a new FGCom standalone (FGCom built-in haven't been touched at all). This update is in fact a total rewrote from scratch of the application.
What is new ?
positions.txt and special.txt are integrated in the binary
FGCom was looking for 2 text files (positions.txt and special.txt) if you lost these files or moved the fgcom.exe away from these files FGCom wasn't able to run.
Now these file are no longer required because they are integrated in fgcom.exe. That way you can move fgcom.exe where you want without taking care of other dependent files.
Reduce CPU load
FGCom was running as many loop as fast as possible and processed all data for each loop.
Now FGCom is processing data only if they are relevant and skip the loop as soon as data stop to be updated (e.g if you are on parking without moving and without using your radio in FlightGear, FGCom don't process any data but as soon as you use your radio or you are moving FGCom will process the required data)
New mode: OBS (observer) for listening a frequency
This new feature give you the possibility to listen a frequency without need to run FlightGear. FGCom was setting the frequency because FlightGear sent data.
Now you can tune a frequency and an airport ICAO then listen this frequency. That way you can install FGCom on a low-end laptop and listen the tuned frequency without any FlightGear session required.
While you use this mode you can't talk at all. This feature is only designed for listening a frequency.
Source code ready to be used with another library
For those who would like use FGCom with another library (IAXClient) you can easily implement it because all dedicated code to the library is wrote in helper functions.
Support for COM1 and COM2
You can switch between COM1 and COM2 in FlightGear then FGCom will recognize the select COM and use it.
Fix bug where frequencies conflict avoid switching between similar frequency in range
FGCom was unable to switch between different airport with the same frequency until you switch to another frequency then come back to the previous frequency and finally connect to the new airport (nearest)
Now FGCom will automatically switch to the nearest airport matching the tuned frequency. That way you can fly all over Europe without touching the radio frequency and FGCom will select the correct airports during your flight.
Better logging information and debug information
The debug information are more informative and helpfull for debugging FGCom.
Also usual logging information will now tell you much more things: selected freq for each COM, which COM is used, connect, disconnect and the reason of the disconnect.
Range depends on altitude
FGCom is now aware of your altitude and can compute the range (via a basic function without taking of the terrain).
This feature improve the realism of your flight.
Some example for those who don't have time to read the Usage of this new FGCom (available via a simple ./fgcom --help)
How to use the ATC mode ?
The ATC mode give you the possibility to record an ATIS message on the frequency of an airport. As example if you want record the ATIS message for LFMV, the ATIS frequency is 120.825MHz:
- Code: Select all
./fgcom --atis=120.825 --airport=LFMV
This feature is working on fgcom.flightgear.org server.
How to use the OBS mode ?
If you just want listen at a frequency, as example listening LFMV on 122.600MHz:
- Code: Select all
./fgcom --frequency=122.600 --airport=LFMV
How to use the Echo Test ?
You just need to run:
- Code: Select all
./fgcom --frequency=910
How to use the Pilot (normal) mode ?[b]
Just run FGCom:
- Code: Select all
./fgcom
[b]How to get more informations on options ?
Just ask for help with:
- Code: Select all
./fgcom --help
These new feature are only available in GIT version until the FlightGear 3.4 will be released. Feel you free to test and report feedback.
Regards,
Clément