On Wed, Nov 28, 2012 at 11:51 PM, Blaine Booher <[email protected]> wrote:
> No problem. Here you go! It's an intel i7 with integrated Ivy Bridge > HD4000 (I think) CPU/GPU > > [blaine@lemur:~/src/pyglet/tools Wed Nov 28] > 18$ python gl_info.py > Pyglet: 1.2alpha1 > ... > GL attributes: > double_buffer=1 stereo=0 buffer_size=24 aux_buffers=0 sample_buffers=0 > samples=0 red_size=8 green_size=8 blue_size=8 alpha_size=0 > depth_size=24 stencil_size=8 accum_red_size=0 accum_green_size=0 > accum_blue_size=0 accum_alpha_size=0 major_version=None > minor_version=None forward_compatible=None debug=None > GL version: 3.0 Mesa 8.0.2 > GL vendor: Tungsten Graphics, Inc > GL renderer: Mesa DRI Intel(R) Ivybridge Mobile > Good. Looks like a bug in Mesa drivers. There are some reports about this combination. Like this one: http://jogamp.org/deployment/jogamp-next/javadoc/jogl/javadoc/com/jogamp/opengl/GLRendererQuirks.html It may help to see if glxinfo returns different info: > glxinfo | grep OpenGL It will help to pinpoint of problem before reporting to http://www.mesa3d.org/index.html with a smallest crasheable piece of code. I'd run test once more to see the exact function that crashed and try to make a standalone example out of it. > python -m tests.graphics.RETAINED -v -- anatoly t. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
