On Jan 10, 12:52 am, "Alex Holkner" <[EMAIL PROTECTED]> wrote:
> On Jan 10, 2008 8:22 AM, mdboom <[EMAIL PROTECTED]> wrote:
> > glxgears seems to run fine. I have a nVidia Quadro FX 550 EPCI card.
> > I have attached the output of glxinfo.
>
> I don't have many ideas.. it looks very much like an issue fixed in
> nvidia driver 1.0-4363 (see nvidia driver release notes), but it looks
> like your driver is far newer. Check that you have a complete install
> of the nvidia drivers; that another driver (e.g., mesa) isn't
> interfering, and that the machine has been restarted since installing
> the new driver.
I don't know how to check that mesa isn't interfering, but I'm pretty
sure the other two points are okay.
> A good start in tracking down the problem would be to check that the
> arguments passed to glXCreateWindow seem reasonable (i.e., not null).
> These are in pyglet/window/xlib/__init__.py.
These arguments are not null, but I didn't did any deeper into their
values. I'm happy to do so if you think there's anything interesting.
> It might also be worth trying the GLX 1.1 path, which doesn't use
> glXCreateWindow -- patch the have_version() method in
> pyglet/gl/glx_info.py to always return False.
This seemed to work for me. FWIW -- the versions here are 1.4 for
client and server.
I ran tests/test.py, and everything seems to pass now. However, by
disabling glx, does that mean I am not getting hardware acceleration?
The opengl.py torus example, for instance, seems much slower than I
would normally expect from this machine...
Cheers,
Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
