Custom Resolution Utility (CRU)
|
11-19-2022, 04:59 AM
Post: #7057
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-19-2022 03:09 AM)mdrejhon Wrote: There are many mitigation measures that people do to compensate, and it's important for that person to adjust.My point is increasing the refresh rate wouldn't mitigate any of that because the frame rate would still be low. In fact, changing the refresh rate can actually increase judder if it's not a multiple of the frame rate. It would only help in games where you can make the frame rate synchronize with the refresh rate. Increasing the refresh rate for desktop use only has minor improvements like smoother mouse movement and smoother scrolling. If someone gets headaches from general computer use, the refresh rate is not likely the cause. (11-19-2022 03:09 AM)mdrejhon Wrote: You're correct for realtime-scanout displays (e.g. CRTs and unstrobed esports LCDs)I'm aware that global refresh displays exist, but they are such a small minority, and they tend to be TVs with additional processing lag, so anyone that cares about lag shouldn't be using them. The vast majority of monitors and TVs don't do global refresh. Strobed LCD is a different issue. The whole point of using QFT with strobing is to finish the scanout faster so there's more time for the pixels to change before the backlight strobes, which reduces crosstalk. QFT wouldn't reduce lag with strobing unless you make the backlight strobe sooner, but then that would negate the crosstalk reduction. (11-19-2022 03:09 AM)mdrejhon Wrote: I have access to thousands of displays -- and QFT reduces lag on more displays than you think. How many displays do you have access to....I'd like to know more about which displays do global refresh. The problem is most sites don't test lag properly or mention the scanout method, so I don't have enough information. For instance, RTINGS lag measurements include vsync lag measured in the center of the screen, so it's usually higher than the actual lag, and I don't see them talking about the scanout method. Other sites used inconsistently updating timers with wildly inaccurate results. Back when I tested displays, I always made sure to use a method that lets me see where the screen is refreshing to get more accurate measurements (vsynced vertical bars was the best method I found). All of the displays I tested did a normal scanout, even the ones that delayed frames. OLED is newer tech, so I don't know much about them. The part about OLED HDR needing the full frame is new information to me. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 66 Guest(s)