Le 28/08/2010 22:49, Vivian Meazza a écrit : > > AFAIKS in the code an aircraft gets a TACAN if the callsign is MOBIL1 > (060X), MOBIL2 (061X), or MOBIL3 (062X). On the other hand if the callsign > includes MOBIL, it is recognized as a tanker on MP. The property 'isTanker' > is not transmitted by default over the net and is not handled on receipt. It > is set to 'false' for all mp aircraft, and is only set to true if the > callsign contains MOBIL is the first part. > > The tanker property is used in aar.nas to determine if refueling takes > place. > > Hmm ... this one needs a bit more investigation ... mainly to remind myself > what I did in the first place :-). > > you're right, and thinks are now more clear to me. in fact the change in the tanker property is taken in account by aar.nas, so exporting it by mp will work.
I just wanted not to be forced to use a MOBIL callsign to do refueling by mp, this function should be enabled only by the tanker property. jano ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
