Something wrong with the engine?
dePARA
Join Date: 2011-04-29 Member: 96321Members, Squad Five Blue
I was tired of locking the fps everytime over console and did this via nvidiainspector on driver level.
After that i noticed something strange:
No matter what value i locked the fps, the game had always 7 fps more.
A test with crysis @ locked 30 fps via nvidiainspector had 30 fps as result like intended.
So this brought me to the question:
Is there something wrong with the engine?
An no, im not talking about low fps, stutter, etc here.
After that i noticed something strange:
No matter what value i locked the fps, the game had always 7 fps more.
A test with crysis @ locked 30 fps via nvidiainspector had 30 fps as result like intended.
So this brought me to the question:
Is there something wrong with the engine?
An no, im not talking about low fps, stutter, etc here.
Comments
There probably is but I don't see it getting fixed
Especially because other FPS limiters i've tried (like fraps) do not have this symptom
So the card is limiting and not a software (Iike fraps or NS2).
If i lock it ingame via console i have the locked fps also.
Its just strange that other games didnt have this symptom i descibed.
3rd party software, however - Including drivers - that limit FPS ... incur input delays.
Unlike game engine implemented FPS limiting which has zero input delay.
It's probably nvidia inspector being odd, but either way stick to using maxfps , it will be fixed soon.
Why would you want to set a max FPS for regular gameplay? What would change from a players perspective? Input latency? Hit registration?
Of course if you're not using gsync or freesync (in which case you wouldn't need to limit fps) Then there's going to be downsides like input delay or screen tearing, or large drops in fps (if you can't hold 60 fps with vsync it will drop to 30)
So it's not worth it Imo, instead just use either of those technologies.