Main > Software Forum
[Discontinued][17-09-22] RatRefresh - refresh rate switcher, stops LCD tearing
Rataplan727:
I noticed during testing that every time you remove your video driver or monitors from device manager, I think the latter, it gets redetected with a number +1. Not sure why that is, but that's what I see.
Anyway, I think I found the issue, and it's related to using CRU.
[Boring explanation] When you use CRU, it obviously writes a custom EDID value. However, it writes the Feature Blocks, which is a part of the EDID string that contains the min / max refreshrates as supplied by the monitor itself, in a different way, maybe even incorrect according to EDID specs. What RatRefresh did was to use the existing custom EDID value as a base to calculate things. And as RatRefresh checks the minimum and maximum refreshrates your monitor supports, which read out completely wrong, it wouldn't work properly. So I changed RatRefresh to use the monitors own supplied EDID value to customize, unless you use the switch -usecustomedid in which case it works as before.
What's even weirder though is that I've seen several times that CRU changes the monitors own EDID value, and changes min/max there too:
And that's why I made the -remove option to delete both the EDID_OVERRIDE key, but also the monitors original EDID value. After that it resets the display, and the EDID value will be re-generated by what the monitor supplies
[/Boring explanation]
I've upped a new (debug) version here: https://drive.google.com/file/d/1JZ_-TFvZktMEZGlCvAAuLv28zT_h92nD/view?usp=sharing
run RatRefresh -remove
run RatRefresh -setup
and now just run for example RatRefresh -refresh 58.850
Let me know! Unfortunately none of the admins has responded to my question to unlock my Rataplan626 account, so I can't update the opening post :(
TitanGorilla:
Unfortunately, after following the steps the refresh rate doesn't seem to change. I followed your steps but set the refresh rate to 57.451. On the UFO Test, the refresh rate is still close to 60 Hz.
Also, after it refreshes, there is still noticeable tearing when scrolling on web pages. It's subtle, so I don't know if anyone noticed it or if they might have the same issue. Can you test to see if you get screen tearing in your browser after resetting your refresh rate? If not, it might be an issue with my video card driver. I get the same issue when disabling/enabling the video card manually from the device manager.
I'm not sure if the CRU tool caused some type of conflict with the video card driver or if it would have had the same issue without CRU installed. I reset CRU before re-installing RatRefresh and it still gives tearing. I may have to re-install my video card drivers to see if the issue persists. Restarting my machine fixes the tearing completely, it still persists until I restart, even if I reset the refresh rate in Windows. After restarting my machine setting the refresh rate from Windows without enabling or disabling the video card or using RatRefresh doesn't cause the screen tearing.
Rataplan727:
*sigh* I really hoped this would've fixed it. The thing you have in common with TrevorP is that both of you have NVidia GPU's. In a way I have the feeling that has a relation to the issue. But on the other hand, trevorp states and showed that RatRefresh 0.11 works fine for him. The actual registry key written by 0.11 is identical (or should be) to the one from later versions. The calculation of the resulting registry key has not changed since 0.11, after an issue found by user xxDaViDxx. All changes since are about detecting the registry key it has to write to, and adding more parameters, but nothing about the actual registry value.
So, if have some spare time and want to help out, if you know your way in Windows, can you:
- run RatRefresh -remove once again
- export me your HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY registry
- delete edid.txt and Run RatRefresh -setup once again just to be sure
- run ratrefresh -refresh 59.150 or something
- export me your HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY registry again
Did 0.11 work for you? Does it work when you set a custom resolution through CRU?
Thanks for helping out.
trevorp:
I had negative results as well. Just didn't get a chance to do the full registry export run this morning. Will do at lunch, just to document progress, and I'll also follow the above instructions as well.
I was going to ask if the nvidia GPU might be the issue as I recall you were testing with NUC.
I've got a few generations old NUC here I also want to test with, just to see if the results are different.
Rataplan727:
yeah but then again I just can't think of ANY reason why 0.11 WOULD work then...
[edit]
ah cr@p... I just found another bug, triggered on my work pc which does not occur on my home pc, laptop and cab. Working on that. No need for additional registry export for now. Stay tuned :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version