Couldn't measure a consistent frame rate

[oliviamborges]

WARNING     Couldn't measure a consistent frame rate!
  - Is your graphics card set to sync to vertical blank?
  - Are you running other processes on your computer?

I have this issue with version 2022.2.1 to 2022.2.5. I granted PsychoPy permission to access input monitoring and accessibility. This problem occurs even when a simple task with just a text component is executed. The only method I've discovered to prevent this issue on my Apple M1 computer (Ventura 13.1; Python 3.9.12) is to deactivate vertical sync, which is inconvenient.

Do you have any recommendations concerning potential solutions for this?
Thank you!

[peircej]

Depending what level of temporal precision you need, I don't really recommend using a Mac for genuine data collection because the timing is less good than windows and linux (see our paper, the Timing megastudy for details)

In your case working out how bad the frame-by-frame inconsistency is by running the demo called time-by-frames in the Coder view

[peircej]

I'm not convinced this is a bug at PsychoPy end, versus just a performance issue on this machine. So I'm closing, but re-open if there's any further evidence of a bug

[glupyan]

This seems to be a MacOS ventura issue with OpenGL https://discussions.apple.com/thread/254744079

...am teaching using psychopy now and code that worked fine a year ago with win.flip() waiting for a frame before existing, now exits immediately, requiring manual core.waits() :(