When everything is working fine, it usually is. Did you change your mind or have other, more annoying, issues popup after disabling Monitor Auto Detection above To re-enable the Windows 10 Automatic Monitor Detection feature, or Transient Multimon Manager (TMM), one would simply need to go back to the TMM folder mentioned above and set the value of UseIViewHelper to 1 with a. If you have any other ideas let me know.Īlso the frame skipping test is not always consistent between Firefox and Chrome, at least not when the problems happen. In that case the black screen happens for a second and then the screen ends up being very choppy and that frame skipping test looks like this: Normally (without sleep/hibernate), when I change the refresh rate I'd get 1 or 2 seconds black screen and then get the confirmation window with a 15sec count down.īut if I do this after sleep/hibernate there is usually no black screen, the Hz "change" is instantaneous.Įxcept sometimes for the very first time when I switch from the 75Hz setting (=a properly working 60Hz) to the 60Hz setting. Then it shows the refresh rate at 60Hz and the frame skipping test also shows it's running at 60Hz. It's actually only showing it at 75Hz until I close and re-open that advanced monitor setting window. (02-08-2014 02:41 AM)ToastyX Wrote: Are you saying Windows shows it's set to 75 Hz but it's actually running at 60 Hz?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |