On Mon, May 24, 2010 at 5:47 PM, Jörg Emmerich wrote: > Thanks Stuart for the explanation - and I guess I understand now how it > shall work in an event with a group of people having the same goals and > settings (e.g. TGA). Although I still see the possibility that some > (younger or older) kids "try to show off" by changing their "grade" and > making as much trouble as possible - but that is a minor concern. So: > Fine for them! > > I also understand that the ATC can choose which people he wants to deal > with - and as ATC that would be great news for me (if I would believe > that people do not manipulate their grades! But I see that as a minor > concern!).
If that becomes a problem, the "serious" ATC users can change their usage class to a user-defined value which the "kid" does not know. The MP protocol will transmit a hash of this value, so it will be non-trivial to determine, if not very difficult. > But still I do not understand how that works for the users in an "open > ATC environment", e.g. just dropping in at EDDF on her/his flight from > EHAM to LSZH. What do they see? Does ATC tell them while approaching the > airport to set certain filters and or grades? Because also for the "just > passing by users" it would be rather confusing suddenly seeing traffic > that ATC did not see/control. I experience that problem very often, when > visitor come in or depart with AI-traffic-manager enabled -- they > suddenly get hit -- and blame ATC for a "very bad work"! I may not have explained that the user's setting indicating their usage-class is independent of the (multiple) usage-classes that a user can choose to display. So, in this use-case we have: - User A, cross-country from EHAM to LSZH - Tower, performing ATC duties at EDDF - Users B, C, flying under control from Tower at EDDF. We'll assume that Tower, B and C have set a usage-class of "FGCom", while User A has no usage-class set. By default, all users will see all aircraft except those with a usage class of "ignore". So A, B, C and Tower would see each other, Tower can invite user A to take part in the ATC simulation. If A wishes to take part, no action is required by anyone. That should be straightforward. To extend this use-case, let's say User A decides to dogfight user B which spoils the simulation. Tower then asks users B, C to switch to only display usage-class "FGCom", while Tower ignores user A explicitly, in case someone else would like to join. User A can then continue tailing user B, but Tower, B, C can continue their simulation without being bothered. Extending it further, say User D on a similar cross-country comes across EDDF. By default she will see Tower, A, B, C, with user A waxing the tail of user B. Tower can also see User D, and may invite her to take part, changing her usage-class to "FGCom" to become visible to users B and C. I think this provides sufficient flexibility, though it relies on the Tower staying "open" to new aircraft, rather than just hiding all non-"FGCom" aircraft. However, I think that is something for the Tower to decide. I hope this addresses your concerns, and indeed will be easier to understand in practise than my explanation :) -Stuart ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
