Huge fps loss when streaming

ardranf10

New Member
Hello,can anyone help me,i try to stream cs2 but fps loss is too much,in lobby,when IM not streaming i could get 115 fps,but when Im start streaming my fps down to 60-50 fps,IM using ryzen 5 GTX 1650 laptop,and all the obs setting is default
 

qhobbes

Active Member
 

qhobbes

Active Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. It's an experimental feature and we recommend disabling it via this screen these instructions.
2. In Windows, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
3. You are running an old version of OBS Studio (30.1.0). Please update to version 30.1.2 or newer by going to Help -> Check for updates in OBS or by downloading the latest installer from the downloads page and running it.
4. OBS is not running as Administrator. This can lead to OBS not being able to Game Capture certain games. If you are not running into issues, you can ignore this, but it looks like you are since you're using Display Capture to capture CS2. To run OBS as Administrator, right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok. Then open OBS, remove Display Capture and add the Game Capture source. If you can't get it to work with Game Capture, then try Window Capture (remove the Game Capture source if doing this).
5. In the Output Settings, set Multipass Mode to Single Pass and disable Psycho Visual Tuning. Both of those use additional GPU.

If still having issues, post new log.
 

ardranf10

New Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. It's an experimental feature and we recommend disabling it via this screen these instructions.
2. In Windows, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
3. You are running an old version of OBS Studio (30.1.0). Please update to version 30.1.2 or newer by going to Help -> Check for updates in OBS or by downloading the latest installer from the downloads page and running it.
4. OBS is not running as Administrator. This can lead to OBS not being able to Game Capture certain games. If you are not running into issues, you can ignore this, but it looks like you are since you're using Display Capture to capture CS2. To run OBS as Administrator, right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok. Then open OBS, remove Display Capture and add the Game Capture source. If you can't get it to work with Game Capture, then try Window Capture (remove the Game Capture source if doing this).
5. In the Output Settings, set Multipass Mode to Single Pass and disable Psycho Visual Tuning. Both of those use additional GPU.

If still having issues, post new log.
Thank you,i forgot to run obs as administrator, and using game capture is what fixed my problem,thank you for your reply
 

Lawrence_SoCal

Active Member
@qhobbes - love your succinct recommendations.
Question though on running as Administrator [something fortunately I don't have/need to do].
When running OBS Studio as Administrator, does that then usually involve an alternate OS User Profile, meaning Scene Collection, Profile, etc would all need to be recreated (or backed up/ imported)?
Or is this a case of assuming Windows Home (vs Pro) version, with single user account, default Administrator account disabled?

If running as Administrator often does confuse users unfamiliar with OS User Profile related implications, I'm curious if a FAQ is warranted (and Yes, I'd be willing to start a draft one, if need be)
 

qhobbes

Active Member
@Lawrence_SoCal I opened OBS as Admin and it was on Profile: 720P 59.94 FPS x264 , Scene collection: test5
I closed OBS and opened it again not as Admin. It opened to same Profile and Scene collection. I then changed the Profile to: 720 and Scene collection to: test and closed OBS. I re-opened OBS as Admin and it was Profile: 720 and Scene collection: test

The same profiles and scene collections were available regardless of running as Admin.
I am using Windows 10 Pro and the user I log in with is Administrator type (but it is the only administrator account).
 

Lawrence_SoCal

Active Member
I am using Windows 10 Pro and the user I log in with is Administrator type (but it is the only administrator account).
that explains
The same profiles and scene collections were available regardless of running as Admin.
You are using same user Account/Profile regardless... but that can NOT be assumed

I believe that behavior is true ONLY in the circumstance you describe ie. already logged into only active (not disabled) local Administrator account
something that tends to be a REALLY bad idea from a security perspective, for the average user... convenient, just insecure for almost all except those that know exactly why I'm saying this, and how to mitigate associated risks [which is usually more hassle than its worth, imo]

I'm not sure with latest Win11, but as it really is more of just an updated/re-skinned Win10, I'm not aware of a basic User Profile change in behavior ... but granted, I haven't been paying as much attention to Win11.
_IF_ an end-user follows standard OS best practice (non-default OS behavior on initial setup) and creates a separate non-Admin User Profile, and uses that User Account/Profile for (almost) all normal activity including OBS Studio, then running as Admin I believe will invoke an alternate WinNT user profile (the default local Administrator account) and those OBS Studio settings (Global, Scene Collection, etc) all stored in User Profile path, so not shared.

There are (were) ways to share a Profile Path between accounts, but MS articles/guidance on that have been removed (many years ago) and need some expertise to properly configure, and I could foresee issues/complications with things like OneDrive or similar ... so not something I'd advise unless someone has ready access to appropriate OS support
 

bobsterr

New Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. It's an experimental feature and we recommend disabling it via this screen these instructions.
2. In Windows, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
3. You are running an old version of OBS Studio (30.1.0). Please update to version 30.1.2 or newer by going to Help -> Check for updates in OBS or by downloading the latest installer from the downloads page and running it.
4. OBS is not running as Administrator. This can lead to OBS not being able to Game Capture certain games. If you are not running into issues, you can ignore this, but it looks like you are since you're using Display Capture to capture CS2. To run OBS as Administrator, right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok. Then open OBS, remove Display Capture and add the Game Capture source. If you can't get it to work with Game Capture, then try Window Capture (remove the Game Capture source if doing this).
5. In the Output Settings, set Multipass Mode to Single Pass and disable Psycho Visual Tuning. Both of those use additional GPU.

If still having issues, post new log.
Hello! I just read on nVidia website an article from sept. GPU scheduling is recommended to be On. Is this a fix now ? Did you guys test it out for a much longer time
 

PaiSand

Active Member
Hello! I just read on nVidia website an article from sept. GPU scheduling is recommended to be On. Is this a fix now ? Did you guys test it out for a much longer time
If you're going to only play a game, yes, it's recommended to have it on.
If you at the same time stream / record and have issues related to it, turn it off.
 
Top