News for hackers. Stuff that matters.
Re:Raytracing won't simplify AAA real-time rendering by Ygg2 on Monday December 28, 2020 @05:12AM (#25558053)
I think after 144Hz, you hit a point of really diminishing returns. Like is it possible in blind test to feel 240Hz vs 144Hz? It might give you in game like 1% advantage for +100% the costs.
Re:Raytracing won't simplify AAA real-time rendering by dmytroi on Monday December 28, 2020 @05:26AM (#25558116)
FWIW tried testufo [0] with Samsung G7, 240Hz vs 144Hz was very noticeable on image and text scrolling tests. I guess for a person who never seen 240Hz it would be hard to identify it in a blind test, but after you've seen how the images/text looks like in scrolling, it's trivially identifiable.

- [0] testufo.com

Re:Raytracing won't simplify AAA real-time rendering by Ygg2 on Monday December 28, 2020 @06:56AM (#25558539)
But that's the point. If in a blind test you can't tell the difference, then there is very little to no perceptible difference.

If testufo was randomized with multiple repeating patterns and random offsets, it could be a much better test. Here you can accidentally bias yourself.

Re:Raytracing won't simplify AAA real-time rendering by codetrotter on Monday December 28, 2020 @05:42AM (#25558179)
240 is not evenly divisible by 144. Curious to know if 240 vs 120 Hz is more or less noticeable on a 240 Hz monitor than 240 vs 144 Hz on a 240 Hz monitor.
Re:Raytracing won't simplify AAA real-time rendering by doikor on Monday December 28, 2020 @05:59AM (#25558245)
With games as long as you have good enough hardware to run the game at a steady frame rate you want it being divisible by some magic number does not matter. Also the old "standard" Hz for games is 60hz so going to 120 and then to 240 is the "natural" steps.

The old 144hz goal was/is nice if you want to display 24fps (movies) content but games don't work like that. They display correctly without any judder/pulldown at whatever frame rate you want (as long as you have the hardware to run it at that rate)

Re:Raytracing won't simplify AAA real-time rendering by q-big on Monday December 28, 2020 @09:59AM (#25559639)
> 240 is not evenly divisible by 144.

Sounds like the beginning of a sales pitch for a 720 Hz display. :-)

Re:Raytracing won't simplify AAA real-time rendering by smnscu on Monday December 28, 2020 @08:22AM (#25558980)
While they are more entertainment than science, I believe LTT performed a few tests like on this topic:

- https://www.youtube.com/watch?v=tV8P6T5tTYs - https://www.youtube.com/watch?v=OX31kZbAXsA

Re:Raytracing won't simplify AAA real-time rendering by nightcracker on Monday December 28, 2020 @04:30PM (#25563450)
As someone who owns a 240hz monitor, absolutely.

And here's how I can probably immediately convince you that I can as well: drag your cursor at a rapid speed across your screen back and forth (e.g. 2-3 times across the width per second). Focusing on one spot, do you see individual cursors with gaps of background in between? (I'm assuming yes.)

Now on 120 Hz the gaps will be half as big as on 60 Hz. On 240 Hz they are half as big once again, but they are nevertheless noticeable. The size of the gaps easily allows you to distinguish between 120 and 240 Hz.

Until I can drag my cursor across the screen and see nothing but a continuous moving object, we haven't hit diminishing returns on monitor refresh rate yet.

Re:Raytracing won't simplify AAA real-time rendering by TwoBit on Monday December 28, 2020 @09:36PM (#25566102)
Just because there's some measurable difference doesn't mean it has significance.