caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ANN: Chess III Arena 0.5
Date: Fri, 6 Jul 2007 20:41:58 +0100	[thread overview]
Message-ID: <200707062041.58352.jon@ffconsultancy.com> (raw)
In-Reply-To: <000001c7bf5d$de5bf260$ac01a8c0@johnyaya>

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 
initialized).

>  (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. 

Maybe.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The OCaml Journal
http://www.ffconsultancy.com/products/ocaml_journal/?e


  reply	other threads:[~2007-07-07 11:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 21:48 Grant Olson
2007-07-03 22:43 ` [Caml-list] " Jon Harrop
2007-07-04  2:18   ` Grant Olson
2007-07-04  8:00     ` Daniel Bünzli
2007-07-04 20:06       ` Grant Olson
2007-07-04 20:51         ` Bünzli Daniel
2007-07-04 21:22         ` Jon Harrop
2007-07-05  0:25           ` Daniel Bünzli
2007-07-05  3:05             ` Jon Harrop
2007-07-05  7:45               ` Daniel Bünzli
2007-07-05 12:52                 ` Jon Harrop
2007-07-05 13:37                   ` Daniel Bünzli
2007-07-05 13:52                   ` Daniel Bünzli
2007-07-05 14:22                     ` Jon Harrop
2007-07-05 14:43                       ` Daniel Bünzli
2007-07-05 23:40           ` Grant Olson
2007-07-06 19:41             ` Jon Harrop [this message]
2007-07-04 10:58 ` Jon Harrop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200707062041.58352.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).