| Reference | Downloads | Github

Pylink/EyelinkCoreGraphicsPsychoPy is turning my stimuli transparent. Randomly

If this template helps then use it. If not then just delete and start from scratch.

OS (e.g. Win10): Win 10
PsychoPy version (e.g. 1.84.x): v. 2021.1.4
Standard Standalone? (y/n) If not then what?: yes
What are you trying to achieve?:
I am running a study that involves eye-tracking in psychopy. It looks like whenever run through the calibration/validation routine, every text component after it (and some before) turns transparent. I can see from the data output that it is running through the rest of the task successfully and recording key presses, but it is just not displaying on the screen.

What did you try to make it work?:
I have tried changing colors of the text components, deleting text components and putting them back in, changing opacity of text components, and changing the foreground color in the eyetracker set up code chunk. Is anyone else running into this issue?

@sol and I have recently been adding Builder eyetracking functionality for the next release and did find a few bugs where things in the experiment were altered by events happening during iohub procedures - the main thing is that keyboard and mouse components kept listening during iohub calibration. Do you have any keyboard or mouse components which affect the text components?

Nothing that should effect drawing of experiment graphics after the calibration ; the calibration window should not be able to randomly impact the drawing in the psychopy experiment window.

It looks like whenever run through the calibration/validation routine, every text component after it (and some before) turns transparent.

Does the issue occur if you do you not run eye tracker calibration / comment out the call to .runSetupProcedure()? It seems even more odd that it could be effecting graphics before it is even called. This makes me think something else is going on.

Would you mind making a simple example that shows the problem so I can try to reproduce?

Thank you.

1 Like

Hi @TParsons and @sol thanks for your responses. I didn’t have any keyboard or mouse components that were listening in, and I agree that it was strange that it was affecting it before the eyetracker. What I realized was happening is that it appeared the eyetracker was changing the spatial units to pixels (rather than whatever the default is)- therefore my text size 0.03 wasn’t showing up because it was wayyyy too tiny. Once I set text to size like 40+, it was resolved!

1 Like

Hi @TParsons , thanks for all your help. I’m wondering if you could tell me a bit more about this? I am wondering if I’m running into this now- I have a keyboard press that should terminate the routine when ‘z’ is pressed, and was doing so successfully before the eye tracker addition, but it is no longer doing that now. Is this sort of thing what you mean?