[ggo-discussion] Re: glGo 1.2 beta
- From: Matthew Rohn <mdrohn@xxxxxxxxxxx>
- To: ggo-discussion@xxxxxxxxxxxxx
- Date: Fri, 11 Mar 2005 15:07:35 -0500
I apologize for the late feedback, but I haven't had time to fiddle with
the new version until today. I've been playing with the territory
estimator, and have run across some bad behavior, including a few crashes.
I have found that in certain positions the territory estimator can take an
extremely long time to do its work. My computer is what I would call a
weak but by no means obsolete system (WinXP/1.4GHz athlon/512MB DDR/Abit
KG7-R/Geforce3 with latest drivers). As I am writing this, glGo has just
passed the twenty-minute mark estimating territory on an live observed
game, the whole time at over 90% of CPU. It appears the estimator has
frozen in a loop, and it would be nice if there were a way to stop it
without having to close the game window, since that defeats the purpose of
observing a game in the first place.
I'm writing now after a short break, during which time the game that caused
the estimator to freeze has ended. I saved and closed the game to stop the
estimator, then loaded the saved game and tried again from the same board
position, and glGo came up with a territory estimation in only a few
seconds. But unfortunately I've encountered a few other problems in
testing this. glGo will sometimes crash and close when I try estimating
this same board position multiple times in raipid succession, or when I
page through the game moves using the arrow keys while an estimation is in
progress. The estimator also sometimes freezes as described above while
analyzing positions in the late early game.
Sorry for the diary-like structure of this post... I have been composing
this on Notepad, and while writing, I have experienced another crash which
is very simple to invoke, and 100% reproducable.
1) Open a saved sgf file for viewing with glGo. (this bug does not occur
for observed games)
2) Open a notepad window so that it is the active window and on top of the
3d game board pane in glGo.
3) Move the mouse from the Notepad window to hover over the 3d Game board
4) glGo crashes!
There are two other bugs I have seen involving the drawing of the 3d game
board as well.
First, glGo doesn't like being on top of or behind translucent
windows. Applications such as DUMeter and Trillian allow partial
transparency of their windows, and when one of those windows overlaps the
game board, bizarre artifacts occur. I am not sure if this is a problem
with glGo or Windows, but I thought it was worth bringing up.
Second, the game board will not display at all, or will draw only in a
skeleton form, if you do the following procedure:
1) Launch glGo and click the 'load a game' button
2) Do not load a game from the load SGF file dialog. Keep the dialog open.
3) Open a game through another means, such as double-clicking an SGF file
in windows explorer, or launching a shortcut.
4) The game board doesn't draw. Close the 'load SGF' dialog, and the board
will draw with limited graphics (b/w, no textures, etc).
Keep up the great work with glGo, it is still by far my favorite panda
client and SGF viewer.
At 08:58 PM 3/2/2005, you wrote:
>Hello,
>
>glGo 1.2 beta is available here:
- Follow-Ups:
- [ggo-discussion] Re: glGo 1.2 beta
- From: Peter Strempel
- References:
- [ggo-discussion] glGo 1.2 beta
- From: Peter Strempel
Other related posts:
- » [ggo-discussion] glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- » [ggo-discussion] Re: glGo 1.2 beta
- [ggo-discussion] Re: glGo 1.2 beta
- From: Peter Strempel
- [ggo-discussion] glGo 1.2 beta
- From: Peter Strempel