Hi Stuart,
Stuart Buchanan schrieb am 25.11.2007 16:09:
> I haven't seen this bug (yet), so the following is to some extent guesswork 
> based
> on the information above.
>
> The MP chat system keeps a hash of all the incoming messages keyed against the
> callsign of the user. This is the only way I could think of to keep a track 
> of the various
> messages to avoid repeating them.
>
> My suspicion is that there are multiple MP aircraft with the same callsign in 
> the session.
> My there should be multiple mpdummy aircraft I am not sure, but it is 
> obviously
> a situation that is going to become more common as FG MP becomes more popular,
> so the chat sub-system will have to deal with it.
>
> As a first attempt to fix this, I've uploaded a new version of 
> multiplayer.nas which 
> ignores duplicate callsigns (and also uses "var" properly) to
>
> http://www.nanjika.co.uk/flightgear/multiplayer.nas
>
> I think this will solve the problem. If you could try it and report back, 
> that would 
> be great.
>
> -Stuart
>
>
>   
I am testing your patch right now. I am sure, that the bug is not due to 
two players logged on the MP-server with the same Calls-Sign. I think it 
could be related to the timing-reset, e.g. after resetting the 
simulator. I think, I get it more often, If I am debugging/developing a 
FDM, which causes a reset every few minutes.  Or maybe it is necessary 
to do a reset short time after receiving a MP-message? Or to do a reset 
short time after ther message-sender did a reset or time-out? Maybe this 
causes double-callsigns in the property tree and Stuarts patch solves 
the problem? Who nows..

Maik

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to