PsychoPy n170 fails on Windows 10 Pro
See original GitHub issue- Windows 10 Pro
- Python Version: 3.7.11
- Brain Interface Used: Crown
When running n170.present (form visual_n170), PsychoPy freezes and python crashes.
The problem was fixed by removing show_instructions(duration)
. We think that the error comes from the fact that mywin = visual.Window([1600, 900], monitor="testMonitor", units="deg", fullscr=True)
is repeated twice and therefore PsychoPy creates two screens which makes it crash.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
Troubleshooting — PsychoPy v2022.2.4
Below are some of the more common problems and their workarounds, as well as advice on how to get ... Windows users (starting...
Read more >Experiment does not work on Windows 10 PC, but does on ...
I got a error message with the same PsychoPy3 program file about getGammaRamp ending “AttrtibuteError : 'NoneType' object has no attribute ' ...
Read more >Experiment does not run on Pavlovia - PsychoPy Discourse
The errors occurs: Failed to load resource: the server responded with a status ... I am using PsychoPy v2022.1.2 on Windows 10 pro,...
Read more >Error only with Random Dot Kinematogram ( RDK ) stimulus
If this template helps then use it. If not then just delete and start from scratch. OS: Windows 10 Pro 64-bit (10.0, Build...
Read more >PsychoPy (or Windows ?) bug - Other
Also, I found an emergency solution to avoid this problem. I think this error often occurs in multi-monitor environment. If you use multi ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @oreHGA I had to revert that PR, so we’re still on an old version of psychopy.
@gbernal Thanks for that, I updated to latest Psychopy in #167 so at least that shouldn’t be an issue anymore.