By dbecker - 2/18/2015
Hi,
i am currently working on a script in which i want to present trials that start with a fixation, then show stimulus 1, which is then erased, and then show stimulus 2, which participants respond to. The script looks like this:
<trial boxInR>
/pretrialpause = 1000
/validresponse = ("z", "m", "x", "n")
/correctresponse = ("m")
/stimulustimes = [0 = fixation; 500 = boxConGroen; 633 = erase; 866 =boxInRood]
</trial>
(boxConGroen & boxInRood= refer to a png stimulus which is defined earlier).
Here the problem: if i run this trial, inquisit displays the fixation and then the last stimulus (boxInRood) at 500 ms, then erases it, and then shows it again at 866 ms. So I am wondering what happened to the middle stimulus (boxConGroen), which is not displayed?? If i only run /stimulustimes = [0 = fixation; 500 = boxConGroen] I do see it - so the problem is not in the previous coding.
Any ideas why the last stimulus substitutes the middle stimulus (but not the erase or fixation)?
Thanks!
|
By Dave - 2/18/2015
We have seen (very) few instances of something similar. In all those cases a buggy graphics card driver was responsible and updating the driver to the latest version available from the vendor fixed the issue.
|
By dbecker - 2/18/2015
Thanks, i will try running the same script on a different (/better) computer.
But your response suggests that this is odd and actually should not happen....I will keep you updated!
Best,
Daniela
|
By Dave - 2/18/2015
> But your response suggests that this is odd and actually should not happen...
Indeed -- provided that there is no mistake in the script -- it should not happen. Hence my suspicion that the graphics card driver is responsible (as in previous cases). Basically, the card is not doing what it is instructed to do by Inquisit due to a defect in the card's driver. Update the driver on your machine and the issue should go away. The script should also work fine on other machines with different graphics cards / drivers without that particular defect.
|
|