-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.5.0.0 lost on time #1
Comments
btw. i switched the title .. at first i thought the main issue was that castling rights were not updated (after castling on move 5 and 6) but i was mistaken : the shown FEN was my starting position - sorry. |
Time handling code not really set up for these parameters. Either expected (1) "movetime" parameter or (2) full set of time parameters with "movestogo" as well as "wtime" and "btime". With these parameters it fell into option (2) and a further issue was then created given the negative time passed in for "btime". Code changed to handle this set of parametres: if you do not provide full parameters it just uses either the "wtime" or "btime" as if they were "movetime", depending on whose turn to move. This change is in v.0.5.0.2. Will close later if this does indeed fix the issue. |
Actually previous comment was not accurate. Needed instead to use option (2) but allow for issue with a negative other time. |
OK Net5.0 RC2: When building a solution with a target runtime ID an error is given #14281 Here is another workaround which may be better than creating publish profiles for each project.
Then when you build or publish, specify the RuntimeIdentifier with the MyRuntimeIdentifier property instead of the --runtime parameter. For example: now this works for me :
note: i should give an |
regarding the time management : v0.5.0.2 doesn't lose on time but it has a poor time management .. in a 7m+3s game it takes almost all time upto move 4, then using only the 3 sconds bonus for every move .. it was a draw, but it might have won ..
|
while testing your v0.5.0.0 in CuteChess the engine lost on time .. it was a game with fixed start position (Flounder had to open the game with 1.Nf3) against another engine (on another PC), which moves i entered by hand .. here's the game :
i must say Black had negative time for many moves, because i paused frequently, but normally CuteChess allows this when a human is playing ('human' = Certaur manually), so i guess this was NOT the cause ..
here's the log tail .. sorry i couldn't save the full log, i switched the CuteChess window pane several times which makes CuteChess refreshes its log ..
[ i'm on Xubuntu 22.04 ]
The text was updated successfully, but these errors were encountered: