Comments on: Creating a game with PyGlet and Python

By: Weeks Unknown – Scaling Troubles | Import Soul

Weeks Unknown – Scaling Troubles | Import Soul — Sun, 27 Feb 2011 05:19:31 +0000

[...] good use of hardware surfaces by default. In learning pylet i stumbled upon some basic guides on game desgin and another guide that provides a basic camera class for me to base my scrolling and zooming [...]

By: Michael

Michael — Tue, 28 Dec 2010 00:53:35 +0000

Thanks a lot for this tutorial. It’s very clear, well written and nicely laid out. I’m sure things have changed a lot in pyglet by now, but I know very little about game programming, and your tutorial was a great introduction. I really feel like I’ve gotten a good insight, so, again, thanks very much.

By: Matt

Matt — Fri, 24 Jul 2009 09:27:39 +0000

Billy Bob,
try looking in the source code, it’s just code there. that’ll show you where.

PS: great tutorial!
PSS: i heard that there’s an update for pyglet that adds more sprite functionallity, a sprite class, maybe? downloading the new one and checking the documentation now…

By: Billy Bob

Billy Bob — Sun, 14 Jun 2009 23:28:03 +0000

When you start modifying the main loop about two thirds into the tutorial you begin to add function like crazy, but never identify where they are to be placed.

By: Blake

Blake — Tue, 10 Feb 2009 00:29:03 +0000

hey i am new to using python and i have been trying to study and understand it but i copied the coding you have and when i run it the only thing that comes up is a black screen and the FPS. Is there advise you can give me for this?

By: Olberg

Olberg — Tue, 06 Jan 2009 13:14:27 +0000

Check Cocos2d – http://cocos2d.org/

By: selsine

selsine — Thu, 19 Jun 2008 23:44:46 +0000

Thanks for the tip SeaRider. I wrote this code using the Beta version of pyglet so I wouldn’t be surprised if a few things have changed since then.

Thanks for letting me and the other readers know.

By: SeaRider

SeaRider — Mon, 16 Jun 2008 21:04:41 +0000

I found that on running the code from the first code box, the window fails to close until you tell it to once you’ve exited the loop (at least, running under Windows). I put

space.close()

after the call to space.main_loop(), and it then works properly.

By: selsine

selsine — Fri, 22 Feb 2008 02:11:15 +0000

Hi Jonathan,

Thanks for letting me know! I’ve added it to the tutorial list.

Hi Stephen,

Do you still have the code around? Or could you let me know what you tweaked? If you have some improvements I would use them to update this tutorial or write a new one.

By: Peter

Peter — Wed, 06 Feb 2008 00:20:39 +0000

CPU Utilisation:

I changed the FPS limit in …clock.set_fps_limit(30)… to 10, 15, 30, 60, 90 and also uncommented the entire line and noticed some interesting benchmarks on CPU utilization. On a 1.4Mhz Pentium M laptop running Ubuntu 7.10 I got the following average CPU utilization percentages from top running in another terminal window of the python process running this game:

10 FPS = 9.3% CPU
15 FPS = 15.3% CPU
30 FPS = 24% CPU
60 FPS = 39.6% CPU
90 FPS = 16.3% CPU
Uncommented = 7.3% CPU

It is noted that at 90 FPS and Uncommented the game window maxed out at 60 FPS.

Also noted, pyglet as it stands has a bug on linux, at least on Ubuntu 7.10, with Compiz/Beryl running. The window border frame and widget bar is not drawn and you only see the windows canvas on the screen. This severely limits the users ability to quit execution of the program without an explicit menu option programmed into the main program.

With Compiz/Beryl being enabled more and more by default on the Linux distros to provide advanced windowing features / eye-candy this may be a more serious problem.

I wonder what people on other platforms observe when trying out the same experiment.