"Error 9, Subscript out of range" - some computers but not others (case 10691)
"Error 9, Subscript out of range" - some computers but not others (case 10691)
I'm receiving the following error when running on my lab computers but not the computer that I programmed the studies on:
Subject 6, 10/4/2013, 3:11:28 PM, v2012.4.160, Initial Display: 1280x1024, 32-bit colour, 60hz or 16.67ms/screen
Subject 6, 10/4/2013, 3:11:28 PM, v2012.4.160, Session Display: 1024x768, 16-bit colour, 60hz or 16.67ms/screen
Elapsed Time: 1040ms, block -1, trial 37, stim 1, Error 9, Subscript out of range, on line 200, during FlipScreen of Form DDFullScreen
Subject 6, 10/4/2013, 3:14:41 PM, Finished. 1 Errors/Warnings.
The error message usually does not pop up until after the study is complete (but occasionally will interrupt the experimental session). On a positive note, all data is recorded and intact. The primary concern is that the error popup is disrupting the experimental session.
My current OS is Windows 7 for the 'programming' computer and Windows XP for the lab stations.
I attempted recreating the DirectRT .csv script from scratch on the lab computers but this did not resolve the problem. I've searched here extensively, but could not find a similar issue.
Thanks for any advice you might have!
Try setting the screen size in your study's Styles file to match the resolution setting of you monitor. You can find the screen setting drop down menu under the Options button of the Styles file.
Just checking in to see if you ever found a resolution to why this error message popped up. Let me know if there is anything I can do!
Just checking in to see if you ever found a resolution to why this error message popped up. Let me know if there is anything I can do!
Jason, so sorry I didn't catch your earlier post! I'm still at a bit of a loss as to the origin of the error. Unfortunately, the screen resolution fix didn't end up resolving the error screen. The error has only impacted that single study so I *think that it might be specific to my coding. I'll let you know if it pops back up or if I determine the source!
Please do let me know what you find or anything that I can help with!