Question / Help Battlefront High FPS, but low fps on stream

LIMIT

New Member
Only on this game does this happen. I get 60fps in game all the time, but in my stream it will dip to around 15 quite commonly. It is very frustrating as all of my other games stream flawlessly at 30fps. I tried lowering the gfx quality to low in game and it still does it.

My settings
bitrate - 2500
1080 downscaled to 720
fps 30
use CBR
Enable CBR padding
x264

I'm running an i7 2600k @ either 2.4 or 3.4ghz can't remember
GTX 770
8gb ram
everything streaming related is installed on my SSD along with my OS
Asus z77 motherboard
 

H4ndy

Forum Moderator
The game is just hogging your CPU and does not leave much room for encoding and the other way around. You can try using NVENC for that game instead of x264.
 

LIMIT

New Member
How do I post a log file?

Because I don't think its the CPU being hogged. Otherwise I would get the warning in my OBS GUI telling me the CPU Usage is high, I know for a fact that it can't be that b/c I play DayZ and other extremely intensive games that have no issues.
 

FerretBomb

Active Member
Go to the Help menu, Log Files, then Upload. Then just paste the link it gives you here.

Out of curiosity, are you monitoring your CPU load, temperatures and throttling while streaming+playing? Just to get that one out of the way... if it's running over-hot (dust buildup, thermal paste dry-out, mis-seated CPU cooler) it could throttle itself or otherwise behave badly. I'm not saying that's what's doing it (need the log to see what's happening) but it could indeed be one reason, if you aren't keeping an eye on system health.
 

FerretBomb

Active Member
20:20:14: Total frames encoded: 4664, total frames duplicated: 555 (11.90%)
20:20:14: Total frames rendered: 4364, number of late frames: 257 (5.89%) (it's okay for some frames to be late)

Well, there's the issue. Tons of dupes and lates, almost 20%.
Problem is, there's nothing indicating what's causing them. Video thread is under 11ms (60fps requires sub-16ms, so you're fine at 30), and CPU profiler is under 2ms.

There's a good possibility that this is just the Windows 10 game capture performance bug (welcome to early-adoption, and the teething problems associated). Supposedly there's a patch coming soon to try and fix it, When It's Done(tm). Not sure if going borderless fullscreen and window capturing would fix the issue, or if monitor capture would work in the meantime.

Alternately, some of the CLR browser/overlay stuff could be causing issues. Could you create a new scene with JUST a game capture of Battlefront and test-stream it? Never switch to a scene with any of the CLR browser or overlay stuff (that will avoid having it load; global sources only load the first time they're used in a scene). Run it for ~5 minutes. Then close OBS, reopen it, and upload latest logfile (have to close OBS for it to close out the current logfile). Can create a throwaway account for testing purposes (what I do). Not sure if this would do it, but ruling out vectors. Possible a slow browser thread could be throwing a monkey wrench in.

I don't think this will do anything and probably isn't necessary, but you might also bump up your scene buffering time to 700ms. It's the new default.

If I had to put money on, I'd blame Win10 every time though.
 

LIMIT

New Member
I disabled my CLR browser and it fixed the issue. So now how do I go about changing settings so that I can keep the overlay on, or do I just need to have it turned off for this specific game? I would love for it to work as it has a lot to do with the visuals of my stream, but if I have no other choice then, lame stream without gfx and stuff. Thank you for suggesting turning the CLR off, I honestly didn't think it would cause an issue. Now does that mean the CLR was using too much CPU or wtf? So confused.
 

FerretBomb

Active Member
Ah, thanks Osiris. I thought it was GC in general under W10; I've been avoiding it entirely with all of the issues I've seen here, as well as at the day job.

Limit, I'd expect strexm.tv to be the problem. There have been a few of these 'cloud based' overlay sites, and they never really work out well as you're left at the mercy of a remote server; if it starts having a problem for any reason (which is probably what's happened), your stream can die out of nowhere, then start working perfectly again just as quick, entirely inexplicably. Remote access times, throughput, hardware failure... remember a prior iteration that ended up with a few streamers showing 'the site is not available, click here to retry for a live version' splash when it just died out of nowhere.

Set up your art assets locally. Keep them under your own control as much as possible... it's why I haven't moved to TwitchAlerts or the Nightdev chat plugin, as tempting as they are, and as well as they work compared to SubAlert/Chatty colorkey. You don't want someone else's server bombing out to impact your stream. After all, you already have to worry about that enough with the Twitch ingests. Kappa
 
Top