624
edits
FGCom-mumble: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
{{caution|The plugin relies on '''Mumble 1.4.0''' which is not yet released. | {{caution|The plugin relies on '''Mumble 1.4.0''' which is not yet released. | ||
To test FGCom-mumble, you thus need to self compile mumble and murmur.}} | To test FGCom-mumble, you thus need to self compile mumble and murmur. I wrote a small guide on how to do that on debian/bullseye: https://github.com/hbeni/fgcom-mumble/wiki#compiling-mumble-140-plugin-branch-from-krzmbrzl-on-a-debian-testing-bullseye-system}} | ||
{{note| This is currently in development and has no stable release for productive use yet. Expect lots of bugs! }} | {{note| This is currently in development and has no stable release for productive use yet. Expect lots of bugs! }} | ||
| Line 27: | Line 27: | ||
== Servers == | == Servers == | ||
<!-- Maybe we can switch to mumble://radio-mumble.flightgear.fr/fgcom-mumble some time... --> | |||
<!-- | * The main FGCom-mumble '''testserver''' is [[mumble://fgcom.hallinger.org/fgcom-mumble|mumble://fgcom.hallinger.org/fgcom-mumble]] | ||
* The status-page for that service showing all connected clients is: http://fgcom.hallinger.org/ | |||
* The main FGCom-mumble | |||
* The status-page for that service showing all connected clients is: http:// | |||
== Project main goals == | == Project main goals == | ||