"Martin Spott" wrote > I'd like to express a wish: _Please_ try - as long as possible - not to > add redundant features. There are already three multiplayer extensions > for FlightGear - partially unmaintained .... > I'd love to see them merged somtime in later future, probably sharing > common modules bus driving different protocols, if necessary. > > Please remember: This is only a wish, > Martin. > --
Ok -- lets run it down -- I'm aware of the basic raw multiplayer and the OLK code (which I peeked at and am still trying to figure out the details) and what is the 3rd one ?? Dont see anything in CVS for it...... I'm looking at creating a new protocol module to handle the low level details of the connection, and a hud overlay like the OLK code to handle radio messages and user input, enabled only when the protocol module is activated on the comand line, some gui to handle canned radio messages and adhoc message input (standard messages such as ID, traffic control requests and replies, etc .. the goal with canned messages is that they will be sent as unique messages that other programs can easily recognize and process, such as an ATC simulator if someone should write one) The HUD setup is going to be pretty basic, and could be used as a general HUD add-on for any network code since its main functionality will be displaying radio messages... suggestions on how to implement it to be usable by any module that needs to display a scrolling list of messages would be welcome "Erok Hofman" wrote: > Excellent. > I was thinking it would be a good idea to set this up as a side project > and just sent the necessary code updates for inclusion in CVS. I can work via patches for the time being, but was really hoping for developers access to CVS at some point. Make my life a lot easier getting updates to the server machine (I work for an ISP and have several machines to play with :), and to the team that will be helping me test (I have already recruited a number of friends to help out :) I guess as a last resort I can fork the code and setup my own CVS server -- but that doesnt pay off in the long run :) > > Some things you might want to remember is to use plib/SimGear functions > whenever possible because that makes it easier to maintain cross > platform compatibility. Thats an absolute neccessity :) One of my long term ideas is to have the server load the terrain data around each aircraft in play for use by automation/AI code running at the server. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
