I figured out that the problem is an incompatibility between the pyglet sprite module and AMD video cards. This problem came up on Stack Overflow about a year ago: http://stackoverflow.com/questions/9693934/cant-draw-sprites-in-pyglet. The workaround in reply # 3 here (http://code.google.com/p/pyglet/issues/detail?id=544#c3) worked for me. Just change "v2i" to "v2f" in two lines of sprite.py. Hopefully I haven't broken my game for other people!
On Tuesday, April 1, 2014 5:29:51 PM UTC-7, [email protected] wrote: > > I was working on an unfinished game which worked fine on my old computer, > with python 3.3 and pyglet 1.2alpha1. It used lots of sprites, and they > displayed fine. > > I've now moved the code over to a new computer with python 3.4 and the > latest version of pyglet, and the sprites are broken. They are displaying > as black, or as transparent, or not at all -- but they aren't throwing an > error. It turns out that image.blit() works properly. Has anyone else had > this problem? You can see a little test code here: > https://github.com/joeclark77net/roguestate/blob/master/program/sprite_test.py. > > The "robot.blit()" command works, but the "sprite.draw()" command does > nothing (or appears to do nothing) and throws no error. > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
