This article applies to:
E-Prime 3.0 experiments do not respond to key presses, mouse clicks, etc. after the onset of the first visual display object.
NOTE: This issue has only been observed on a small subset of Windows 11 machines. While PST has not observed this in-house, it is possible this issue may occur on a small subset of Windows 10 machines as well.
Whenever the first visual screen appears at runtime, responses to the input mask do not get recognized right away. PST has observed this behavior from the onset of the E-Object until about 5 seconds. After 5 seconds, all responses to that E-Object (and subsequent E-Objects) are normal. This only affects the first visual E-Object within the first 5 seconds after onset time.
Disable the Fullscreen Optimizations setting for E-Prime. This setting needs to be edited per user account.
Follow these steps to disable this setting:
Navigate to C:\Program Files (x86)\PST\E-Prime 3.0\Program.
Find the E-Studio application.
Right-click on the E-Studio application and select Properties.
Navigate to the Compatibility tab in the E-Studio Properties.
Check "Disable full screen optimizations."
Click OK to confirm the changes.
NOTE: If using E-Run, perform steps 2-6 on the E-Run application.
NOTE: While PST's timing was accurate in-house, timing should be verified by external hardware to ensure millisecond accuracy. For example, users can verify timing by using Chronos and a photosensor to ensure that Stimulus onset and monitor refresh rates are accurate.
Create a visual E-Object before the one that requires input. The newly created E-Object should have a 5000-millisecond duration and no Input Mask. This way, the Input Mask during the next E-Object runs correctly.
Configure the experiment to use the DX7 API. To do so, open the Experiment Object Property Pages > Startup Info tab > and click Add.
Enter the information shown in the image below.
NOTE: Make sure to uncheck "Prompt the user for this startup info parameter".
Running on Windows 8 and beyond requires Display Flipping to be enabled for timing purposes. For more information, see AV: DisplayDevice.FlippingEnabled .
WARNING: Extensive testing has not been performed at this time using the DX7 API. DX7 with AMD has shown slower processing times (meaning more OnsetDelay may occur). Timing should be verified by external hardware to ensure millisecond accuracy. For example, users can verify timing by using Chronos and a photosensor to ensure that Stimulus onset and monitor refresh rates are accurate. Please view TIMING: Verifying your Clock and Timing in E-Prime  for more information on verifying your timing.