·
42 commits
to master
since this release
This Release brings some bug fixes and a new feature for FlightGear users!
- For Linux and Mac users; this is the last release built against openSSL v1.1.1.
- The next release will link against openSSL v3.0.
- If you do nothing, the plugin updater may download a version against v3 and if you don't have that installed, it will break your plugin and/or mumble.
- (Windows users are not affected, as the plugin links openSSL statically.)
- For your convenience, this release also contains a plugin bundle against openSSL v3, to be manually downloaded and installed.
Details:
-
PLUGIN: 1.0.3
- Fixed a bug that made the statusbot outputting missing data when reconnecting a client (#168).
- Fixed a bug that occurs when you connect two clients to one plugin instance (for example RadioGUI + Flightgear) that causes loss of an identity if it is not changing location or radio info (#169).
- RDF feature was broken (#157)
- Fixed two possible/hypothetical deadlock situations
-
RADIOGUI: 1.1.0
- Fixed a small bug that resets the spare frequency when choosing a location
- Added RDF feature, so you can now see where transmissions are coming from (also helpful to test/debug the RDF feature)
-
FGFS-ADDON: 1.2.0
- New intercom support when using FlightGears copilot feature (#166).
- New Keybinds: CTRL+SPACE now transmits on the intercom, ALT+SPACE on COM3.
- Support for arbitrary numbers of COMs (previously this was limited by the protocol side; #165)
- The combar now sets the buttons to "disabled" when the radio is not operable. This gives some feedback whether FGCom-mumble thinks the radio is working.
-
SERVER: 1.1.2
- Statuspage now has some more sanitizing for the provided database entries. This avoids garbled output when the statusbot provides missing data.
- Statuspage now is compatible to PHP8.
- Statuspage has a new tilesource configured, because the old one was broken
- Statusbot uses new JSON module (#168)
- Bots now print timestamps into the logs