How to use Scanline sync with Lossless Scaling (Fix tearing without latency penalties)

[sharp plume]

This guide is for those who wants the minimum latency possible without being annoyed by those nasty screen tearing lines.

First thing first, make sure to have RivaTuner Statistics Server installed on your device.

From there, uncap the Global table/game to 0 and set the Scanline sync to x/2 by clicking on it two times:

Now, click on Setup by the bottom left corner, scroll down and make sure to set the Global/game frame limiter to async, and close the window.

From here, add LosslessScaling.exe to RTSS and cap it to your refresh rate, set Scanline sync value to 1040, or tweak it manually in hundreds till your tearing is gone (100,200,300,400...)

Open Setup again and make sure LosslessScaling.exe frame limiter is set to async and close the pop-up.

• make sure to enable "Allow tearing" in Lossless Scaling window.
• do not use any other type of frame limiter in RTSS otherwise whis method won't work.

[twilit kite]

really good guide, fixed my tearing completely!

[gentle fulcrum]

So if I have a 120hz display, I set my fps cap to 12?

[sharp dove]

how about hybrid scanline sync👌

[fervent garden]

Thanks so much for this! 😄 ❤️

[fervent garden]

Btw, if my system is 60hz/60fps - setting to 1040 will be fine? @sharp plume

[sharp plume]

I suggest you to change the values manually and see which value works better for you.

you are welcome 😄

[fervent garden]

Seems to be no tearing with 1040 so I'll leave it at that lol thanks again 😁😜😀

[fervent garden]

How do I save scanline sync to x2?

I set x2 and it goes back to normal...

Nevermind 😄 it's x2/s not x2. Saved it now 😄

[lime beacon]

Can add settings LosslessScaling?
@sharp plume

[glacial valley]

RTSS can't even cap my lossless scaling so scanline sync can't work

it just caps the ui not the actual gameplay window

[fervent garden]

Same mate but: It DoEs NoT wOrK 😭🤣😂

[glacial valley]

yeah, try a 10fps cap, your LS window won't be capped but the scrolling in the menu of LS will be

[sharp plume]

Try this:
Reset scanlyne sync configs, and cap your games at half your refresh rate, therefore just go to "LosslessScaling.exe" in RTSS and set the scanlyne sync value to something like 1040, and remember to keep async in setup (meanwhile you can set NVIDIA REFLEX or back-edge sync in the games .exe while maintening async on LS)

[glacial valley]

if fps cap of rtss doesn't cap the game window then scanline sync definitely can't

it works on the lsfg menu/gui only

[sharp plume]

Something weird is going on, if I cap my Lossless Scaling to something like 50, the frame gen becomes laggy as if I capped it to 50, but if I set it to 74 (my refresh rate) it becomes smooth

[glacial valley]

try 10fps that would be a 100% certain test

for me only scrolling through the options in LS ui is capped by rtss

no effect on the capture window

and had several people say the same thing

[sharp plume]

Alright, I'll test this later and post the results here.

[sharp plume]

There it go my friend

It's pretty visible that limiting Lossless Scaling (at least in my setup) works.

First video it's at 10 fps cap, and second a 1 fps cap

And, there's no tearing at all, even at such low fps

Now, this one it's from 37 to 73.992012, no tearing at all, and vsync is disabled

[glacial valley]

well weird that it doesn't work on 2 of my systems and several other ppl too

but works on yours and some others

very very weird

[fervent garden]

🤣 I love it when people are proved wrong! 😄

[glacial valley]

this is a "works on my machine" moment

you're the one making it an ego thing

sometimes things work differently on 2 diff pcs. Like I said, me and a few others can't get it to work

[fervent garden]

Yet to see these "several other people" and your proof! Works great.

I have 2 gaming PCs (both AMD) and it works as intended. Seems it's a you problem.

[glacial valley]

yeah it's my problem since it doesn't work on my 2 machines. Idk why you have an attitude about it, ya weirdo

#💬│lossless-scaling message

[fervent garden]

😂🤣 I don't have an attitude about it at all. You were proven wrong. That's it. And now you're going to click "1 blocked message" and see what I say anyway. Kids, heh.

[glacial valley]

