Question / Help Newly developed FPS issues

yardgnome

yardgnome

New Member
Hello, I've been streaming with OBS regularly since the end of October 2017. In the past two or so weeks I have started experiencing a new issue where no matter the game played, after an extended period I see my stream FPS begin to drop. I stream at 720p 60fps and after extended periods the problem can get as bad as sub-20fps. The only variables in my setup that I can think of is that I did install Streamlabs OBS to test out and also updated core OBS Studio around the same period. All of my settings, personal, internet or otherwise are (to my knowledge) untouched. I also try and keep an active watch on my CPU usage and it seems relatively untouched/unaffected, I notice these issues even with my CPU usage is as low as 3-3.5%. I'm also experiencing the occasional crash when trying to switch scene collections but I consider this rather minor in comparison to the drastic impact to my FPS/stream quality.

Below I have attached three logs, one during a match of Fortnite which ended in OBS crashing after trying to switch games, the stated crash log, and the last being a successfully completed stream of PUBG that lasted roughly two hours and found my FPS output at the sub-20 fps I mentioned earlier. I've also included a link to the archive of that PUBG stream here on Twitch to show the effect I'm describing. Before these issues began I almost never experienced any sort of issues with my streaming. Potentially worth noting is my CPU is successfully overclocked to 4.0ghz, something I don't believe is stated correctly in the logs.

Thank you for your time and consideration reading this!

Fortnite Log:
https://gist.github.com/anonymous/a706cc2130de93d70b680268108a953a

PUBG Log:
https://gist.github.com/anonymous/65ea93f603e9c0a59191bc49ac25b779

PUBG Stream Archive:
https://www.twitch.tv/videos/227145454
 

Attachments

Last edited:
Only the 2nd log has the summary of encoding stats.
From that we see:
[AMF] <Id: 5> No output Packet, encoder is overloaded!
[AMF] <Id: 5> No output Packet, encoder is overloaded!
[AMF] <Id: 5> No output Packet, encoder is overloaded!
[AMF] <Id: 5> No output Packet, encoder is overloaded!
Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 101203 (20.1%)

Have you had any updates such as GPU drivers or anything change related to what is being powered by your GPU? This can be as simple as I have a new higher Hz monitor. Or, I added a 2nd monitor and have OBS preview window running on a 60hz monitor while I try to game/stream from a 120+hz monitor.

It looks entirely GPU based to me, but I don't have direct experience with the AMD cards so this is the first entries like this I'm decoding trying to help out.

--hth
Kilspent
 
I have updated my GPU drivers while this has been going on but the problem began before I did that and has not been resolved by doing so. Otherwise nothing has changed in my setup at all, I use two monitors, both at 60hz, but I've been using those the entire time and as I mentioned this issue just recently began.
 
"I'm also experiencing the occasional crash when trying to switch scene collections"

Your crash log is showing the stack state when you changed Scene Collections.

Thread 31F0 (Crashed)
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
0000001DC43A9868 00007FFA5C517590 0000014E7BBA76E8 0000014E0AAFBEA0 0000014E0AF90A80 0000014E0AAFC4E0 obs.dll!getsignal+0x20
0000001DC43A9870 00007FFA5C517CB9 0000014E7BAF8120 0000014E7BAF8120 0000014E0AAFC4E0 0000014E7C0B7CC0 obs.dll!signal_handler_disconnect+0x49
0000001DC43A98A0 00007FFA63BAA5AF 0000014E0AAFBEA0 0000014E7C0B7CC0 0000000000000006 0000014E72F5B0A0 obs-websocket.dll!0x7ffa63baa5af
0000001DC43A98D0 00007FFA63BA9A9D 0000000000000006 0000000000000008 0000014E71D994A0 0000000000000003 obs-websocket.dll!0x7ffa63ba9a9d
0000001DC43A9900 00007FF65BD2A680 000000000000012C 0000000000000000 0000001DC43A9A30 00007FFA5C5019B0 obs64.exe!OBSStudioAPI::on_event+0x60
0000001DC43A9930 00007FF65BD42DC6 0000001DC43A9D10 0000001DC43A9D10 0000001DC43A9D00 0000014E00000008 obs64.exe!OBSBasic::Load+0xbe6
0000001DC43A9CF0 00007FF65BDF3974 0000014E6FCAD1B0 000000006FA39528 0000000000000004 0000014E7C3DDDD0 obs64.exe!OBSBasic::ChangeSceneCollection+0x184

Looking at the stack trace, this is invoking a third party plugin DLL to generate a websocket call through obs-socket.dll.

Refer to:
https://obsproject.com/forum/resour...e-control-of-obs-studio-made-easy.466/updates

it is known to have a bug when switching scene collections and an update was made January 28, 2018.

Do you recall installing this plugin?
 
I do! I use it as a means to change my active scene/overlays from my laptop. Thank you for that, I was unaware of the bug as well as the update! I will look into applying this fix. Now if I get my FPS issues worked out I'll be back in great shape!
 
You must log in or register to reply here.
Back
Top