#The fps limited by the secondary screen

71 messages · Page 1 of 1 (latest)

young junco
#

Hello everyone,

Here's my system specification:

  • RTX 3070 for the PCIe 4.0 x16 slot (for real frame rendering).

  • GTX 1650 for the PCIe 3.0 x16 slot (for frame generation).

  • Main monitor: 1440p 185Hz (connected to the GTX 1650).

  • Secondary monitor: 1080p 60Hz (connected to the RTX 3070).

This is the problem I'm facing:

When I turn on the secondary monitor (connected to the RTX 3070), as shown in the first picture, Lossless Scaling (which is running on my GTX 1650) only takes 60 FPS of real frames to generate fake frames.

However, when I turn off the secondary monitor, as shown in the second picture, Lossless Scaling takes all my real frames to generate fake frames (this is how it should work, and how it should also work in the first scenario).

How can I fix this? Thanks for reading.

image.png IMG_20250726_192958.jpg
sand crown
#

Seems like your second monitor has some kind of overlay or something on it that LS picks up

#

Have you tried connecting it to the 1650 as well?

young junco
#

yes, i tried conectting it to 1650 but the fps also limited

sand crown
#

Also if you're on a consumer platform your second slot isn't actually x16 that's also something to consider

young junco
#

i dont think that is the problem because as you can see in the second pic it running good

#

and i have check my mainboard spec in the internet also

sand crown
#

What's your mobo?

young junco
#

i just asked ai and it said my secondary pcie lane is just pcie 3 x4

#

but i just play in 1440p with 185 fps, and i read it is enough

sand crown
#

Yeah it'll cap out at around 200 FPS

#

Anyways do you have something like Nvidia Shadowplay running?

#

And what version of Windows are you on?

young junco
young junco
sand crown
#

Exact version

#

23h2, 24h2 etc.

young junco
sand crown
#

Tried WGC Capture API?

young junco
#

yeah i tried both

sand crown
#

Weird

#

WGC should bypass that

young junco
#

:((

#

And my second screen is broken now, it's stuck in an open loop.

#

maybe it's the problem

sand crown
#

Open loop?

young junco
#

i will update when i fixed it

sand crown
#

I've had this too

#

Nvidia app?

young junco
#

i think it keep open and make lossless scaling set wrong

young junco
sand crown
#

It's an issue with the app, I have it too

young junco
#

i pluged it on my chromecast then it had the same problem

#

so that is because my monitor hardware:(((

sand crown
#

Hmm

#

I still don't understand how that should affect LS tho, that's weird

#

That didn't happen with a single GPU?

young junco
#

i haven tested that yet

rancid python
young junco
rancid python
young junco
#

It have the same problem with a single gpu

rancid python
young junco
#

Maybe bc my damaged monitor or idk

young junco
sand crown
#

Seems like some overlay that's somehow tied to your second monitor

#

Is the Chromecast still plugged in?

young junco
#

no

rancid python
#

wait...

#

your one monitor is 60hz

young junco
#

yeah

#

i think that's the problem

rancid python
#

okay, let me confirm...

when only the 180hz monitor is connected to 1650 everything is working or not?

#

in this case the 60hz monitor should be physically disconnected

young junco
#

If my second screen keeps getting stuck in that open loop, then Lossless Scaling might be detecting that state and consequently limiting itself to the monitor's 60Hz refresh rate. That's what i think

young junco
rancid python
#

i think when 3070 is connected to 60hz display and then LS is used to capture, it is only capturing the output 60fps

#

instead, try connecting both monitors to 1650

#

and i assume you've properly designated the displays in ls

sand crown
#

We already tried that

young junco
#

i tried but it keep limit:))

#

i gonna fix my monitor tomorrow

#

I've replaced my monitor with a different screen (my TV), and the FPS is no longer limited.

#

Now I'm certain it's my monitor that's faulty.

#

Thank you everyone for your help!!!!

sand crown
#

Weird but solved at least

young junco
#

I was also surprised that turned out to be the solution. :)))