-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Psychopy backend suddenly stopped working / Unexpected Error / pyglet.gl.lib.GLException: b'invalid value' #812
Comments
This seems like an issue with OpenGL, which can be very system- and version-specific. It's not directly related to OpenSesame or PsychoPy, and it's probably not something that you can debug in a meaningful way, other than through trial and error. Possibly it's indeed triggered by a driver installation, but that's hard to say. I would probably first see if there are (video) updates available for the computer. If this doesn't solve the issue, then I would build a new anaconda environment with OpenSesame in the hope that in this environment the error doesn't resurface. |
Thanks for yor response. I don't understand how it can be an opengl issue, if it works when calling manually via the "Opensesame python module (no gui"). I also reinstalled via the installer - isn't this equivalent to reinstalling via anaconda? I'm not doubting or so - I'm just collecting debugging ideas until I (or @tmalsburg) can be back in the lab |
I suspect that when you use the OpenSesame Python module, you're doing this in a different Python environment. Is that correct? If not, then that would indeed be strange. By saying that it's an OpenGL issue I mainly mean that it in general terms originates from OpenGL—I can see that from the error message. But what the underlying cause is exactly is hard to tell.
OpenSesame is indeed built on an Anaconda environment. However, if you install your own Anaconda environment, you will end up with slightly different versions of all packages, possibly even a different version of Python. And since this issue is quite likely version-specific, this might do the trick. |
I am using the opensesame environment, there is no other python installed - so we are in strange territory... Any way to get opensesame to return even more debugging information? |
The offending GL call originates from psychopy here: I don't know enough about OpenGL to say what this does, or what the role As I said before though, these things can be super context-dependent in the sense that it crashes in one situation and runs fine in another seemingly identical situation. And that can make it practically impossible to debug. |
We got a weird problem since last week. As far as we are aware, only a new microphone was newly plugged in (windows 11 probably installs drivers). Could be related, could be unrelated, who knows. Since around that time, psychopy backend doesnt work anymore.
If I run the default experiment I get an "Unexpected Error" - which is not helpful.
activating "--debug" note results in an (to me) uninformative log (see [1] below)
I tried running on last release (4.0.13) instead of current release (4.0.24) with no difference
If I remove the canvas object it works. If I move to pygame it works too
If I use the
New OpenSesame Python module (no GUI)
code from the release notes, it works (I did have to download aFreeType.dll
first though) => not a psychopy issue!If I use an inline script, and I try to draw something, I get an openGL error
pyglet.gl.lib.GLException: b'invalid value'
(full log see [2]). I used the simple inline script:I really dont know how to debug this any further. I checked for graphics drivers and removed the microphone for now. I installed newest windows updates and checked that no driver/update was installed via windows update in that time period.
Anything I can do besides completly reinstalling the windows computer?
Given that we have a university course running their experiments right now, it would be great to get some input how I can debug this further. I'm willing to spend the time, but I dont really know anylonger where to look for this issue / what to try.
Best, Bene
[1] The
debug.log
[2] the openGL pyglet error
small edit - the full startup log from the console
The text was updated successfully, but these errors were encountered: