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
That sounds like a terrible idea. XAudio, the NVIDIA driver and most video capture software requires MMCS. You could turn the responsiveness target down to 10%, but disabling it is going to make a lot of things not work.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile
Added this DWORD:
“SystemResponsiveness” = 0x00000000
Though I wouldn't put too much stock in these tweaks without a lot of testing but you haven't disabled MMCS. :)
(From: https://www.reddit.com/r/killerinstinct/comments/4fcdhy/an_excellent_guide_to_optimizing_your_windows_10/ Which yeah I would be a bit wary of some of these but eh nothing wrong with trying as long as you remember what you tweaked and can set it back if needed.)
EDIT: Ah that's a bit better, there's the doc for it.
https://docs.microsoft.com/en-us/windows/desktop/procthread/multimedia-class-scheduler-service
EDIT: I was too late ha ha, already covered in the post below this one. :D
If that's the only thing you've changed, and you're using Windows 10, then MCSS should still be available (you can use the Threads widget of Special K to confirm it).
Source: https://docs.microsoft.com/en-us/windows/desktop/procthread/multimedia-class-scheduler-service
I'm running everything on max except Volumetric Clouds at High, Fog at Medium and Anti-Aliasing at Medium. 1440p. Capped at 60 fps because I'm playing on my 4k TV. The frame limiter in SK seems pretty good when it comes to framepacing/frametimes.
I7 4790k @ 4.6ghz
16gb of 1600mhz DDR3 9-9-9-24-1T
1080 GTX Strix slightly overclocked core and memory.
EVO 850
It measures the health, so to speak, of the last 120 frames.
When the variation between frametimes becomes too large, the limiter disengages and allows the CPU to render-ahead of the GPU until the event that caused stuttering eventually works itself out. Then the limiter re-engages and the end-result of all this is no perceived stutter.
You can stare at the frametime graph if you want and notice that something weird happened, but my framerate limiter isn't there for the purpose of limiting your framerate unconditionally. It's there to produce smooth, stutter free rendering.
Ah I see. That make sense. I don't feel any stuttering when it happens, I just see shit going on on the frametime graph. I can't stand the tearing without vsync so I have to keep it enabled. Using a framelimiter with vsync enabled is kinda useless I guess then?
One more question. Under Advanced in the framelimiter, there is a option called "Use Multimedia Task Scheduling" 0-4. What does it do and what should it be set on? Is it related to "Maximum pre-rendered frames" in the Nvidia control panel?
Also, that setting is apparently not what you think it is :)
The slider is "When to apply framerate limiting." It's there in case some other software is drawing an overlay after Special K is.
It's not a saved setting since it's experimental and it defaults to 4 (immediately before my UI is drawn)