OBS 27 improved display capture causes performance drops

BartInfinity

New Member
How to revert that
  • Improved Display Capture on Windows 10 1903+, which fixes the infamous "black screen" issue on laptops without requiring you to change the GPU that OBS is running on
Because since OBS 27:
  1. I can notice huge performance drop, like in game I have 144 fps, when capturing drops to about 80 but sometimes even to 40.
  2. Because of that "improved display capture" I can't anymore capture desktop old way, it means because I have two graphics cards:
    • GTX 1060: is dealing with all other aps
    • RTX 2070: that one were dealing with game and OBS itself
So whenever I wanted play a game I temporarily changed main screen connected to RTX and ran game and OBS then I switch back with main screen connected to GTX and since OBS were stared on same graphics card like game it was able to capture whole screen or games properly. With OBS 27 this trick seems not working anymore. I can't understand why OBS ran on RTX still have issues with capturing desktop. Seems like I would have to keep OBS inside screen of RTX whenever I move it to second screen it lost ability to capture 2nd screen the old way. The only working way is using that "improved display capture" however this drops FPS radically and I don't like it. How to turn off that "feature"? I can't normally use OBS anymore. If it will so drastically drop performance I would consider take out GTX and use only RTX, revert to old version or overall resign from using OBS on which I have teens of cool looking scenes prepared.

Shout to me if you need log.
 
new info:
  • whenever I ran OBS on screen/graphics card RTX and then change main screen to GTX whole OBS is freezing. OBS cant work anymore when changes main screen.
  • I used different software named Action:
    • works better I mean I have zero performance drop, my games keeps 140fps like I would never ran software to capture video.
    • works even when game is ran on separate graphics card and started on different main screen and software were started on different graphics card. Doesn't freeze whenever changes main screen.
Unfortunately in state OBS is useless for me.

I tested another software very similar to OBS named xsplit and had similar issues, for sure it had performance drop so I immediately stopped testing further.
 
Unless you need more than four display outputs the 1060 only hurts your performance and introduces complexity, I'd suggest removing it.
 
Unless you need more than four display outputs the 1060 only hurts your performance and introduces complexity, I'd suggest removing it.
Actually I had issues where 2nd screen were lags when I was using only RTX and game were opened. That's why I decided to take full power from RTX and use it only for games while GTX is handling with Windows and bunch other apps.

The issue I think is not actually with GRX & RTX, I'm kinda fully confused now.

I created new pack of scenes from scratch and...
  • OBS can now be ran on spare GTX and...
    • handles both screens without a crash:
      • when I tell OBS to capture main screen which is on GTX it is using old method so no yellow/orange border
      • but when I tell OBS to capture 2nd screen from RTX then it is using that new method so the yellow/orange border shows on that screen.
  • also OBS can be ran on RTX (so mine old way to deal with it) and...
    • handles also both screens without a crash
so now it have to be something in my scenes that is causing OBS to crash but I am not able to find it my self.

Generally I'm using a bunch of websites and also I'm using a lot of references, like on one scene are imported many other scenes. It is not crashing when I ran OBS on RTX and will not change my main screen back to GTX.

I'm sending a log file when OBS crashed at the end, there is no message at log why it could crashed, only info that I switched scene. Actually it is not crashing, my bad, it is freezing, so I have to forcefully kill it.

Please disregard my above messages.
 

Attachments

its hard for me to explain this, English is not my native, I recorded a video ( https://youtu.be/k85Pvg2Zyi8 ) and I didn't noticed when it took 40 minutes, but while recording and showing everything I'm sure now that the core of issue have to be in my scenes collection. I created new scenes collection and OBS works fine, at least is capturing RTX and GTX. I still noticed strange things like OBS were changing GPU in the background or task manager were not sure which GPU is OBS using because I setup OBS to always use GTX to encode. But overall on new scene collection there is no freeze when OBS is capturing current screen (old way) and separate screen from separate GPU (new way). Are there any limitations that came with 27 version? Like maybe the core of issue is in some browser, I have tons of them since I use a lot of code of own things. Any hint what could cause such issues? Like what source of types are using GPUs?

quick edit: the root issue only shows when OBS is running on GTX, whenever OBS is running on RTX there is no freeze issue, but somehow OBS is changing its GPU back to GTX when I change main screen - normally should stay on RTX like game app. I don't want to keep main screen on RTX because any app ran will use resources of RTX which I don't want.
 
Found the issue: it was at all not related with GPUs!
It was missing audio device that I removed from system couple of days ago and was still present on specific scene as audio source.

Wasn't your new and cool feature named "A new "Missing Files" dialog to warn you when some of your sources are missing their underlying files (images, media sources, etc.)" supposed to detect such sources?

Anyway OBS now works, it works even when running on GTX and capturing RTX (so using that new feature).
 
It was missing audio device that I removed from system couple of days ago and was still present on specific scene as audio source.
It was not missing audio, it was NVIDIA noise removal filter on Microphone.
That's explain why OBS were working fine on RTX while on GTX freezing. - so still related to GPU
 
22:36:20.045: Hardware GPU Scheduler: On

Try turning this off. In general HAGS causes more problems than the performance is worth.
 
Back
Top