Serious performance regression from recent update from 2.0.1 to 3.0

Bug #135736 reported by Alexander Jones on 2007-08-30
Affects Status Importance Assigned to Milestone
pyopengl (Ubuntu)

Bug Description

Frets on Fire is absolutely unplayable as of the update to 3.0 on Wednesday 29 August 2007.

I have tried this with both r300 and fglrx. I could get very good performance prior to this upgrade.

ProblemType: Bug
Architecture: i386
Date: Thu Aug 30 02:54:52 2007
DistroRelease: Ubuntu 7.10
Package: python-opengl 3.0.0~a6-4
PackageArchitecture: all
SourcePackage: pyopengl
Uname: Linux flash 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

Alexander Jones (alex-weej) wrote :
Alexander Jones (alex-weej) wrote :

Also to note that version 3.0 of python-opengl is alpha. I really think we should revert to stable 2.0.1 for Gutsy. (2.0.2 is latest stable I think, but it was never packaged according to the debian changelog.)

Alexander Jones (alex-weej) wrote :
Alexander Jones (alex-weej) wrote :
Alexander Jones (alex-weej) wrote :

The only PyOpenGL application I have is FretsOnFire (package "fretsonfire" in Gutsy archive). I get about 10fps on the *menus*, but funnily enough about 25 in the actual game.

While I'm prepared to believe that for some other graphics cards with some other drivers and some other applications, the 3.0 alpha brings some improvements, it certainly doesn't for me.

Please try FretsOnFire with both 3.0 and 2.0.1 and see if this affects your hardware.

sancheztavo (sancheztavo) wrote :

Definitely, but I only tested the same game, and python-opengl 3.0 decreases it's frames per second a lot.
But we should test another python opengl app before blaming this package and not fretsonfire.

It is a real shame that ubuntu is released with an 3.x alpha version of python-opengl. It does not only contain many bugs, it is also incompatible with previous versions. Programs that run fine with the stable 2.x releases of python-opengl, are not guaranteed to work. Please read the release notes:


A quote from these release notes:

This is still a rather early alpha. We're missing big
tracts of functionality, such as the AGL and WGL libraries
(we do have raw XGL support). There is lots of work still
to be done and we would love to see your patches to get your
 favourite bit of the package working. Bug reports, reports
 of success/failure and the like are also useful. We
haven't even begun to optimise the code, btw, so expect it
to be very slow.

I am currently preparing a release of a program that uses python-opengl, but a lot of the visualization has become completely trashed with python-opengl-3.0.0a6, due to incompatibilities with the previous version and bugs. This makes it impossible to release my software for ubuntu users. That's a real shame.

FYI: I have downloaded the source packages for python-opengl ( from and generated a debian package from theses sources. When I downgrade to this home-made package, my python-opengl based applications run fine again.

Alexander Jones (alex-weej) wrote : is available from the Feisty archives and is compatible, FWIW.

Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta or later?

Changed in pyopengl:
status: New → Incomplete
Alexander Jones (alex-weej) wrote :

Probably, but I don't have regular access to the machine in question anymore. Should know by Christmas.

At least the version is now 3.0.0~b3 (beta 3?) rather than the alpha before... Should be a bit more reliable.

Robert Ancell (robert-ancell) wrote :

Expecting upgrade to 3.0.0 final to fix this, see bug 351284

Changed in pyopengl (Ubuntu):
importance: Undecided → Low
status: Incomplete → Triaged
Sebastien Bacher (seb128) wrote :

is that still an issue with the stable version?

The graphics card has died now, so cannot test.

On Feb 10, 2010 10:35 AM, "Sebastien Bacher" <email address hidden> wrote:

is that still an issue with the stable version?

-- Serious performance regression from recent update from 2.0.1 to 3.0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers