Question / Help 20-30 fps loss as soon as I open OBS and start streaming

Jh4nTy

New Member
Hello. I've recently upgrade from my i5-4690k to a Ryzen 7 1700 in hope of having better performance while streaming and gaming at the same time but I'm still having this annoying issues.

My current build:

• CPU: AMD Ryzen 7 1700 @ 3.7GHz
• GPU: Gigabyte GeForce GTX 1060 WindForce OC 6GB
• RAM: G.Skill Trident Z RGB 16GB (2x8) DDR4 3000MHz
• Motherboard: ASUS ROG Strix B350 F-Gaming
• OS: Windows 10 Pro
• HDD: 1TB
• SSD: TOSHIBA Q300 240GB

I get pretty much 20-30 fps loss in-game while streaming, RAM and CPU usage barely go over 60% and I don't know what the hell to do anymore. I've spent quite some money on this upgrade hoping for a better performance but that's not really happening.

Games I've tested:

PUBG: 1680x1050, Draw Dist Ultra, Post-Processing Ultra, Anti-Alias Ultra, everything else on very low. While just playing In Pochinki I was getting between 70-80fps. As soon as I turn on OBS and start streaming, I get as low as 45 fps in some areas average being 55fps. In Pochinki, remember.

GTA V Online: 1080p, Very High (almost everything) While just playing, average of 85-90 fps. With OBS opened and streaming getting as low as 55fps, average being in 65fps.

CS:GO: Mixed graphics settings, 1680x1050. While just playing 250-300fps. OBS and streaming average 200, getting spikes to 170 sometimes

Am I doing something wrong? Is it normal to lose this amount of fps while streaming?

Here are my OBS settings and Speed Test results:

obs1.png

obs2.png
 
Or limit your fps, to avoid the bottleneck.

Playing without an FPS limit is fine, if you don't use streaming/recording software.
With OBS, you want to cap your fps, so that the GPU will not become a bottleneck (you need GPU load to stay below 90%).
CPU bottleneck is hard to see, as there are so many cores and SMT threads that windows is using to push around the load. When a Game with 4 thread utilization is CPU-bottlenecked, you might see not one core/thread at high load and still the engine will be running into a CPU bottleneck.

Playing without vsync/fps limit and using the same PC for streaming is as bad as using high refreshrate monitor (for example 144Hz) in combination with a 60Hz monitor and trying to watch OBS preview or other GPU accelerated stuff on the 60Hz monitor, while playing on the 144Hz monitor.
 
Last edited:
I do use a 144hz monitor to play and a 60hz with twitch dashboard opened and streamlabs app to check followers.
 
Disconnecting the 60hz or having it connected makes no difference. GPU loads never go higher than 75%.
 
Makes absolutely no sense...you have a 144Hz monitor and get 85-90fps without OBS (so you definitely are not limiting your fps to 60..maybe you just use Gsync to limit fps to 144max).
So getting 85-90fps without fps limit (or max 144fps limit) you are already have a bottleneck there.
If the GPU is not utilized ~100% than the bottleneck in this scenario is your CPU (which is possible, as PUBG can not make use of your 16 threads and therefore the lower clockspeeds of Ryzen are limiting your max fps here).

When you start OBS, the CPU load should remain the same, while GPU load will increase 6-10%.
When you record/stream with OBS, you will get some CPU load, especially when the game has fast movements. 720p 60fps at faster setting is already pretty high load, but the R7 CPU can handle that.
If your game was already running with a CPU bottleneck, the ingame FPS will dip down, while you stream/record.

By the way: I would disable the "film" tune in your x264 presets. Just set it back to "none".

Where is your log file of a sample recording/stream?
I bet there are some nasty browser_sources in there, that could put some load on your CPU. Also make sure, not to use window_capture, game_capture and/or ,monitor_capture together.

So my suggestion (as I see no log file, that might help to pinpoint the problem) would be:
Create a new scene collection, and create one scene in there.
Insert just the game_capture source and test again (this way you eliminate the possibility of browser_sources or webcam dirvers to tank cpu performance).
 
Last edited:
Back
Top