Hello Christian,
Thank you very much for your prompt reply!
How can I assist you with respect to 5), A) and C) in terms of examples?
Shall I send saved games/matches and/or screenshots of the errors in question to your e-mail address?
Please advise.
Kind Regards,
Efe
--- On Fri, 13/3/09, Christian Anthon <address@hidden> wrote:
From: Christian Anthon <address@hidden> Subject: Re: [Bug-gnubg] Problems with Gnubg 04-Mar-2009 release To: address@hidden Cc: address@hidden Date: Friday, 13 March, 2009, 11:52 AM
Hi Efe,
please bear in mind that the releases you find on www.gnubg.org are development snapshots, and therefore some will be better than others. For example I recently made some changes to the hint code, which didn't turn out too well, and this covers 1), 3) and 4).
> 2) In addition, the line spacings in the "Analysis panel" and "Hint window" > are now much narrower which leads to a more cramped / crowded list of moves.
This is a tradeoff between details, and available space. But it should be different from september 2008.
> 5) For unknown reasons, there were couple of instances when the newer > version arbitrarily crashed during games/matches. The only common > characteristic that I noticed was that they were all happening when I was > clicking on the dice to make the next move (either for gnu or for myself).
Difficult to say without a more precise error report..
> 6) The size of the new Temperature Map window and the fonts are bigger now > which is obviously a huge plus! However, the best moves inside the squares > are listed upto 4 lines now (intentional?). For example, a double six played > 13/7(4) is not represented 13/7(4) anymore, but on four separate lines as > 13/7. Also, when you resize the temperature map bigger, the fonts of best > moves and equity over-adjust such that the characters overlap.
Intentional with the four lines since we had much more vertical than horizontal space. The font problem is probably specific to windows. I'll take a look.
> 7) When an offered cube is taken by the other player, the previous version > played a sound file ("take.wav"). This file is not played in the newer > version. After one accepts the cube, you immediately hear the
sound of next > dice rolling. Very minor issue but just wanted to point it out.
Possible. I don't pay too much attention to the sounds myself.
> 8) Finally, when I analyze the same match that I played in the 2 instances > of gnubg, the older version takes 5 seconds, whereas the newer version does > it in 45 seconds! (even starting the analysis first with the older version!) > This applies to any previous saved games of mine, too. The newer version > with exactly the same settings takes much more time to analyze the > games/matches? I have no idea why.
Are you sure the settings are the same. Another possibility is that the tutor now uses the eval settings, which may be different from the analysis settings.
> Last but not least, there are 4 general problems in both versions that one > would hope to be fixed in the future versions: > > A) The tutor does NOT warn
you (however big of a blunder your cube decision > is) when you are "Too Good To Double" and gnubg penalizes you by taking your > wrongly offered cube and ending the game, whereas you should have continued > to play for gammon. Everytime this happens I think that my cube was correct, > just to be disappointed later when I run an analysis of the match to see > that it was either doubtful, or even bad.
Examples please.
> B) When your actual move is marked doubtful (maybe even bad) in the Hint or > Analysis window and you perform a rollout just to be sure, sometimes you > find out that it is indeed the best move according to the rollout results. > But gnubg does not somehow "save" or "feed" this information into its game > evaluation. Then, when you go ahead and play the confirmed best move in the > game, it is still marked as doubtful, bad etc. which affects your
final > statistics :( This was not the case when I was trial testing Snowie 4 where > seemingly incorrect moves were accepted later after a proper roll-out.
Should be fixed in the near future.
> C) In the bear-in or bear-off phase, Gnubg does some strange checker plays > when it is either definitely winning OR definitely losing the game. For > example, with two checkers left on 1 and 2 points and having a last winning > roll of a 6-1, it moves the checker on the 2 point to the 1 point and bears > off the same checker, leaving one checker behind for an additional > unnecessary roll? I sometimes wonder whether it is psychologically messing > and teasing me by prolonging the pain :)) Likewise, when I am certain to win > a gammon, it does not continue the fight by trying to bear-in as much > checkers as possible to save the gammon and sometimes makes irrelevant moves > in its
own homeboard?
I've rarely seen this, but examples please.
> D) The statistics numbers in the "Player Records" do not match those of > "Match Statistics". One can verify this by erasing all player records, > playing a fresh, brand new match, running a match analysis and adding the > results to the "Player Records". The numbers in the two windows are > completely different (unless "Player Records" calculates something else?)
Player records will be removed very soon in favor of the player database.
Christian.
|