public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Lincoln Peters <sampln@sbcglobal.net>
To: Hans Ronne <hronne@comhem.se>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Bugs in SDL interface
Date: Mon, 23 Aug 2004 02:16:00 -0000	[thread overview]
Message-ID: <1093202262.2792.13143.camel@localhost> (raw)
In-Reply-To: <l03130300bd4e0ec65388@[212.181.162.155]>

On Sun, 2004-08-22 at 02:37, Hans Ronne wrote:
> This is something we have discussed before, but perhaps it is worth
> repeating. I did some profiling which I posted to this list, and up to 90%
> of the CPU time was spent in the hit-unit animations. This was some time
> ago, so the numbers may have changed, but they are still a huge CPU drag.
> You can see this for yourself if you start a game with see-all off, several
> sides and a big map. You will find that if you position the window in a
> part of the map that you cannot see, and where no hit-unit animations
> therefore are played, the game picks up a lot of speed. The same is true
> for sides in the game that are not shown on the map - they finish their
> turn much more quickly than those who are not (in sequential games).

It *has* changed.  I find that, when I use the TclTk interface, my CPU
is hammered continuously.  Even when I'm just looking at the Startup
dialog, my CPU is so hammered that the mouse starts skipping!

(I don't think that the mouse thing is a memory issue because at the
same time I upgraded to a 2.167GHz CPU, I upgraded to 1GB of RAM.)

> 
> So the fact that this essential feature is still lacking in the SDL
> interface is important. With hit-unit animations it would become much
> slower.

I imagine that you could work around this by one of the following
methods:

1. Use an "alarm clock" rather than a loop to create a delay for the
animations.  The game would still be slower, but it wouldn't hammer the
CPU while doing absolutely nothing.

2. Run the animations simultaneously.  This would be slower than having
no animations at all, but it would be faster than running the animations
sequentially.  You could use the "alarm clock" mechanism again here.


One thing that might be a nice addition later on is sound effects like
those in the Mac interface.  Or better yet, sound effects that can be
set up by the game designer and support full surround sound (if the
computer is set up for surround sound), so that if a nuclear bomb
detonates in the north-west corner of the screen, you hear an explosion
in front of you and to the left.

---
Lincoln Peters
<sampln@sbcglobal.net>

I hope you're not pretending to be evil while secretly being good.
That would be dishonest.

  reply	other threads:[~2004-08-22 19:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22  6:39 Lincoln Peters
2004-08-22 13:13 ` Hans Ronne
2004-08-23  2:16   ` Lincoln Peters [this message]
2004-08-23  4:13   ` Jim Kingdon
2004-08-23 16:41 ` Eric McDonald
2004-08-27  4:36 ` Eric McDonald
2004-08-28  5:08 ` Eric McDonald

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=1093202262.2792.13143.camel@localhost \
    --to=sampln@sbcglobal.net \
    --cc=hronne@comhem.se \
    --cc=xconq7@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).