Talk:Distributed Interactive Simulation
From wiki.flightgear.org
Contents |
Related Discussions
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23964.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23969.html
- http://www.flightgear.org/forums/viewtopic.php?f=6&t=292
- http://flightgear.org/forums/viewtopic.php?f=2&t=5532
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17067.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16807.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22673.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18143.html
- About remotely managed properties: "I think the current MP protocol could be enhanced to provide this function fairly easily. The first step would be to (re-add) function to export arbitary properties. Then define the FDM properties to be exported from the master computer (running the FDM), and define control inputs to be passed the other way from the slave (running null FDM)." [1]
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25944.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25961.html
Still to be evaluated
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26356.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg07779.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg15810.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg12391.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg10793.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg07193.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg14615.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg15809.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg34627.html
Turning the AI traffic system into an MP client
(This should probably be put somewhere else, as it affects mostly the AI traffic system and is only relevant here because of additional requirements to the MP protocol)
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13245.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13211.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg08701.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg08708.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18423.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18682.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg34145.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18517.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13210.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18295.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg34143.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15027.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26021.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26038.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26040.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26053.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26054.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg26055.html
- http://flightgear.org/forums/viewtopic.php?f=5&t=6807
Multiplayer Server RFC:
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18128.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18317.html
MP Server
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg11931.html
- multiplayer separating environments (worlds) by using different instances [2]
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18143.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg10210.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg34139.html
- http://www.mail-archive.com/flightgear-devel@flightgear.org/msg11242.html
Bandwidth savings
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17067.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23994.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23970.html
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg24005.html
IVAO/VATSIM Discussions
Also search mailing lists and forums for IVAO/VATSIM
Regarding Multiplayer-aware ATC Support
(also see fgms/atlas sourceforge trackers, and search archives for "ATC", "VATSIM", "IVAO")
- http://sourceforge.net/tracker/index.php?func=detail&aid=1827096&group_id=161928&atid=821811
- http://sourceforge.net/tracker/?func=detail&aid=1905973&group_id=9456&atid=359456
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25729.html
Initial Data (PUSH/SUBSCRIBE)
Depending on the aircraft, each client will need to be provided with a bunch of properties to obtain initial state. These properties are likely to differ between aircraft (custom state such as animations, effects etc), and would ideally be defined by aircraft developers. So that clients connecting with an aircraft, will automatically provide this initial state, while other multiplayer clients would automatically subscribe to it. This would ideally be specified in each aircraft-set.xml file by aircraft developers. Also see [3]
