14
edits
(Fix grammar.) |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
Line 28: | Line 28: | ||
== 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 | * 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/ | ||
Line 54: | Line 54: | ||
* 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) |
edits