FlightGear Multiplayer Server: Difference between revisions
Jump to navigation
Jump to search
(Attempted to correct incorrect information. It is not good yet.) |
Oschroeder (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
# Crossfeed server - everything the server receives from local users and other servers is forwarded to the crossfeed server(s). Intended for running several connected fgms instances on the same host, e.g. for providing both a tracked and untracked service, without incurring additional external traffic. | # Crossfeed server - everything the server receives from local users and other servers is forwarded to the crossfeed server(s). Intended for running several connected fgms instances on the same host, e.g. for providing both a tracked and untracked service, without incurring additional external traffic. | ||
# Tracker - The server sends a digest update for each local user to the tracker every 10 sec. | # Tracker - The server sends a digest update for each local user to the tracker every 10 sec. | ||
# HUB - normally Servers do not send packets they receive from a server to other relays. A HUB server sends data from servers to all relays it knows about. | |||
Special callsigns: | Special callsigns: | ||
* "''' | * "'''obsXXXX'''" (replace X's with any character you like) allows a connected FlightGear client to view all other MP pilots worldwide (position data and chat messages), yet remain invisible to them and on [[MPmap]]. | ||
* "'''mpdummy'''" prevents the pilot from being tracked on FGTracker. Not recommended - if several users use this callsign some will be ignored by the servers. Connect to an untracked server instead. | * "'''mpdummy'''" prevents the pilot from being tracked on FGTracker. Not recommended - if several users use this callsign some will be ignored by the servers. Connect to an untracked server instead. | ||
Revision as of 19:03, 26 August 2010
FGMS or FlightGear Multiplayer Server is a standalone network server for FlightGear and licensed under the GPL. It allows flying with other pilots over a network inside FGFS.
Types of server lists that can be configured in a server configuation:
- Relay server - the other servers in the network. Each has to have the full list (minus itself) for proper network function.
- Crossfeed server - everything the server receives from local users and other servers is forwarded to the crossfeed server(s). Intended for running several connected fgms instances on the same host, e.g. for providing both a tracked and untracked service, without incurring additional external traffic.
- Tracker - The server sends a digest update for each local user to the tracker every 10 sec.
- HUB - normally Servers do not send packets they receive from a server to other relays. A HUB server sends data from servers to all relays it knows about.
Special callsigns:
- "obsXXXX" (replace X's with any character you like) allows a connected FlightGear client to view all other MP pilots worldwide (position data and chat messages), yet remain invisible to them and on MPmap.
- "mpdummy" prevents the pilot from being tracked on FGTracker. Not recommended - if several users use this callsign some will be ignored by the servers. Connect to an untracked server instead.
(Reference: fgms-0.9.13/src/server/fg_server.cxx)