Maximum pre-rendered frames question (in Nvidia inspector)

Todas as discussões > Fóruns Steam > Hardware and Operating Systems > Detalhes do tópico

Este tópico foi trancado

COWZYOV 22/abr./2020 às 19:35

Maximum pre-rendered frames question (in Nvidia inspector)

Aside from input lag, can there be any disadvantage in putting this setting at 8 (I’m trying to improve fps for a cpu bottleneck)?

Can setting it to “application controlled” yield better fps than setting it to 8?

< >

Exibindo comentários 1–15 de 87

Bad 💀 Motha 22/abr./2020 às 19:46

It should always be set to 1.
Adding input lagg should always be avoided.

Autumn_ 23/abr./2020 às 3:13

Escrito originalmente por AÀÁÂÄÆÃÅĀ:
Aside from input lag, can there be any disadvantage in putting this setting at 8 (I’m trying to improve fps for a cpu bottleneck)?

Can setting it to “application controlled” yield better fps than setting it to 8?

Check your other thread, I posted the answer there, before I saw this one.

Escrito originalmente por Bad 💀 Motha:
It should always be set to 1.
Adding input lagg should always be avoided.

No, it shouldn't. That's why it's a setting that can be changed.
In a CPU bottlenecked enviroment, this will increase FPS, which will reduce input lag.

Snow 23/abr./2020 às 6:28

It's more about framerate drops than average framerate. 8 is very unlikely to give any FPS advantage over 3, so there is no reason to set it higher than 3.

Vulkan 23/abr./2020 às 7:04

Escrito originalmente por Bad 💀 Motha:
It should always be set to 1.
Adding input lagg should always be avoided.

ive found that setting low latency mode to on aka pre rendered frames 1 can cause stutter in some games so it most definitely is not a set and forget setting. you need to experiment on a game to game basis

stoneyoda 23/abr./2020 às 7:34

Escrito originalmente por Savage Southerner:
Escrito originalmente por Bad 💀 Motha:
It should always be set to 1.
Adding input lagg should always be avoided.
ive found that setting low latency mode to on aka pre rendered frames 1 can cause stutter in some games so it most definitely is not a set and forget setting. you need to experiment on a game to game basis

Anyone using Nvidia inspector should probably read this to get a better understanding of what each setting does.

https://github.com/CHEF-KOCH/nVidia-modded-Inf/blob/master/Docs/NVIDIA%20Profile%20Inspector/nVidia%20Inspector%20Options%20Explained.md

Jamebonds1 23/abr./2020 às 12:25

Input lag can't be reduced, but with correct monitor settings, it can get you a lower input lag as possible. Usually, it should be in gaming mode.

I had my TV set to high-speed FPS for a movie, but I keep lose to battle online on my PS4. But then when I set it to a gaming mode, I get better at battle online.

Última edição por Jamebonds1; 23/abr./2020 às 12:29

Autumn_ 23/abr./2020 às 12:40

Escrito originalmente por Jamebonds1:
Input lag can't be reduced, but with correct monitor settings, it can get you a lower input lag as possible. Usually, it should be in gaming mode.

I had my TV set to high-speed FPS for a movie, but I keep lose to battle online on my PS4. But then when I set it to a gaming mode, I get better at battle online.

Lots of things impact input lag, not just monitors.

User > Mouse/keyboard (Polling rate, processing speed, sensor or switches) > USB processing speed > OS processing inputs > Program processing inputs > GPU rendering frames (depends on when the data of movements was sent to the GPU in the form of scene info) > Monitors buffer setup > Monitors actual input latency. (And from there, to some degree, response time, but thats kinda moot.)

The monitor is only a fraction of what's effecting latency.

Jamebonds1 23/abr./2020 às 12:52

Escrito originalmente por Autumn:
Escrito originalmente por Jamebonds1:
Input lag can't be reduced, but with correct monitor settings, it can get you a lower input lag as possible. Usually, it should be in gaming mode.

I had my TV set to high-speed FPS for a movie, but I keep lose to battle online on my PS4. But then when I set it to a gaming mode, I get better at battle online.
Lots of things impact input lag, not just monitors.

User > Mouse/keyboard (Polling rate, processing speed, sensor or switches) > USB processing speed > OS processing inputs > Program processing inputs > GPU rendering frames (depends on when the data of movements was sent to the GPU in the form of scene info) > Monitors buffer setup > Monitors actual input latency. (And from there, to some degree, response time, but thats kinda moot.)

The monitor is only a fraction of what's effecting latency.

I don't care.

Autumn_ 23/abr./2020 às 12:53

Escrito originalmente por Jamebonds1:
Escrito originalmente por Autumn:
Lots of things impact input lag, not just monitors.

User > Mouse/keyboard (Polling rate, processing speed, sensor or switches) > USB processing speed > OS processing inputs > Program processing inputs > GPU rendering frames (depends on when the data of movements was sent to the GPU in the form of scene info) > Monitors buffer setup > Monitors actual input latency. (And from there, to some degree, response time, but thats kinda moot.)

The monitor is only a fraction of what's effecting latency.
I don't care.

That's fine, but OP may care, I commented for his good, not yours.

Jamebonds1 23/abr./2020 às 13:01

Escrito originalmente por Autumn:
Escrito originalmente por Jamebonds1:
I don't care.
That's fine, but OP may care, I commented for his good, not yours.

Why are you replied to my comment then?

#10

Autumn_ 23/abr./2020 às 13:04

Escrito originalmente por Jamebonds1:
Escrito originalmente por Autumn:
That's fine, but OP may care, I commented for his good, not yours.
Why are you replied to my comment then?

Because there was misinformation in it. I corrected that misinformation for OPs sake.

#11

Jamebonds1 23/abr./2020 às 13:10

Escrito originalmente por Autumn:
Escrito originalmente por Jamebonds1:

Why are you replied to my comment then?
Because there was misinformation in it. I corrected that misinformation for OPs sake.

It is not misinformations. What I said is correct. So again, why are you even reply when im not going to agree with you?

#12

Autumn_ 23/abr./2020 às 13:15

Escrito originalmente por Jamebonds1:
Escrito originalmente por Autumn:
Because there was misinformation in it. I corrected that misinformation for OPs sake.
It is not misinformations. What I said is correct. So again, why are you even reply when im not going to agree with you?

Well, of course you're not going to agree with what I'm saying - you believe what you're posting is a fact. That's part of the problem.

Escrito originalmente por Jamebonds1:
Input lag can't be reduced.

This is misinformation. It can be reduced. And there are a number of methods that can reduce it or improve it.

#13

Jamebonds1 23/abr./2020 às 13:28

Escrito originalmente por Autumn:
Escrito originalmente por Jamebonds1:
It is not misinformations. What I said is correct. So again, why are you even reply when im not going to agree with you?
Well, of course you're not going to agree with what I'm saying - you believe what you're posting is a fact. That's part of the problem.

Escrito originalmente por Jamebonds1:
Input lag can't be reduced.
This is misinformation. It can be reduced. And there are a number of methods that can reduce it or improve it.

Nope. It can't be reduced, but it can be lower with correct settings. So I'm not wrong unless you get evidence to prove it. Or is there another reason why you are so focusing on me?

#14