Changes

== Servers ==

== Servers ==

<!-- Maybe we can switch to mumble://radio-mumble.flightgear.fr/fgcom-mumble some time... -->

<!-- Maybe we can switch to mumble://radio-mumble.flightgear.fr/fgcom-mumble some time... -->

* The main FGCom-mumble '''testserver''' is <code>mumble://fgcom.hallinger.org/fgcom-mumble</code>

* The main FGCom-mumble test server is <code>mumble://fgcom.hallinger.org/fgcom-mumble</code>

* The status page for that service showing all connected clients is at: http://fgcom.hallinger.org/

* The status page for that service showing all connected clients is at: http://fgcom.hallinger.org/

* Have a stock Mumble client >= 1.4.0 running, and load the plugin

* Have a stock Mumble client >= 1.4.0 running, and load the plugin

* Join a channel named `fgcom-mumble`

* Join a channel named `fgcom-mumble`

* Install the [https://github.com/hbeni/fgcom-mumble/blob/master/client/fgfs/Protocol/fgcom-mumble.xml FlightGear protocol file] (at [[$FG ROOT]])

* Install the [https://github.com/hbeni/fgcom-mumble/blob/master/client/fgfs/Protocol/fgcom-mumble.xml FlightGear protocol file] (at <code>[[$FG ROOT]]/Protocols/</code>)

* Start FlightGear with the new protocol active (add to launcher: <code>--generic=socket,out,10,localhost,16661,udp,fgcom-mumble</code>)

* Start FlightGear with the new protocol active (add to launcher: <code>--generic=socket,out,10,localhost,16661,udp,fgcom-mumble</code>)

* Start using your plane's radio stack (it uses default FGCom buttons, see below)

* Start using your plane's radio stack (it uses default FGCom buttons, see below)