Question / Help Microstutter while streaming 32 bit games

[DrowsyGenie]

Hello, ever since I got the Creator's Update rammed down my throat with the recent final push by Microsoft, I have been experiencing difficulties streaming games like CS:GO. I'm pretty sure it is limited to either just CS or 32 bit games in general as I did a 30 min test stream of PUBG with no issues.

Basically, the issue is that I have been experiencing weird micro-stutter issues almost as if my games refresh rate is locked. My fps will appear to have no issues staying at a consistent 300 frames per second but it looks to be lagging at a consistent rate as soon as I hit start streaming.

I have tried updating to the latest build as well as reverting back to 18.0.2 which is when the patch notes say that the issue with 32 bit was fixed. I have also tried running as administrator and disabling full screen optimizations in the OBS properties. As well as enabling the new networking code.

Stream Settings:

Bitrate: 2500
Resolution : 1280x720 Output @ 30 fps
Encoder: Software

Game Resolution is 1360x1024 stretched @ 144fps

 

[Fenrir]

First step is to verify that the Windows Game Mode is disabled, as well as the Game DVR.

Then, if that doesn't fix the issue, please provide a log.

https://obsproject.com/forum/threads/please-post-a-log-with-your-issue-heres-how.23074/

 

[DrowsyGenie]

Alright checked that and it's still not working properly.

https://gist.github.com/c6acc47519327994724fc42e8988ce9f

 

[Fenrir]

That log is from the old version of OBS. You should update back to the latest.

Once you've updated, try removing the display capture source from your main scene. You shouldn't mix display capture and game capture in the same scenes.

If you are running CS:GO without any kind of framerate limiter, it will max out your GPU and leave nothing left for OBS. 300fps is too high, try capping it at something reasonable.

 

[DrowsyGenie]

I'll try the latest update.. but before the creators update everything worked fine and I would lose no frames at all in game. CS:GO mostly uses the CPU as well, I don't think it will use 6gb of VRAM.

 

[Harold]

VRAM isn't the only part that gets wasted when you don't have a sane framerate limit

 

[Fenrir]

It's not about VRAM, it's about overall GPU load. Running with uncapped frame rate means CS:GO will use all available GPU resources to run at the highest framerate it can, leaving nothing left for OBS to function properly.

 

[DrowsyGenie]

Well Windows did an update last night and it seems to be running better now without capping frames, I did remove that Display capture tho. I'm going to try with ESEA running and see if the issue comes back.