just because it works on one machine doesn't mean it works on everyone's. I assumed it doesn't work for anyone because it didn't work for me or vlbastos

especially because I tested 2 separate pcs

and yeah I blocked you because you're really annoying

[fervent garden]

I'm annoying????? Mate, you're posting rubbish then you get proven wrong and block people. I'm still waiting on your proof and these several other people. You know what. Forget it, you're blocked now.

[sharp plume]

Guys, chill, later I'm gonna try to figure out why it works in my pc, and maybe find the cause that made it work.
My supposition it's nvidia control panel settings.

[fervent garden]

I don't like being called a "weirdo" when he doesn't know me. I'll report him to the mods.

[glacial valley]

let me know what you find out

if it works with some change to some setting(doubt, no idea what could be causing the wrong window to get capped) that would be cool, potentially a slight extra boost to latency over nvcp fast sync

too bad can't use special K latent sync as lsfg freezes on SK injection

but yeah I tested rtss+LS on 2 separate machines 1 amd 1 nvidia

no dice

works to cap the LS gui only in both cases

[fervent garden]

@sharp plume Any update?

@glacial valley I apologise 🙂

[sharp plume]

I couldn't find the reason of the issue guys sorry

Seems like it's not nvcp

Very weird

[dawn topaz]

If you want the best latency, just don't use RTSS to cap the game frame rate and prefer the in-game fps limiter instead.
https://cdn.discordapp.com/attachments/1236717847011393546/1244726166489792645/image.png?ex=66577a93&is=66562913&hm=9b713663c097069e0ef08df75445d3609e07f8eb789a61359386b8ee26b7f008&
https://cdn.discordapp.com/attachments/1236717847011393546/1244726167429185649/image.png?ex=66577a94&is=66562914&hm=4fdb4340a75d36972435d184ceb422520b803205be4293211115fc6adcc5038c&
Screenshots display 72 FPS with in-game FPS limiter and 72 FPS using RTSS FPS limiter (same results on all fps limiter modes - async/front/back/reflex)
RTSS alone MIGHT increase "Present latency" significantly and using LS might make it feel a lot worse. For me it ranges from 5 to 10ms.

[torn heath]

Hello, can I use the scanline sync and the Nvidia reflex from Riva Turner?

[dawn topaz]

Its possible.

[cerulean rune]

scanline sync requires the async limiter (hybrid scanline sync requires either back or front edge sync)
whenever a user sets Reflex to be used with either method or an unsupported API (like Vulkan, OpenGL, D3D9, D3D10), RTSS falls back to async

- Added new framerate limiting mode : NVIDIA Reflex mode. [...] Please take a note that NVIDIA Reflex framerate limiting mode is currently supported on NVIDIA GPUs and in Direct3D11/Direct3D12 applications only. If you try to enable it on unsupported hardware on in unsupported applications, RivaTuner Statistics Server will fall back to default async framerate limiting mode.

https://forums.guru3d.com/threads/msi-ab-rtss-development-news-thread.412822/page-213#post-6192098

[bitter lantern]

What do I use to limit my base in-game framerate?

[glacial valley]

unblocked!

[gentle fulcrum]

Hi I have a 120hz display what should I set my refresh cap to in RTSS?

[ashen smelt]

I have tried to get this working. I think it does work.

Is there a reason that LS is recommended to use Async framerate limiter? Why would you not use back-edge sync on both? Does it only apply to one app or something?

[lethal halo]

This is so buttery smooth

[cerulean rune]

front/back edge are for the hybrid mode, which is less taxing on the gpu because is not constantly refreshing the tearline position as async does, however, it takes a bit more tweaking since you have to find a value approximate to the display's real refresh rate, down to 6 decimals preferably

and sometimes that isn't enough, you have to tweak it further so that the "present" value does not constantly vary and the tearline doesn't move much; it's finicky to have it working properly but worth the time

oakenglass has a nice video about it
https://youtu.be/X1Vhm8eXfCQ?t=293

[ashen smelt]

@cerulean rune Thanks for that. I guess that is why async is important then on Lossless (as you cannot control the frame generation pacing)

I followed Oakenglass guide to try and setup the games refresh rate. I did the refresh rate to 6 decimal places, then divided it by two (to try and do X2 generation mode).

