Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
ANN: Chess III Arena 0.5
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2007-07-07 (11:41)
From: Jon Harrop <jon@f...>
Subject: Re: [Caml-list] ANN: Chess III Arena 0.5
On Friday 06 July 2007 00:40:24 Grant Olson wrote:
> It went from 10 fps before to 70 fps with the display lists.

That's more like it. :-)

>  (1) There were a few hangs in the display while display lists were
> intially being created.  The code should probably be run at startup.

The memoization technique I used is a good way to avoid that problem because 
the display lists are lazily allocated. So you can't get premature allocation 
bugs (a problem if you try allocating global OpenGL entities before the GL is 

>  (2) The textures got screwy after text got displayed.  For example,
> working through a fools' mate, when I take the pawn the textures break.

Probably a bug in ATi's OpenGL implementation. IIRC, John Carmack used display 
lists to cache adaptive tesselations of Bezier surfaces in Quake III and had 
similar problems. nVidia's drivers are much better... :-)

> I didn't get around to all of the other optimizations.  I'm a little too
> busy right now to go through all of that, but I'll give it a try
> eventually. I'm wondering what impact meomizing the 'draw_frame_triangles'
> will have on memory usage.

System memory or graphics card memory? Does it take up much memory?

> I'm guessing that's one of the reasons the files were stored in their given
> format to begin with. 


Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The OCaml Journal