Talk:Distributed Interactive Simulation: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 10: Line 10:


== Related Discussions ==
== Related Discussions ==
* http://flightgear.org/forums/viewtopic.php?f=10&t=8432 Fixing the MP environment 06/2010
* http://www.mail-archive.com/flightgear-devel@flightgear.org/msg11168.html
* http://www.mail-archive.com/flightgear-devel@flightgear.org/msg11168.html
* http://www.mail-archive.com/flightgear-devel@flightgear.org/msg35695.html
* http://www.mail-archive.com/flightgear-devel@flightgear.org/msg35695.html

Revision as of 13:46, 28 June 2010

Details

Related Discussions

Still to be evaluated

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)

Multiplayer Server RFC:

MP Server

Bandwidth savings

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")

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 [6]

Retrieved from "https://wiki.flightgear.org/w/index.php?title=Talk:Distributed_Interactive_Simulation&oldid=22551"