[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Animated sprites
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Animated sprites
- From: Jasper <jasper@xxxxxxxx>
- Date: Sun, 31 Jul 2005 23:53:34 -0700
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Mon, 01 Aug 2005 02:53:58 -0400
- In-reply-to: <4e4a11f805073120136f7a11d3@mail.gmail.com>
- References: <1122572867.1900.25.camel@localhost.localdomain> <42E96BEB.4090703@peak.org> <e82307780507310115784c8aed@mail.gmail.com> <42ED4C03.9000800@peak.org> <4e4a11f805073120136f7a11d3@mail.gmail.com>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
- User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Simon Wittber wrote:
If you're using OpenGL it depends. Texture sizes only come in powers of
two, so you can potentially save space by packing odd sized frames into
a single image of the correct size, or waste a bunch if you pack
texture-sized images into an odd size filmstrip. On balance it'll
probably save space if done well, provided your frames aren't all sized
in powers of 2 to begin with.
If you've got plenty of memory, using mipmapped textures allows you to
use any dimension texture, and also help's with texture quality if you
are doing a lot of zooming in and out.
It's pretty easy to use any size of texture, you just pad it with
transparent pixels out to the next power of 2, which I'd guess is
effectively how mipmapping handles this. This doesn't reduce the amount
of hardware texture memory used however.
-Jasper