Windows 10 Creators Update interrupts E-Prime’s ability to detect refresh rate: setting of the refresh rate goes haywire also
since the Creators Update the refresh rate is not being dete=cted by E-Prime. PST posted a workaround for this problem. When using this workaround the actual refresh rate used is again logged correctly in the datafile. The problem that has not been adressed is the problem that E-Prime now cannot *set* the refreshrate correctly anymore. The refreshrate that is requested in the experiment is not enforced.
This is a critical problem that should be adressed quickly.
Please sign in to leave a comment.