Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Talk about overclocking displays at a higher refresh rate. This includes homebrew, 165Hz, QNIX, Catleap, Overlord Tempest, SEIKI displays, certain HDTVs, and other overclockable displays.
Post Reply
alatron978
Posts: 1
Joined: 16 Aug 2020, 00:17

Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by alatron978 » 16 Aug 2020, 00:20

So I overclocked my Erazer X52773 1440p144hz (can't do 144hz stock) to 801p 500hz and know the monitor has more in it. The issue I ran into is I can't get refresh rates above 500hz to display as a select-able refresh rate, anyone to make refresh rates above 500hz appear?

User avatar
RealNC
Site Admin
Posts: 3737
Joined: 24 Dec 2013, 18:32
Contact:

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by RealNC » 16 Aug 2020, 05:05

SteamGitHubStack Overflow
The views and opinions expressed in my posts are my own and do not necessarily reflect the official policy or position of Blur Busters.

O_O
Posts: 19
Joined: 26 Oct 2020, 06:19

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by O_O » 31 Oct 2020, 19:23

alatron978 wrote:
16 Aug 2020, 00:20
So I overclocked my Erazer X52773 1440p144hz (can't do 144hz stock) to 801p 500hz and know the monitor has more in it. The issue I ran into is I can't get refresh rates above 500hz to display as a select-able refresh rate, anyone to make refresh rates above 500hz appear?
Sorry for the late reply. Yes, I have added 600Hz but it doesn't make any difference, in my case I cannot set higher than 499Hz even though the limit is quoted as 512Hz? Did you get exactly 500Hz? Don't know why there's variance if it's hard coded to 512Hz, really need to trace the syscall NtUserChangeDisplaySettings to find out whats going on :(

Edit: Just to clarify, W10 20H2 does not entertain 500.000 and higher. For instance 499.982Hz works at 800x600 but not 500.000 even if resolution is lowered to 640x480.

Image

Image
Note: 500Hz rounded up from 499.982
Last edited by O_O on 15 Nov 2020, 22:13, edited 1 time in total.

User avatar
Chief Blur Buster
Site Admin
Posts: 11647
Joined: 05 Dec 2013, 15:44
Location: Toronto / Hamilton, Ontario, Canada
Contact:

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by Chief Blur Buster » 31 Oct 2020, 19:31

I currently now a very, very, very alpha build of Windows capable of 1000Hz refresh rate and are working with multiple vendors to validate successfully breaking the 500 Hz barrier.

Unfortunately, due to NDAs involved, I can't yet disclose the method. There are multiple weak links outside Windows, such as driver bugs and driver limitations. I'm working on whac-a-mole of all the weak links.

Rest assured Blur Busters is on top of this behind-the-scenes corporate red-tape cutting, naysayer-convincing, bureaucracy domino tipping, at multiple corporations. Patience...

I estimate end users will have to wait potentially a few years before users can test-CRU resolutions above 500Hz... Consider this "Valve Time" for now. Windows is not the only problem; the whole refresh rate chain has multiple problems along the chain (e.g. GPU limitations, graphics drivers limitations, etc) that needs to be debugged & add support for.

Hang tight is what I can say. 1000Hz display refresh rates is eventually coming.
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter

Image
Forum Rules wrote:  1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
  2. Please report rule violations If you see a post that violates forum rules, then report the post.
  3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!

O_O
Posts: 19
Joined: 26 Oct 2020, 06:19

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by O_O » 01 Nov 2020, 18:39

That leaves me wondering about EDID spec.

User avatar
Chief Blur Buster
Site Admin
Posts: 11647
Joined: 05 Dec 2013, 15:44
Location: Toronto / Hamilton, Ontario, Canada
Contact:

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by Chief Blur Buster » 02 Nov 2020, 14:05

O_O wrote:
01 Nov 2020, 18:39
That leaves me wondering about EDID spec.
The new DisplayID embedded as a CEA-861 Extension Block in EDID, supports 1000 Hz refresh rates just fine.

The latest verison of ToastyX CRU can create >500Hz via CRU -> Extension Blocks -> Switch from "CEA-861" to "DisplayID" -> Add -> Detailed Resolutions -> Add Blocks -> Add -> DisplayID -> Edit the DisplayID (looks like a regular custom resolution editor, but accepts quadruple-digit refresh rates).

The current DisplayID limit is about 6752.19 Hz, which is enough for a few decades of retina-ing out the refresh rate race, even though 6752 Hz is below retina refresh rates in certain situations (180-degree FOV retina-resolution VR, wold actually show human-visible limitations of 6752 Hz...)

Nontheless, that particular weak link is solved clear all the way to practical external-screen monitor refresh rates, as >6000Hz would mainly only be beneficial in simulating a Holodeck (aka retina-resolution VR headset). For all practical intents and purposes, it's essentially in the territory of retina refresh rate for external 2D planar displays.

Not all displays will recognize these DisplayID Extension Blocks on the standard EDID protocol, mind you. And you definitely won't be able to use any Windows older than Windows 10 for any timings-standardized refresh rates >500Hz in the future. (non-custom bitplane packing that Viewpixx and others do to cram a higher refresh rate inside a lower refreshrate stream)
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter

Image
Forum Rules wrote:  1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
  2. Please report rule violations If you see a post that violates forum rules, then report the post.
  3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!

O_O
Posts: 19
Joined: 26 Oct 2020, 06:19

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by O_O » 02 Nov 2020, 20:13

Cool, I didn't know that. Thanks for the information, will take a look at ToastyX.

ToastyX
Posts: 41
Joined: 28 Dec 2013, 14:52
Contact:

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by ToastyX » 01 Jan 2021, 18:56

Chief Blur Buster wrote:
02 Nov 2020, 14:05
The current DisplayID limit is about 6752.19 Hz, which is enough for a few decades of retina-ing out the refresh rate race, even though 6752 Hz is below retina refresh rates in certain situations (180-degree FOV retina-resolution VR, wold actually show human-visible limitations of 6752 Hz...)
DisplayID 1.3 supports a pixel clock up to 167772.16 MHz, and DisplayID 2.0 supports up to 16777.216 MHz. CRU 1.4.2 wouldn't allow more than 10000 Hz/kHz to prevent overflow issues with calculations, but I've worked that out in CRU 1.5.

41648hz.png
41648hz.png (12.8 KiB) Viewed 8180 times

The VESA CVT formulas also completely break down at higher refresh rates because the minimum required blanking time exceeds the total refresh time, so they're going to need a new standard for extremely high refresh rates.

User avatar
Chief Blur Buster
Site Admin
Posts: 11647
Joined: 05 Dec 2013, 15:44
Location: Toronto / Hamilton, Ontario, Canada
Contact:

Re: Unable to get refresh rates above 500hz to display in as a selectable refresh rate.

Post by Chief Blur Buster » 01 Jan 2021, 20:17

ToastyX wrote:
01 Jan 2021, 18:56
DisplayID 1.3 supports a pixel clock up to 167772.16 MHz, and DisplayID 2.0 supports up to 16777.216 MHz. CRU 1.4.2 wouldn't allow more than 10000 Hz/kHz to prevent overflow issues with calculations, but I've worked that out in CRU 1.5.
Great to hear! Thanks for doing this...
No utility formerly let me create refresh rates higher than 6752, so I am very glad to be mistaken.

Still disappointed that the dot-clock limit is lower in DisplayID 2.0 (16.7 GHz) than in 1.3 (167 GHz) because that prevents single-cable 8K 1000Hz which requires a minumum of slightly above 33GHz dotclock at minimum possible blanking intervals. That said, no cable supports 167 GHz 24bit pixel clocks anyway, so this is moot for now.

There is even an engineering path to 8K 1000Hz inside of this decade! Hopefully a future version of DisplayID resolves this.
ToastyX wrote:
01 Jan 2021, 18:56
The VESA CVT formulas also completely break down at higher refresh rates because the minimum required blanking time exceeds the total refresh time, so they're going to need a new standard for extremely high refresh rates.
Yes, so Manual is going to be required for now.
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter

Image
Forum Rules wrote:  1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
  2. Please report rule violations If you see a post that violates forum rules, then report the post.
  3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!

Post Reply