Blur Busters Forums

sky_dynasty wrote: ↑

29 Jan 2024, 13:54

My source for the information above:

That's not a source of information, that's a source of misinformation. That 1ms rule is utter nonsense.

I know this is a dead thread but... I am having the EXACT same issue and am wondering if anyone has found a solution. My stop-gap solution at the moment is to set my secondary 144hz monitor to my primary CRT's refresh rate, so they are both 100hz. This works, but it's quite annoying to disable all ...

I see no mentions of hybrid scanline sync mode, which was introduced in RTSS about a half year ago. Here is some basic info about it, which can be useful in context of this HOWTO thread:

https://forums.guru3d.com/threads/msi-a ... st-5951576

-3FPS cap is for VRR. -0.01FPS cap is for normal vsync without VRR. I wasn't aware of this.. if I'm using scanline sync then I have to set the screen refresh to 60Hz and set the refresh in the settings to 16.66944ms? (which would be for 59.99fps) or do I have to set it elsewhere? No. With ssync, RT...

IDEA! (Usability/Debugging): A mode where a horizontally moving vertical bar is overlaid on game graphics ( like this one ) could be great for RTSS Scanline Sync. Make that a transparent overlay on top of RTSS, perhaps colored the same as the graph/framerate counter. Done, it is implemented in upco...

IDEA! (Usability/Debugging): A mode where a horizontally moving vertical bar is overlaid on game graphics ( like this one ) could be great for RTSS Scanline Sync. Make that a transparent overlay on top of RTSS, perhaps colored the same as the graph/framerate counter. Personally I use RTSS FCAT over...

Did you use the frame colour indicators? Those I found to be more accurate than frame times as even with a 100% stable frame time, sometimes the frame colour indicators flickered and if I focused on the flickers instead, I got it smoother than if I focused at the frame time. There will be a few mor...

However, if you're hooking Present() and doing an inputdelay before the real Present(), there will be latency. That's the only case in context of this thread, Marc. Any third party limiter (and even NV's own framerate limiter) is technically a Present() hook from application's point of view with de...

Thank you, that makes sense. But I disagree that waiting before presenting _always_ increases latency. It depends on definition of latency. If we're talking about input latency then wait before present always increases it. If we're talking about render latency, then wait before present can decrease...

RTSS imposes its limit after Present returns, which really sucks if the application has VSYNC enabled since a full swapchain + n-many queued undisplayed frames causes the calling thread to be re-scheduled. The DWM uses a signal-based (VBLANK) wait when it reschedules threads, RTSS just uses Sleep (...