ERROR: HASP Driver Version 8.31 or later causes E-Prime 2.0 installation error 2753 [39149]
INFO: Some Microsoft IMEs cause issues with E-Prime 2.0 on Windows 10 2004 and beyond [37376]
RELEASE INFO: Known issues in E-Prime 2.0 [19406]
BUG FIX: Corrections for Scripting Typos in Getting Started Guide [18528]
ERROR: Use of Sound.LoadAffinity to diagnose sound loading and playback issues [18654]
BUG FIX: Find/Replace All Script Windows option is not working when using the PackageFile editor on non-certified package files [19563]
BUG FIX: Backslash character is not supported in E-Basic [19561]
BUG FIX: Changing DisplayName property via attributes or E-Basic causes backcolor to reflect not as expected [18803]
BUG FIX: Feedback displays wrong entries when properties are set to attribute reference [19262]
BUG FIX: Syntax error when generating experiments with more than one DisplayDevice [18327]

See more

BUG FIX: Display.RefreshRate logged as 0.000 [18366]

Updated March 24, 2021 15:40

This article applies to:
E-Prime 2.0

This bug has been corrected in E-Prime 2.0 (2.0.1.120).

Symptoms
Display.RefreshRate appears in the log file as 0.000. This is due to an internal error with the logging property of this feature.

Solution
Upgrade to E-Prime 2.0.1.120 or later.

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk