-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no Windows binary release for Python 2.6 #3
Comments
@astraw |
No, I was not working on this. Won't Python 2.7 work for you? (Why not?) |
same issue on python 2.7 with PyOpenGL 3.1.0 |
Do you mean the pyopengl multitexturing bug? Otherwise, what exactly is the issue? |
Sorry my last comment wasn't precise, my issue is when I run any demo from the source code demo list I got this exception: File "C:\Anaconda2\lib\site-packages\OpenGL\arrays\numpymodule.py", line 28, in I'm running visionEgg on windows, My python packages are : PS: I had perfectly run visionegg on ubuntu14.04 with the same packages versions |
After installing the latest version with pip, I encountered an exception with the multitexturing warning: |
Here's the traceback of running Pyff with a visionEgg feedback : Traceback (most recent call last): |
I've been trying to figure out how to fix it, what I'de noticed is that the opengl_info.py script shows that the GL_VERSION is newer than the one used by GD generic (in my case it's 3.1.0 - build 9.17.10.4101) and the renderer is not the default microsoft driver, however one running any demo script visionegg uses the GDI Generic driver with OpenGL 1.1.0, do you have any idea how this can be fixed? |
There is no VE binary available for download for Python 2.6 on Windows.
This is because PyOpenGL 3.0.0 has bug on Windows. Specifically, multitexturing is broken, as reported (SourceForge bug 2817196). This is evident when trying to use the Gabor stimuli, which will fail and an exception will be raised. The workaround is to continue using PyOpenGL 2.x, which unfortunately not available for Python 2.6.
The text was updated successfully, but these errors were encountered: