Main > Software Forum
[Discontinued][17-09-22] RatRefresh - refresh rate switcher, stops LCD tearing
Rataplan626:
--- Quote from: Cisek on September 20, 2022, 04:57:12 am ---Rataplan :notworthy:
I was waiting years for this. Technicaly gsync/freesync solve the issue, however for classic 4:3 aspect ratio lcd, or 16:9 lacking gsync/freesync it is gamechanger!
Will it work on pc crt monitors as well?
Do you think it would be possible to implement it for the linux systems, like batocera?
--- End quote ---
Well, I use linux (ubuntu / debian based) at work, but never wrote any software for that myself. While .NET apps can nowadays made to run on Linux, this app basically writes a registry value to achieve the goal, which Linux doesn't have obviously. So no, don't expect a Linux version soon.
I guess it can work on CRT as well. For that though, maybe changing the resolution as well might be even more effective, or even requiered. The tool now changes the refreshrate for the resolution you are running at now. Maybe I should add actual resolution change too.
Justin:
Since I just moved from a CRT to an LCD (without G sycn/ Free sync) I am very interested in this.
I tried to set it up to plam Metal SLug 5 as a test, which reports a refresh rate of 59.1856....hz
I tried the following command, it seems to be setting the monitor up as I see no errors and it clearly is resetting things (black screen, then back on etc).
C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.185
or even
C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.186
However, testing Mslug5 I am seeing tearing just as usual (as if 60hz).
Am I doing something wrong?
This is the result I get:
--- Code: ---C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.186
Key SYSTEM\CurrentControlSet\Enum\DISPLAY\GSM5674\4&2cbcb734&0&UID16843008\Devic
e Parameters\EDID_OVERRIDE
WantedRefreshRate 59.186
CalculatedPixelClock 15204
HexCalculatedPixelClock 3b64
ReversedEdidHexCalculatedPixelClock 643b
TotalChecksum 9067
Checksum 149
HexChecksum 95
--- End code ---
Rataplan626:
--- Quote from: Justin on February 11, 2023, 03:24:46 pm ---Since I just moved from a CRT to an LCD (without G sycn/ Free sync) I am very interested in this.
I tried to set it up to plam Metal SLug 5 as a test, which reports a refresh rate of 59.1856....hz
I tried the following command, it seems to be setting the monitor up as I see no errors and it clearly is resetting things (black screen, then back on etc).
C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.185
or even
C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.186
However, testing Mslug5 I am seeing tearing just as usual (as if 60hz).
Am I doing something wrong?
This is the result I get:
--- Code: ---C:\mame\RatRefresh>ratrefresh -debug -min 55 -max 60 -refresh 59.186
Key SYSTEM\CurrentControlSet\Enum\DISPLAY\GSM5674\4&2cbcb734&0&UID16843008\Devic
e Parameters\EDID_OVERRIDE
WantedRefreshRate 59.186
CalculatedPixelClock 15204
HexCalculatedPixelClock 3b64
ReversedEdidHexCalculatedPixelClock 643b
TotalChecksum 9067
Checksum 149
HexChecksum 95
--- End code ---
--- End quote ---
What OS are you running, and what graphics card? Also, if you run REGEDIT and go to 'SYSTEM\CurrentControlSet\Enum\DISPLAY\GSM5674\4&2cbcb734&0&UID16843008\Device Parameters\EDID_OVERRIDE', does it actually have a 0-value with an EDID string? It should have, as I do an elevation-check, and also it should give an error when it was unable to write. Does the parent of that, so 'SYSTEM\CurrentControlSet\Enum\DISPLAY\GSM5674\4&2cbcb734&0&UID16843008\Device Parameters' have an EDID value?
I just tested on my work Intel NUC with Iris Plus 655 iGPU with 2 Dell U2421E monitors, and I seem to see the same issue. When I set anything below 59Hz it works fine when I view https://www.testufo.com/refreshrate. But anything between 59 and 60 results in 60.000Hz. I don't have that issue on my actual cab which also has an iGPU, but an older one with probably other drivers. If testufo doesn't lie (can't run MAME here) it might be a driver issue. Also, what are your mame.ini settings?
Justin:
Thanks for the detailed response!
I was running windows 7 at the time. I also tested it on my personal win 7 PC and there it gave me blues screens.
In any case I now updated the mame PC to windows 10 last night and hence I will test it there and see what happens. Is there a good reliable way to verify what hz the system is ACTUALLY running at once the settings have been applied? I looked at dxdiag and I'm not convinced that reports correctly or precisely (maybe it is rounding?).
Edit: just realized you posted an online tool to check refresh. Thanks!
Rataplan626:
Well, Windows 7 SHOULD work, as it supports EDID override. But I never tested it. The Intel drivers however support it since somewhere 2017-2018. Now I can't imagine your Win7 drivers being that old, but still. On my actual CAB with Win10 it works fine:
https://drive.google.com/file/d/1ZlpRVLiw7T9FNJsZmspD9JBE_3m5KCYJ/view?usp=share_link
however on my work-NUC it doesn't, as said anything between 59 and 60Hz gets 'rounded' to 60Hz. It did absolutely work on that NUC as well before, so I assume there's a bug (or feature?) in the current Intel driver.
So again, just to try to debug: what GPU / driverversion do you use?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version