Josh Babcock wrote: > Right, it would be silly to send all that data to the server when all it > needs to know is where your are and what you can see. Plus the position > data could be sent at low resolution.
The best way to do this is actually dynamic: the server gets to send the X "most important" objects to each client per update. Importance can be defined in screen space -- think of it as the number of "pixels" of error that the receiving client would have if the update were not sent. This way your wingman always gets updated, and a burning/turning dogfighter will get frequent updates, but a jetliner moving in a straight line is nicely optimized and receives very few updates. You can also handle orientation error this way, by giving the object a "radius" and figuring that a 180 degree orientation different produces an error of that size. > Either way the server would have to be able to handle multiple instances > of the same callsign. Otherwise an invisible observer could silently > prevent a flier from connecting. Better would be to assign a prefix or suffix to duplicate callsigns, so that the second "andy" to connect becomes "_andy" or "andy-0", etc... Also, I'd suggest defaulting the callsign to the USER (unix, cygwin) or USERNAME (winnt) environment variables where available, to avoid the problem of zillions of identical "flightgear-user" planes flying around. Sane defaults are always good. Andy _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
