Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For example, i now play "the division" and, my pc can do more than 60fps but, i see both cpu and gpu used at very high levels so, i prefer to limit to 50fps.I really dont see the difference in response time and everything runs much smoother and cool
Just personal preference, if you have a powerhouse (or dont care about burning unneccessary cpu and gpu cycles) or is a very recent game i dont really see reasons to limit FPS.
So i would not lock the FPS.
if you were to instead try and push it higher than that, you would be taking damage twice as fast as you were meant to, causing a level of difficulty the game was not meant to support..
you also may want to match it with your monitors refresh rate for a more smooth experience..
remember, higher numbers do not always mean "better"
Theres a counter question to be asked: Whats the point of havimg way more FPS than the monitor can display? Except driving up your power bill by having the GPU workimg in vain, that is. And ive no idea who the hell would artificially blow up their power bill (and there are still better ways to do that).
is best for your hardware and related things
The 'other' reason is the bad one that 99% of people cite.
The main 'fake' reason is that one time some dumb game reviewer claimed that "Diablo2 killed my laptop". Basically Diablo2's main menu screen was uncapped for FPS and so basically just rendered the main menu at like 500 fps.
This generated a ton of heat which, 'supposedly', fried the reviewers laptop
Note this led to a flurry of basically dumb people insisting "Diablo killed my computer". To which Blizzard, despite this being pure nonsense, was forced to make a placebo fps limiter on the game.
So here's the thing. Heat is not a game problem. Its a COOLING PROBLEM.
Diablo did not 'kill' the reviews laptop
THeir laptops insufficient cooling killed it.
Your GPU and CPU are designed to run 100% 24 hours a day 7 days a week for YEARS. How do you think bitcoin miner work? Do you think they're 'downclocking' those 1080TIs? NO. Do you think IBM's Watson goes "holy these Jepoardy questsions are too hard! We need to downclock the CPU" NO. They're running full bore 100% all day long. That's because they are sufficiently cooled to address the heat. The GPU/CPU has no problem running at 100% for years. As long as you have the proper cooling its not an issue. Running your CPU and GPU at 100% does not damage them. Insufficient cooling damages them. Not the act of running at 100%. This is like saying you can only drive your Ferrari at 10mph because it will overheat, but ignore the coolant line that was sliced in hafl, then blaming the engine for beign defective.
FPS limiters are fix for the wrong problem. But people don't understand this and thus insist that the game fix the fact that their cooling fans are filled with cat hair and they put a space heater behind their computers and enclose them in air tight closets at 150F.
If you speak about dumb, you should call these games dumb.
It is not dumb to expect something not running insane would be enough to display, you know...... a menu.
With your claim, i would be stupid by reducing fps to reasonable levels.
Its not that i miss out anything, while likely having a positive effect on wearing and cost.
It doesnt matter if it does 1000fps
This does not harm your CPU or GPU thus having it render at that speed is fine. Your GPU and CPU are designed to run at 100%. If that means 1000fps then who cares. Its not 'dumb' because the main menu is rendering very fast.
Its dumb because there's no actual reason to reduce it to reasonable levels. 1000fps does no more harm to your CPU/GPU than 60fps/120fps/etc. If you want to reduce screen tearing and thus want your fps to sync with your monitor, sure ok that's fine. But the most common 'reason' for reducing your FPS is to avoid 'damage' to your components. And running at 1000fps does not damage anything thus making the necessity to reduce your FPS for anythign beyond screen tearing, based on a boogey man that doesn't exist.
Game limiting FPS limiters are going to look pretty silly soon as well. People are 'guessing' what limits to put in. Some put arbitary upper limts like 100fps. because no one thought 144hz monitors would exists. They do now. They're just placebo for ignorance of the real problem.
Its rational to remove these events.
In a good software you would call that optimization. Thats what i think of it.