Reducing pygame cpu-load to < 4 %

Noah Kantrowitz kantrn at rpi.edu
Sun Dec 9 23:34:58 EST 2007


The Python way is explicit over implicit. pygame.image.load() will
return a surface of the form you actually saved, you must explicitly
convert it to another format if you saved it in a format different than
what you want for blitting.

--Noah

Bernardo Innocenti wrote:
> On 12/09/07 19:51, Roberto Fagá wrote:
>
>
>> I think for now pygame is doing with 16bits at default yet, and I
>> wrote wrong, the second parameter from set_mode are the flags, depth
>> is the third parameter. I also used 12bits too to test, for games when
>> colors don't matter so much can be a good choice.
>
> Even a lower depth, like 12bpp, is going to result in a slowdown
> with the Geode GPU.  The best depth is the same of the screen.
>
>
>> Was 16bits the default depth since the first pygame for XO? I
>> remembered that it was creating 32bits for me by default, but with
>> older versions of Sugar...
>
> It's the default of the X server.  It would be nice if pygame
> would create surfaces in the screen depth by default, so that
> application developers wouldn't have to care.
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071209/d94ebcfc/attachment.sig>


More information about the Devel mailing list