Csaba Halász wrote: > On Fri, May 21, 2010 at 11:26 AM, Stuart Buchanan wrote: >> My proposal is that users may optionally set a class or community they >> are flying in (say /sim/multiplay/class) that is exposed over MP. >> >> For example: >> Default - the default >> Newbie - for new flyers >> Student - those training - might be reseting regularly >> FGCom - those using FGCom - implies they will use realistic radio procedures >> Dogfight - for those engaged in mock dogfights (ignored by default) >> Ignore - for those who wish to be ignore (ignored by default) > > While you are at it, it might be a good idea to incorporate some other > class too, such as "single engine ga", "2 engine jet" and so on. Then, > even if a client doesn't have the model, it could pick a similar > replacement. > > "Your" class could simply be preassigned transponder codes (ranges), > thus achieving two goals for the price of one (I am thinking of more > realistic ATC/IFR).
I think the class of aircraft you fly is really orthogonal to the way that you are flying. My aim here is to create broad classes which are largely mutually exclusive, so users only select one, to represent the type of flying they are doing. There is certainly a case for including a "aircraft class" as a separate property. However, that would better be represented as a per-aircraft property to be exposed over MP, so the receiver could then choose the generic model to use. Of course, such an aircraft-class would also allow us to group aircraft more effectively within a launcher. However, that is really another enhancement :) -Stuart ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
