This article applies to:
E-Prime Go 1.0
An E-Object may encounter the following timing issues:
- The OnsetTime reported may be inaccurate and therefore can impact the next target OnsetTime. As a result, when running with Event timing, display objects may remain on screen longer than the specified Duration, although the default setting for RefreshAlignment will help mitigate this issue.
- The "task" component of a TaskEvent defined for the OnsetTime "event" may be delayed.
- The RT and RTTime may be inaccurate because the Object's Input Mask is not armed during the delay period before the OnsetTime is set.
Windows 11 laptops may exhibit timing issues where the OnsetTime is delayed and the OnsetTime value is inaccurately assigned and logged. Typically, this issue only occurs while on battery power. This delay period typically lasts a few milliseconds, but can be greater than a refresh, and does not occur on every trial.
PST recommends running the battery test experiment attached to this article to test if:
- the issues exist on your machine
- and if so, whether the workarounds described below fix the issue
The test experiment should run in less than two minutes. A "Pass" or "Fail" message is displayed after the last trial. The data file (.edat3) can also be examined to confirm that the entries in the TestResult column are set to "Pass".
NOTE: We have observed this issue when running experiments on battery power with a specific Power Mode on Windows 11. We have not observed this issue on Windows 10. However, we encourage running on line power when possible (i.e., machine plugged in).
The following workarounds are possible:
Plug the machine into line power and do not run on battery power.
Change the computer's Power Mode setting. We observed these issues when using "Balanced" or "Recommended" settings. To check this setting and change if needed, open the System Settings (i.e., press Windows key + I), select Power & battery, and change the setting from "Balanced" or "Recommended" to a "Performance" mode (the specific Performance setting name may vary with specific Windows versions).
Disable Fullscreen Optimizations to possibly resolve the issue while running in "Balanced" Power mode. ERROR: Multiple monitor experiments run on Windows 10 or Windows 11 freeze or receive a display is too busy error (Error 11102)  outlines how to disable Fullscreen Optimizations.
NOTE: The Disabling Fullscreen Optimizations setting is automatically applied during E-Prime Go sessions.
If the above workarounds do not resolve the issue, Chronos can be used to obtain the correct OnsetTime. Contact PST support for more information.