Some hardware- and OS-specific bugs

[pevzi]

Hello everyone. I finished a simple game using Pyglet and I decided to
test it on some other machines. The results were quite surprising: the
game ran differently on all 4 test machines.
1. The game runs perfectly both on my Linux laptop and desktop.
Everything works just as I expected.
2. On the same desktop but under Windows 7 there is a strange bug.
When I use pyglet.graphics.draw() to draw primitives directly every
image which is drawn by blit() method gets tinted by the color used
when drawing a primitive. Sprites don't get affected.
For example, what I expect:
http://i.imgur.com/Is5ks.png
...and what I see:
http://i.imgur.com/Zuwky.png
3. Another Windows 7 desktop shows another bug: not a single sprite is
drawn on the screen. The images which are drawn with blit() method
just work well but everything that relies on batch drawing is not
being drawn at all (incl. sprites and text labels). It seems like this
issue is already reported but the reason isn't found yet. There are
several related bugs in the tracker, here is one of them:
http://code.google.com/p/pyglet/issues/detail?id=544
4. The 3rd desktop running Windows XP reveals one more problem. Images
drawn with blit() sometimes flicker as if they are not blitted at some
frames. I'm not sure but it seems to happen when performing operations
such as adding/moving sprites between batches. To be honest I didn't
quite understand the true reason.
I don't know if these are purely Pyglet bugs or hardware/driver flaws
so it would be nice if someone eventually found the sources of these
problems. Does anybody have any ideas about what causes these issues?
Maybe someone faced these too?
Also you can grab the mentioned game here: https://bitbucket.org/pevzi/pullout
Here is how it must look like: http://i.imgur.com/cpa5l.png

[Andreas Schiefer]

I tried your game on two different machines, one laptop with an integrated Intel GPU and one desktop with an AMD HD 4xxx series GPU. Both are running Windows 7 (one 32 bit, the other 64 bit) and I've used the latest pyglet revision from the repository.

Your game looks exactly like it should on both machines.

You didn't mention which version of pyglet you are using, maybe you should try the latest from the repository.

Otherwise I think the errors are maybe due to driver bugs, have all your machines the latest drivers installed? And make sure you are using a 32 bit Python version on Windows - even if it's a 64 bit Windows.

(FYI the game also works fine with Python 3, needing just one minor correction after 2to3 conversion)

[Михаил Сидоров]

Thanks for your reply.

Sorry, I forgot to say that I'd already made some workarounds in my game to avoid these issues. I got rid of all blits to bypass the bugs #2 and #4 and forced Sprite to have float coordinates for #3 (see spritemod.py). So if you still want to have a look at these problems you can test the revision 87741dacb7bf of pullout where they are not «fixed» yet.

I use pyglet 1.1.4 but I've tried the one from repository and unfortunately the problems are still there. The drivers and Python version seem to be ok too.

2012/2/18 Andreas Schiefer <andreas....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/LufbUe62LT0J.
To post to this group, send email to pyglet...@googlegroups.com.
To unsubscribe from this group, send email to pyglet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.

[Andreas Schiefer]

Just as a quick update, I've now also tested the older revision of your game on the same machines, but still without any issues. 

But good to know that you've found some workarounds already.