“Now wait for 1,000 Hz content and capable GPUs.”
Forget the content and GPU, you need an input port capable of that.
HDMI 2.1 and Display Port 1.4 cap out at, what? 240?
So you just need 3 4090’s with 1 displayport each to the monitor and a whole new version of sli.
… I actually wonder if the graphics cards could multiplex across multiple dp to a single display.
Isn’t 4k 360hz equivalent to 1080p 1440hz? I wouldn’t expect 1000hz at 4k any time soon but 1080p in competitive FPS is easy
“Now wait for 1,000 Hz content and capable GPUs.”
Now wait for humans who can see the difference
Here’s a real-world use case where this difference is noticeable to the average person. We don’t need to render video games at 1000 Hz, but many things that can be rendered with comparatively low GPU power could be made a better experience with it. The real question is whether/when the technology becomes cheap enough to be practical to use in consumer goods.
Here is an alternative Piped link(s):
Here’s a real-world use case where this difference is noticeable to the average person
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
I’m sure some people will demand it. But for 99.9% of the population you don’t need 1000Hz content. The main benefit is that whatever framerate your content is it will not have notable delay from the display refresh rate.
For example if you are watching 60Hz video on a 100Hz monitor you will get bad frame pacing. But on a 1000Hz monitor even though it isn’t perfectly divisible. the 1/3ms delay isn’t perceptible.
VRR can help a lot here, but can fall apart if you have different content at different frame rates. For example a notification pops up and a frame is rendered but then your game finishes its frame and needs to wait until the next refresh cycle. Ideally the compositor would have waited for the game frame before flushing the notification but it doesn’t really know how long the game will take to render the next frame.
So really you just need your GPU to be able to composite at 1000Hz, you probably don’t need your game to render at 1000Hz. It isn’t really going to make much difference.
Basically at this point faster refresh rates just improve frame pacing when multiple things are on screen. Much like VRR does for single sources.
Here’s a big part of why they want 1000Hz. You don’t need to fully re-render each frame for most cases where 1ms latency is desirable - make a 100 Hz (or even 50 Hz) background and then render a transparent layer over it.
Here is an alternative Piped link(s):
Here’s a big part of why they want 1000Hz
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
Who needs 1000hz refresh rate? I understand it’s impressive, but 120hz already looks smooth to the human eye.
I think the perceptual limit is around 60 or 80fps, but don’t quote me on that
Competitive (professional) gamers?
Seems there are diminishing returns, but at least some gains are measurable at 360.
In thought that 60Hz was enough for most games, and that for shooters and other real time games 120 or 144 was better. However, it reaches a point where the human eye can’t notice even if it tried.
Honestly, going up in framerate t9o much is just a waste of GPU potency and electricity.
A better way to look at this is frametime.
At 60 FPS/Hz, a single frame is displayed for 16.67ms. At 120 Hz, a single frame is displayed for 8.33ms. At 240 Hz, a single frame is displayed for 4.16ms. A difference of >8ms per frame (60 vs 120) is quite noticeable for many people, and >4ms (120 vs 240) is as well, but the impact is just half as much. So you get diminishing returns pretty quickly.
Now I’m not sure how noticeable 1000 Hz would be to pretty much anyone as I haven’t seen a 1000 Hz display in action yet, but you can definitely make a case for 240 Hz and beyond.
It’s pretty easy to discern refresh rate with the human eye if one tries. Just move your cursor back and forth really quickly. The number of ghost cursors in the trail it leaves behind (which btw only exist in perception by the human eye) is inversely proportional to the refresh rate.
The obvious awnser would be VR and AR where the faster the refresh rate is the less likely you are to get motion sick. A display with a refresh rate that high would be displaying a frame every millisecond meaning if the rest of the hardware could keep up a headset using this display would be able to properly display the micro movements your head makes.
Here’s a real-world use case that also won’t require insane GPU power.
Here is an alternative Piped link(s):
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
I would be happy with a 240hz 4k that doesn’t have a subtle hum when it’s going that hard. It’s hard to test for because shops are too loud to hear it, but in a quiet office it gets very noticeable.
Please stop
Your eyes can’t possibly tell the difference. We’re past the max eye resolution at this point.
After having a TCL smart TV that constantly smells like burning plastic, even a year after using it, I’m not sure I would want another of their product in my home.