Blur Busters Forums

Abiak wrote:Ok so scanline sync 60 and fps limit 60?

No. Just scanline sync. Scanline sync is the FPS limiter. Do not apply any other FPS limiter on top.

Thanks.

Chief Blur Buster wrote: 8. Enable the Scanline Sync hotkeys, it makes calibration easier (arrow keys to move the tearline UP/DOWN)
Enable the Hotkeys to manually move the tearline up/down Add SyncHotkeys=1 to your config file to enable shortcuts. Hold CTRL+SHIFT while using UP/DOWN arrow to move the tearline up and down.

Can you explain this? Which config file?


Edit: nvm done...

This thread must be sticked at top.

My only problem with this whole thread is that it doesn't actually tell you how to enable the feature in RTSS, even though it's supposed to be a how-to!

How does one go about turning it on? I can see how to tweak the numbers, but how does one actually turn on the Scanline Sync, or is it done by simply changing the number there? I don't see any difference when I'm changing the numbers, so maybe I'm doing something wrong. Thanks in advance!

MrFix wrote: ↑

01 Dec 2019, 14:21

How does one go about turning it on? I can see how to tweak the numbers, but how does one actually turn on the Scanline Sync, or is it done by simply changing the number there? I don't see any difference when I'm changing the numbers, so maybe I'm doing something wrong. Thanks in advance!

1. Calibrate it using VSYNC OFF
2. Use horizontal panning motion (continual panning or strafing)
3. Use a game whose frame rate that rarely dip below Hz

I was trying to find the optimal way to use Scanline sync in a fps capped game (Game has fps limiter implemented and no way to uncap fps).

At the moment I have it running perfectly but I was curious whether the in-game limiter and RTSS's limiter are fighting against each-other,
since both are running in parallel?

Moreover, I was wondering if there is a way to disable RTSS's limiter, use the in-game limiter and therefore only use RTSS to apply tearline positioning?

ipiv wrote: ↑

15 Jan 2020, 03:31

At the moment I have it running perfectly but I was curious whether the in-game limiter and RTSS's limiter are fighting against each-other,
since both are running in parallel?

That's fine. They can both work at the same time. The lowest cap normally wins, but in scanline sync mode, RTSS will still cap the game just at the right moment for tearline positioning.

Moreover, I was wondering if there is a way to disable RTSS's limiter, use the in-game limiter and therefore only use RTSS to apply tearline positioning?

Scanline sync is the RTSS frame limiter. It's just a different mode of operation compared to normal FPS-based cap. In normal mode, RTSS just caps frame times to 1000/fps_cap milliseconds. In scanline sync mode, RTSS caps frame times to 1000/monitor_hz milliseconds with the exact time the frame limiter activates depending on the monitor's current scanout position.

Thanks, @RealNC.
I see, the action (fps limiter), which controls the scanline positioning is not actually a separate functionality as I had previously thought.

Yeah, I have it currently running perfectly and coupled with strobe crosstalk for blur reduction results in super smooth gameplay with minimal input lag.
Thanks to @Chief Blur Buster for the guide!

ipiv wrote: ↑

16 Jan 2020, 12:12

Thanks, @RealNC.
I see, the action (fps limiter), which controls the scanline positioning is not actually a separate functionality as I had previously thought.

Yeah, I have it currently running perfectly and coupled with strobe crosstalk for blur reduction results in super smooth gameplay with minimal input lag.
Thanks to @Chief Blur Buster for the guide!

You are very welcome!

Correct, scanline position is synonymous with framerate capping, since each pixel row (scanline) is scanned-out once every refresh cycle, as seen in high speed videos at www.testufo.com/scanout ...

Scanline sync cues on the exacts timing of the scanout of a single pixel row (raster based sync). It essentially guarantees fps=Hz if game engine can keep up. Which pixel row (scanline) to sync to, helps you determine tearline placement (in a perfect world, tearline location = scanline location -- but they're usually a few pixels apart due to overheads).

Fine tuning the scan line number, allows you to steer the tearline offscreen between refresh cycles (below bottom edge of current refresh / above top edge of next efresh .... when you metaphorically picture it as an endless reel of refresh cycles like the Blur Busters scanout diagrams, the "below/above" is conceptually exactly the same thing)

So in this sense, scanline sync really cannot be decoupled from framerate cap, it's really a fps=Hz cap unless you sync to 2 scanlines via custom config file edit, then it becomes fps=(2xHz) with the disadvantage of a on-screen tearline that cannot be hidden.