Re: [simspark-devel] [Sserver-three-d] [Fwd: Re: (Possibly) Faulty messages]

[Hedayat V. <hed...@gm...>]

Hi Mahdi and all,
@all: can anybody report about his experiment?!

/*Mahdi <zig...@gm...>*/ wrote on ۰۹/۰۲/۱۷ 04:33:20:
> Hi Hedyat
>
>   I tested that, redirected all the output to a file, and yet the 
> problem still haunts... Here is the file's inside:
>
> Successfully parsed file.
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))lj6) 
> (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))lj6) 
> (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))lj6) 
> (ax -0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax -0.00))
> Successfully parsed file.
> WorldModel::updateFromServerMsg: Unknown information: (n llj6) (ax 0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax 0.00))
> WorldModel::updateFromServerMsg: Unknown information: (n llj6) (ax 0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax 0.00))
> WorldModel::updateFromServerMsg: Unknown information: (n llj6) (ax 0.00))
> WorldModel::updateFromServerMsg: Unknown information: (ax 0.00))
> Successfully parsed file.
> Finished starting players.
> (DataPorter::recvMessage) Connection reset by peer
> Goalie out.
> (DataPorter::recvMessage) Connection reset by peer
> #2 out.
> (DataPorter::recvMessage) Connection reset by peer
> #3 out.
>
> I guess, that maybe it is because There is a specific order for 
> sending scene, init and beam commands in the first of initialization. 
> Is there any such squence in a continuos cycle series? Let me calrify 
> by an example:
>
>  cycle #0: Agent sends scene command
>  cycle #1: Agent sends init command
>  cycle #2: Agent sends beam command
I use the same sequence as above, and I've not seen any errors till now.  :(

Good luck,
Hedayat

>
> The reason for me to guess this, is that when I randomly change the 
> cycles of these commands, the error come in every cycle, so far my 
> current configuration is the one that has the minimum of these errors.
>
> Cheers
> Mahdi
>
>