I am writing a 2d game in Python with Pygame. I only use Pygame for the rendering, and in the way I have written everything so far it is pretty easy to switch renderers, so I made a pyglet prototype and showed it to a friend.
Weird thing is, everything worked find on my computer, but he just got a plain black screen. He even got the black screen with the pyglet samples. He even reinstalled pyglet and python, and I even tried shipping an executable built with py2exe, but alas - he still got the black screen.
Now this is really demotivating. I would love to use pyglet, because it seems so much nicer, faster and easier to extend with opengl than pygame, but this is really preventing me from switching. I have never had any issues with running pygame everywhere.
What could be the cause of this, and should it affect my choice?
Weird bug in pyglet prevents me from using it
Two likely causes:
- Your executable expects folders and external resources on your computer that your friend doesn't have. You can find out what wrong and unexpected filesystem accesses take place with monitoring tools like Process Monitor.
- Your OpenGL implementation is OK, while your friend's computer has crappy OpenGL drivers that just fail miserably or inadequate hardware that actually doesn't support the OpenGL features your game uses.
Perhaps better logging and error handling can clarify the situation, but your friend is likely to play the game only after getting a new computer.
Omae Wa Mou Shindeiru
I'm sorry, I talked to that friend again and got more information.
He has the latest nVidia drivers installed, and opengl works in general. The thing that doesn't work is pyglet.sprite.Sprite. If I blit textures directly it works, but the pyglet's sprite class doesn't work.
Any ideas? Should I maybe report this bug to the pyglet devs?
He has the latest nVidia drivers installed, and opengl works in general. The thing that doesn't work is pyglet.sprite.Sprite. If I blit textures directly it works, but the pyglet's sprite class doesn't work.
Any ideas? Should I maybe report this bug to the pyglet devs?
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement