Distributed Interactive Simulation: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (adding pointer to RFE discussion (and patch) related to XML configurable multiplayer properties) |
||
| Line 11: | Line 11: | ||
* Clients to set TOS (SO_PRIORITY) in IP packets (#1904264) | * Clients to set TOS (SO_PRIORITY) in IP packets (#1904264) | ||
* Protocol customizable using XML & Scripting (#1847251) | * Protocol customizable using XML & Scripting (#1847251) | ||
** allow multiplayer properties (property IDs) to become XML configurable [http://sourceforge.net/tracker/index.php?func=detail&aid=1906884&group_id=161928&atid=821811 (#1906884)] [http://sourceforge.net/tracker/index.php?func=detail&aid=1908456&group_id=161928&atid=821810 Note: there's a related patch available via the fgms patch tracker] | |||
* Protocol to publish own data, and subscribe to data from others, while multiplayer server acting as a data dispatcher (#1847251) | * Protocol to publish own data, and subscribe to data from others, while multiplayer server acting as a data dispatcher (#1847251) | ||
Revision as of 10:16, 29 March 2008
| This article is a stub. You can help the wiki by expanding it. |
Requirements
This section describes requirements to the FlightGear multiplayer protocol.
Architecture
- Architecture to strive to support DIS/HLA (#1859058)
Protocol features
- Protocol to use selective data propagation mechanism (#1904577)
- Clients to set TOS (SO_PRIORITY) in IP packets (#1904264)
- Protocol customizable using XML & Scripting (#1847251)
- allow multiplayer properties (property IDs) to become XML configurable (#1906884) Note: there's a related patch available via the fgms patch tracker
- Protocol to publish own data, and subscribe to data from others, while multiplayer server acting as a data dispatcher (#1847251)
- Protocol to publish multiple aircrafts from one client (#1849308)
- Protocol to support multi-crew and non aircraft-class vehicles (#1883587)
- Clients to display a default model of a given category (light single engine, light twin engine, light helicopter, light twin jet, spacecraft) when missing exact aircraft model (#1866514)
- Protocol to allow datalink communication; clients (aircraft, ATC) should be queryable via network (#1849311)
- Protocol to have simple configuration (#1899371)
Global state
- Server to support separate "worlds" to ensure that certain users only get to see certain users (#1866508)
- Server to maintain a global status for each world (#1866504, #1849311)
- date/time
- weather
- positions of automatic (random, AI) objects
- runway status
Data filtering
- Support use of Kalman filters for multiplayer data (#1867389)
- Validate plausibilty of distributed flight data (#1866527)