Author: enrico carrisco
Date: 23:16:36 01/06/05
Go up one level in this thread
On January 07, 2005 at 01:44:39, Peter Skinner wrote: >On January 06, 2005 at 09:44:16, Lex Loep wrote: > >>On January 06, 2005 at 07:24:52, enrico carrisco wrote: >> >>>On January 06, 2005 at 07:18:03, Lex Loep wrote: >>> >>>>On January 06, 2005 at 05:31:08, enrico carrisco wrote: >>>> >>>>>I haven't played with ChessPartner since 5.1 or 5.2 -- perhaps I'm missing an >>>>>important setting. However... >>>>> >>>>>When connected to ICC and trying to play with multiple UCI engines, ChessPartner >>>>>5.3 appears to lose track of who's turn it is. As I tinkered more, I noticed >>>>>that this problem disappeared after removing the TIMESTAMP client... This does >>>>>not appear to be the case when using native engines, however. (I couldn't >>>>>re-create this situation with LCHESS loaded...) >>>>> >>>>>Lastly, I doubt it makes any difference, but this is with the evaluation version >>>>>of ChessPartner 5.3. >>>>> >>>>>Any help would be appreciated -- thank you. >>>> >>>> >>>>There is currently a possible bug in ICC under investigation, is that perhaps >>>>what you are seeing ? >>>>See this thread: >>>>http://www.lokasoft.nl/forums?func=view&wid=37&forumId=1059&forumOp=viewThread&forumPostId=621#621 >>>> >>>>Lex >>>>> >>> >>>Thank you Lex.. One question, though. If it were clearly an ICC bug, why can't >>>I cause the same situation when using a native engine? Whether the engine is >>>native or UCI/winboard should have no bearing on how fast the bookmoves get sent >>>to ICC. It seems very odd to me that the native engine(s) aren't experiencing >>>the same issue (however, I've only tested LCHESS.) >> >> >> >>In the traces I have seen it is clearly a ICC bug. I don't know why it does not >>happen with LCHESS. This could be because LCHESS book handling is a bit slower, >>probably there is just a very small time window of maybe 10-20 millisecond in >>which this problems shows up. In fact here in the lab I have never been able to >>duplicate the problem. >> >> >>> >>>For the time being, selecting "None" instead of Timestamp seems to be a quick >>>fix for the problem. >>> >> >>The problem seems related to the timestamp program. >> >>I will soon release a ChessPartner update which has a option to introduce a >>small delay before sending move to ICC. This is of course a workaround. >> >>Lex >> >> >>>Regards, >>> >>>-elc. > > >Well if it is an ICC bug all interfaces would have this problem. Not if the other interfaces do not try to send moves (specifically book moves) at as fast of a rate as ChessPartner is. > >I _only_ have it with the ChessPartner interface and not with others like >Winboard/Arena. See above. > >I left Gandalf running overnight a few times in the Chesspartner interface only >to find it hung up in the morning. Over the Christmas holidays I left Gandalf >running in Winboard for 4 days straight, and not once had a problem of a >disconnection. > >Peter Remove timestamp (by selecting None under "Network Lag Control") and you will have no further problems.) As Lex said, he'll have a band-aid for this soon. -elc.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.