[open] Error: Source and destination surfaces need the same format. ????
Hello everyone,
We tried to run our experiment on another computer than we were used to. We get this error: Source and destination surfaces need the same format.
We already tried to adjust the pixellevels, but this didn't work. When we run the experiment, it shows the instructions but when the actual task should begin, it stops and shows the error.
The computer is from the brand "Eizo" with a screen from " FlexScan S1932"
Please help!!!
Comments
Hi,
Could you post the full error message, which you can find in the debug window? Please also include the relevant script, if the error results from an
inline_script
, and information about the operating system and back-end that you're using.Cheers!
Sebastiaan
There's much bigger issues in the world, I know. But I first have to take care of the world I know.
cogsci.nl/smathot
This is the message displayed in the debug window:
We are using an inline script but I don't know if thats the problem, however, this is the inline script were using:
Ok, that's a weird error indeed. As a first step, I would see if you still get this error with the most recent version of OpenSesame. Right now you're using 0.26, which is relatively ancient (almost two years old):
I think there's a good chance that updating will resolve the issue, even though, to be honest, I have no clue what causes it. If an update doesn't resolve things, we'll take it from there.
Cheers!
There's much bigger issues in the world, I know. But I first have to take care of the world I know.
cogsci.nl/smathot
As a potential temporary workaround: could you check if the 'psycho' back-end provides the same error?
Hi,
I am having the same error with the latest version of OpenSesame. I am able to run the experiment full screen using expyriment and psychopy backend but not the legacy backend.
Here is my experiment https://drive.google.com/file/d/1aTYxVVqzueYsp-ih2bEcFO9VHK9LfWxH/view?usp=sharing
Thanks!
Han
Hi Han,
Maybe a new issue for that. The discussion is almost 5 years old, so it is highly unlikely that the issue is caused by the same thing.
Thanks,
Eduard