[solved] "Fullscreen not found" with OpenSesame 3.0.X on windows 10
Hi all,
I'm quite new to OS, so I apologize if there is something obvious I am missing.
I wrote my experiment in OS version 2.9.7 and the experiment ran with no problems. The experiment runs OK on OS 3.0.1) (after modifying some of the mouse visible functions) that is installed on a pc with windows 7. But for some reason on my personal pc which runs windows 10, the experiment will only run on OS 2.9.7. When I try running the experiment with OS 3.0.1 I get the following error:
Item-stack: ' '
exception message: fullscreen not found
Any clue what is going wrong?
I would appreciate any insights
Thank you!!
Comments
Hi,
In the Window with the error message, you should see a detailed error message under Traceback. Could you post that as well? Does this error occur with all backends, and in both fullscreen and window mode?
Cheers,
Sebastiaan
Check out SigmundAI.eu for our OpenSesame AI assistant!
A few people have reported this same problem now, so let's try to get some more information.
Question:
Check out SigmundAI.eu for our OpenSesame AI assistant!
Hi! I've tried with multiprocess runner and it works!
What that this change is about?
thank you so much!
Hi Sebastian,
Thank you for your comment.
I apologize for my late response.
Great this change works!
Changing "external" to "multiprocess" or "inprocess" makes my experiment work without the error message mentioned in the previous message. The way my laptop displays the experiment resolution changes between "multiprocess" and "inprocess", but I don't mind this (I will not run my experiment on my). What do these preferences changes do? What is the difference between "external", "multiprocess, and "inprocess"?
Thank you very much!!!
Hi guys,
Ok, that solves it: The external runner is broken (#371). There's generally no reason to use the external runner (which uses opensesamerun); it's mostly a remnant from the days before @dschreij developed the multiprocess runner (which uses multiprocessing).
So, for now, a workaround would be to use the multiprocess runner, which you can select under Menu → Tools → Preferences.
Cheers !
Sebastiaan
Check out SigmundAI.eu for our OpenSesame AI assistant!
Hi Sebastiaan
Thank you very very much both for this magnificent program and for your quick and thorough support.
Asher
One more thing, I forgot...
Can you explain what the difference is between multiprocess and inprocess? my experiments take much more time to load (there is quite a lot of text screens to prepare) in the multiprocess mode. Is there any reason to not to use inprocess in this case.
Thank you!!!
In a nutshell, the multiprocess runner starts the experiment in a separate process. The main advantage is that, if a hard crash occurs, the OpenSesame doesn't go down. Also, the live-updating function of the variable inspector only works for the multiprocess runner.
But you can use the inprocess runner as well--it really doesn't matter for your experiment.
See:
Check out SigmundAI.eu for our OpenSesame AI assistant!
Thank you!!!