Hi Becca,
Apologies for my very slow response to this. In the end we decided it wasn’t worth creating a version solely for touchscreen devices and instead asked participants to use a laptop/computer. Although I have no doubt the “hover” mode idea you suggested would have worked if we had more time to update the task with that!
As for my other issue, no it was to do only with clicks. What I realised was happening is that my experiment in general was using up way too much CPU and this meant that sometimes when the participant clicked on the objects psychopy didn’t record what button was clicked before it jumped ahead and ended the routine anyway. My guess is that because it didn’t know which button was clicked (forestright and forestleft were both still set to zero), so it just used the last iteration of the routine and took participants to wherever they went last time.
I managed to reduce the amount of CPU being used in my experiment by cutting down the useless variables that were being recorded and in general by streamlining code to make things a bit simpler. I also delayed the presentation of the buttons and click components so participant weren’t able to rush through the experiment and potentially causing the game to miss clicks. Additionally, I added the following code to each frame in the routines were participants made clicks:
time.sleep(0.001)
I thought this may help to delay the task for a second before executing the routine. All of this was an attempt to reduce the CPU usage which may cause unexpected delays as other processes (outside PsychoPy) finally jump in and wrest control of the CPU from you (see this forum for a discussion of this).
Finally, I also closed all other programmes on my computer when running the experiment so that all I had open was Zoom and the Psychopy experiment. All this together seemed to fix the issue as the bug never occurred again (apart from one time when I had about 20 other programmes open at once!).
Thank you for help.
Best,
Matthew