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
This "feature" was implemented when QL standalone was first released, with the goal of making the game not waste CPU resources when idle (i.e. if you just leave the game running with the match browser open). Unfortunately it also causes the CPU to go into lower power modes while you're actually playing the game.
Set com_idleSleep to "0" and forget about this annoying "feature".
agent smith : it's not just for the "browser mode". QL spends most of its time idling/sleeping on modern hardware in pretty much every situation.
I honestly don't know anyone who gets solid/stable fps with idleSleep enabled. All of the competitive players I know have idleSleep off and their PC's power settings set to "performance" rather than "balanced". Most people I know are on Intel + Nvidia. I'm curious to know what your setup is, because I do know there are some people who don't have a problem with idleSleep.
All I can say is... All of the people I regularly talk to experience unstable fps with idleSleep enabled. I certainly do on my system. It was the case when I had a gtx770, two 970s in SLI, and it remains an issue with my single 970 I'm now using. But ultimately this is just another testament to the fact that there is all kinds of buggy ♥♥♥♥ with this game that can't be explained.
As for the 'planet' or whatever, I assume this is some reference to co2. I mean, I heard the devs say something to that effect before, but I couldn't tell if they were serious. Where I live very little power comes from coal anyway. Either way, the planet will be just fine, even if a few coastal cities end up under water. =]
This is the most sound advice to be followed. I asked devs about it and they told me to leave it at default UNLESS it's causing problems. Turning it off will generate unnecessary heat from the CPU.
LOL. Because they won't acknowledge that on a large portion of PCs it causes dropped frames. It means there are a ton of noobs out there who don't even know how to check the stability of their frame rate, warping unnecessarily as a result of this 'feature'.
thanks internet!
Weird statement FS.
com_idlesleep 1 has caused slow performance on every computer I've owned. From the 4770k all the way up to the 12700k, also on Ryzen 2700X all the way to 5800X cpus.
Whatever it was originally made for, it causes issues now.
com_idlesleep "1" - avg 245fps, with drops down to 211fps.
com_idlesleep "0" - avg 250fps, with drops down to 248fps.
This is on a 12700k with running at 5.2Ghz.