Right now i try to stream LoL at the highest settings possible.
But i hit the CPU limit with 1080p 60FPS faster preset, with nothing more than my stream running in the background (its a +1 viewer + i can check it live), LoL, TS3 and some other background stuff, mostly windows internal crap and drivers.
LoL eats max 19% of the CPU, Chrome can jump up to 20% while watching something heavy in the flash player (damn twitch move dat thing called HTML5 finally in).
OBS is hitting the 60% peak, leading to FPS drops ingame. But i dont get the "high CPU usage" warning and on stream everything looks fine, i can just see the FPS ingame dropping all over the place, i see double digits pretty often and thats far away from being smooth.
So i had to roll back to veryfast, but even this is producing up to 30% load with a simple game like LoL.
Stuff that is harder to encode (something like Rust) will produce even more CPU-load, pushing OBS up into the 50% load zone while using the veryfast preset.
This is how it looks like with veryfast:
https://gist.github.com/anonymous/72f0e28071e7c671f29f
What the log doesnt tell you:
CPU is overclocked to 4,3GHz, properly cooled and primestable.
GPU is also overclocked by ~200Mhz on both VRAM and GPU itself.
16GB of DDR4 are used, with slight OC (2400) and sharp timings around CL12.
SSD is used for every programm running, recording is placed on a fast HDD.
My problem is not that i cant stream, my problem is just the overall too high CPU usage compared to what i had under Windows 8.1. And i need a solution for this, specially because some games actually use more CPU than LoL and i cant stream them with 1080p 60FPS anymore without crippling the preset. Going back to 8.1 is an option, but i like windows 10 and i need stability, decent performance and everything else just working.
P.S. i also get a ton of errors using the CLR browser/CLR host plugin and Ubiquitous2 Chat with the modified version of this plugin. Cant replace them so OBS MP is not an option (just for testing - i have it). And i get some memory leak errors in the log O_o
But i hit the CPU limit with 1080p 60FPS faster preset, with nothing more than my stream running in the background (its a +1 viewer + i can check it live), LoL, TS3 and some other background stuff, mostly windows internal crap and drivers.
LoL eats max 19% of the CPU, Chrome can jump up to 20% while watching something heavy in the flash player (damn twitch move dat thing called HTML5 finally in).
OBS is hitting the 60% peak, leading to FPS drops ingame. But i dont get the "high CPU usage" warning and on stream everything looks fine, i can just see the FPS ingame dropping all over the place, i see double digits pretty often and thats far away from being smooth.
So i had to roll back to veryfast, but even this is producing up to 30% load with a simple game like LoL.
Stuff that is harder to encode (something like Rust) will produce even more CPU-load, pushing OBS up into the 50% load zone while using the veryfast preset.
This is how it looks like with veryfast:
https://gist.github.com/anonymous/72f0e28071e7c671f29f
What the log doesnt tell you:
CPU is overclocked to 4,3GHz, properly cooled and primestable.
GPU is also overclocked by ~200Mhz on both VRAM and GPU itself.
16GB of DDR4 are used, with slight OC (2400) and sharp timings around CL12.
SSD is used for every programm running, recording is placed on a fast HDD.
My problem is not that i cant stream, my problem is just the overall too high CPU usage compared to what i had under Windows 8.1. And i need a solution for this, specially because some games actually use more CPU than LoL and i cant stream them with 1080p 60FPS anymore without crippling the preset. Going back to 8.1 is an option, but i like windows 10 and i need stability, decent performance and everything else just working.
P.S. i also get a ton of errors using the CLR browser/CLR host plugin and Ubiquitous2 Chat with the modified version of this plugin. Cant replace them so OBS MP is not an option (just for testing - i have it). And i get some memory leak errors in the log O_o