fullscreen error (only when screen=1)

[Alex Holcombe]

I have a very simple error with recent versions of PsychoPy. The following program is enough to elicit the error:

from psychopy import core, visual, event

#create a window to draw in

myWin = visual.Window(allowGUI=False,fullscr=1,screen=1)

The error is specific to fullscr and screen=1. That is, it only applies when one has a second screen connected and attempts to start it up in fullscreen mode.

Psychopy outputs the following in response. At the end you'll see the "invalid fullscreen drawable" error. I've encountered this both on a recent OSX10.9 MacBook Pro and an older Mac Pro. Searching this forum, I find a report of this error, but only way back in 2012- https://groups.google.com/d/msg/psychopy-users/aQNtKXsae8c/haMCPur5qSMJ. Did it disappear of its own accord, only to crop up again now?

/Applications/PsychoPy2_1.80.app/Contents/Resources
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python27.zip
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/plat-darwin
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/plat-mac
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/plat-mac/lib-scriptpackages
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/lib-tk
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/lib-old
/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/lib-dynload
error importing TextureAtlas: No module named textureatlas
0.4629 WARNING Creating new monitor...
0.4630 WARNING Creating new monitor...
0.4640 WARNING User requested fullscreen with size [800 600], but screen is actually [1024, 768]. Using actual size
Traceback (most recent call last):
  File "/Users/alexh/Documents/Honours/ChrisFajou/gaborChris.py", line 5, in <module>
    myWin = visual.Window(allowGUI=False,fullscr=1,screen=1)
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/psychopy/visual/window.py", line 314, in __init__
    self._setupGL()
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/psychopy/visual/window.py", line 1329, in _setupGL
    self._setupPyglet()
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/psychopy/visual/window.py", line 1199, in _setupPyglet
    style=style)
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/pyglet/window/__init__.py", line 686, in __init__
    self._create()
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/pyglet/window/carbon/__init__.py", line 549, in _create
    _aglcheck()
  File "/Applications/PsychoPy2_1.80.app/Contents/Resources/lib/python2.7/pyglet/window/carbon/__init__.py", line 1365, in _aglcheck
    raise CarbonException(cast(agl.aglErrorString(err), c_char_p).value)
pyglet.window.carbon.CarbonException: invalid fullscreen drawable

[Erik Kastman]

Alex,

We just had this error as well: https://groups.google.com/d/msg/psychopy-users/S8R8W5A8hzE/iJT7ue1N45EJ

It was specific to the monitor, so that one external monitor worked fine but another gave the invalid fullscreen drawable error. 

We updated from 10.7 to 10.9 and it’s now working, but I have absolutely no idea what the root cause is. That’s not an ideal solution, especially if it happens in the middle of a study, but it does give an idea of the scope of the cause.

Erik

--
You received this message because you are subscribed to the Google Groups "psychopy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to psychopy-user...@googlegroups.com.
To post to this group, send email to psychop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/psychopy-users/8bf87f09-3080-4d39-b902-d36f70a1794b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alex Holcombe]

Thanks for letting me know about your other report (https://groups.google.com/d/msg/psychopy-users/S8R8W5A8hzE/iJT7ue1N45EJ), Erik. I've upgraded my Mac Pro to 10.9.4 and still get the error with two different CRT screens, whether the inbuilt graphics card is the second screen or an Nvidia Quadra graphics card is controlling the second screen.  Fortunately using a second screen is not essential for me, can just run it in fullscreen mode.  Just posting this message so the community knows the problem is still around.

Alex