When I use the RTSS standard present mon overlay. The app latency in ms is lower using Front Edge sync that it is using Back Edge Sync

[cerulean rune]

is the present value constant with just dividing by 2? in my case, I had to further adjust it
and regarding back/front edge, I'm getting the same results as you, however frame times seem more consistent with back edge, difference between the 2 on my system is about 5-7ms less for front edge

[ashen smelt]

@xvt I'll try and capture some images today showing you what I can see. I need to learn to use PresentMon or Capframe I think

[polar ginkgo]

this unfortunately does not work for me

[rich drum]

seems like lossless scaling doesn't work with rtss anymore

so I can't use this or even try it

[blissful pecan]

what, why not?

[rich drum]

Idk rtss stopped working for lossless for me but it works fine for others

A few other people also experience this

[urban sand]

You seem to be the one being fully in ego and rude on here buddy, manners is always appreciated in any situation.

[west spoke]

dang this doesn't work for me either 😦

[rich drum]

damn I wonder why that is

[mighty yarrow]

not work

[abstract spindle]

awesome it works like butter! ty alot for this guide

[silk forum]

Glad I found this. No tearing. Off-allow tearing is selected in Lossless scaling. Working great. 😄

If anyone wants some help setting it up, feel free to ping me here or in DMs

[silk forum]

As you can see, no tearing. It's a bit tricky but it definitely works.

[topaz pulsar]

What im doing wrong then

I keep getting massive tearing with allow tearing

[safe gale]

same here

[rich drum]

same

[tidal jetty]

Can someone please tell me how to do it with an AMD graphics card? I know that in theory it is doing the same thing as OP, but there are several things that are not made clear. For example, my monitor is 144hz and I don't know what the OP's is.

I also want to know how much to limit it to in Rivatuner. I usually set it to 72 FPS so that with LS I can reach 144.

Can someone please guide me?
@sharp plume

Here I show my current configuration

[safe solstice]

Same here. Win11 23H2.

[silk forum]

Upgrade to 24H2. RTSS has issues with 23H2 iirc....

[silk forum]

Your scanline sync number should always be a minus. Right now mine is set to: -490 because that's what I use to get no tearing. Each PC with RTSS is different so this number might not work for you. It also depends on your resolution, too. I'm at 1080p.

[safe solstice]

Issues such as?

[silk forum]

... issues such as not working when trying to cap your fps.

[sick light]

this seems to be quite random, or maybe i'm looking at the wrong place. I was able to find the correct scanline placement for my game (fortnite) at -60. But when I go and tweak the scanline for lossless, even if I eventually find a good placement for it, if I need to alt tab or re-apply LSFG, the sync line will randomly appear somewhere else. Meaning I would have to re-tweak it every single time I apply LSFG, and sometimes it breaks even with the slightest stutter from my pc (rx 6750xt + r5 5500 + 32gbddr4). And even if I go from -1, to -2, and then back to -1 again, the break line will be different.

i was able to find my monitor's real refresh rate at 144.9966

so I lock the game at 72.4983 for a perfect half

although i found the scanline for the game at native (non lsfg) at 144.9966hz

and it seems to translate well to 72.4983

[sour sand]

Sure

I'm using low lag vsync atm

[sour sand]

Doesn't work for me either

Unfortunately

[regal salmon]

Worked for me perfectly👌 Thank you OP

[untold storm]

Love this

[hearty pier]

If you have G-Sync you don't even need to do this. You simply enable NVIDIA Reflex as the limited (global) and set it at least 2 frames below the max refresh rate /2. My refresh is 120hz so I've set this to 58. Then enabled G-Sync on LS and Disabled Sync (tearing) and I get no tearing at all.

[sour sand]

No way

Maybe think first

[hearty pier]

Well it's working fine for me.

[sour sand]

That's not the point

We wouldn't be here if we had gsync

https://tenor.com/view/winnie-the-pooh-think-think-gif-15324290528311488474

[hearty pier]

Oh I'm sorry. I didn't knew this only worked without G-Sync

[bitter lantern]

It's just another sync method

Completely different thing

Targets max refresh instead of below max

[open lichen]

No longer works. RTSS used to be able to cap fps in LS, but now it doesn't do anything, so scanline sync doesn't work either