Sudden extreme slowing (freezing) in Windows64 (standalone install)

[Peter_Soltesz]

Amazingly I found a workaround for this. It is embarassingly simple: setting useFBO=False
LOL

Now I don’t really know what are the repercussions for this setting, it seems to be missing from the documentation of class psychopy.visual.Window.

I connect here another threads that recognised this:

useFBO option in Builder

Hi All, I’ve found when trying to run a Builder-generated study on a relatively old PC that the experiment just basically grinds to a halt if the window is instantiated with useFBO = True. Unfortunately, we can’t control the useFBO setting within Builder. The only solution seems to be to compile the script and manually edit the generated code. In this thread back in 2015: https://groups.google.com/forum/m/#!msg/psychopy-users/vCsQHBGyC50/yr58ZRSJM00J @jon suggested that useFBO = False should …

Multiple windows with "useFBO=True"

Hi, We have a projector displaying a psychopy window using the ProjectorFramePacker (to get a 60hz output split into 3 subframes for 180hz). This requires leaving “useFBO=True” for that window. Since the projector will be projected into a microscope, I have a second window on the monitor that mirrors the projector window. Prior to using the framepacking, I followed the advice in this thread, and leaving useFBO off worked there. Now that I’m forced to use FBO for the projector window, creating …

Divide by zero in double_scalars; display lag of 8 seconds!

Here’s that line 73 of the code that throws the divide by zero error: # Setup the Window win = visual.Window( size=[1680, 1050], fullscr=True, screen=0, winType='glfw', allowGUI=False, allowStencil=False, monitor='testMonitor', color=[0,0,0], colorSpace='rgb', blendMode='avg', useFBO=True) # store frame rate of monitor if we can measure it expInfo['frameRate'] = win.getActualFrameRate() if expInfo['frameRate'] != None: frameDur = 1.0 / round(expInfo['frameRate']) # !!!ERROR…

Now it would be nice to know why this happens though…