Bug Report OBS+BF4 alt-tab causes the stream/recording to glitch/stutter

Spazmo

New Member
No matter the version of OBS, whenever I use alt-tab in Battlefield 4 the stream or recording starts to stutter. It looks like this: https://youtu.be/PjqV4MR4xFs?t=40m49s . A friend of mine (who recorded this video) experiences the exact same issue. With Xsplit I personally haven't had this problem, so I think it must be OBS. I tried all three encoders with different settings and a variety of different in-game settings, but nothing helped even the slightest bit.

https://gist.github.com/anonymous/b3360bb43c73b928f60d
 

R1CH

Forum Admin
Developer
Usually games will lower their frame rate when they aren't active. It's generally an option in most games.
 

Spazmo

New Member
So what you're saying is this stuttering is the expected behavior of OBS:



PS: I've never heard of such a "feature" (if you can call it like that). It's certainly not an option in Battlefield 4 (or any other Battlefield title). But even if it was, why would lowering the FPS temporarily cause this stuttering issue? And why doesn't switching back into the game fix the stuttering then? If it really was the game and not OBS, shouldn't I have the same issue using xsplit? Sorry, but your answer makes no sense to me. Did you even take a look at the video I linked in the first post? If not, don't bother, I've just recorded this short clip, so it won't waste anybody's time that much. If you take a look at it, you'll surely notice the webcam capture is smooth. So it can't be the encoder, but the part of OBS that captures the game play footage, right?
 
Last edited:

Spazmo

New Member
Have you tried with just a game capture source and using x264 instead of NVENC?
Yes, I have tried with just a game capture source and using x264 instead of NVENC.

As previously mentioned, I doubt it's the encoder or any setting concerning the encoder, since the webcam capture (or anything but the game capture) is buttery smooth. I believe it might be another quirk of the game itself that the guys from xsplit managed to find a workaround for.
 
Last edited:
Top