davethejackal
Member
Apparently they updated to a "new and improved" browser engine with 27.2. https://obsproject.com/blog/the-tale-of-a-legendary-hotfix
Devs? Why u do this? Hotfix has not fixed it
Is Browser hardware acceleration broken in 27.2?
- Thread starter davethejackal
- Start date
Devs? Why u do this? Hotfix has not fixed it
Tyr808
Member
No, I do tick the box there to run as Admin, but not for an older version of windows or anything else. I've tried with HAGS on or off, frame limiters on or off, gysnc on or off. I'm absolutely down to test any suggestions though, but even on very modern hardware it seems that without fail hardware accel on 27.2 causes browser sources to stutter and in the case of a youtube video player, completely lock up, goes away with HW accel off. In this working state (27.2 + HW acell: off), I can downgrade to 27.1.3 and the same configuration that previously had issues works perfectly with HW accel.
For clarity, I'm just focusing on sharing as many details as I can here for the sake of identifying the problem. I don't want to sound like I'm being ungrateful that I have OBS in the first place :)
davethejackal
Member
It's still broken in 28.0.3 ...
Tyr808
Member
Still experiencing the same issues on the v29 beta as well. I feel like I'm going crazy getting less performance on more powerful hardware and with a more optimal and lightweight scene collection and composition in OBS. I just get the WEIRDEST performance issues with hardware acceleration enabled in OBS, but if I turn that off it it's just an unnecessarily heavy load on the CPU that causes other issues. I had done a clean install of OBS and reconfigured my scenes with the minimal amount of things and a better use of sources and nested scenes. I've also tried limiting browser sources to 30fps and below.
Here is a clip of my camera source responding to the issue that seems to be connected to hardware accelerated browser sources. This is also happening on the current stable release and without any plugins either, but I was currently testing the v29 beta to see if having more optimal nvenc settings with StreamFX's beta helped anything.
Here's the log of that stream: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/yStOzBCshtSUmmd-#logURL
I've recently turned HAGS back on because it was allegedly recommended, but I see the log analyzer is recommending I don't use it. I'll try that yet again for good measure but this has been thoroughly toggled on and off many a time. I saw that my stream elements overlay source is constantly complaining about permissions and such, it's just for alerts and some text on screen (latest sub/follow, etc) and I also turned that source off on every scene for good measure, it "helped" by making this problem manifest less aggressively, but still didn't solve it.
I can't imagine that I'm actually having a resource bottleneck with my specs and configuration, I've ordered more RAM because 32gb would definitely be better than 16 in general, but I'd be surprised if this was a fix because it seems to be more of a bug-based bottleneck regarding hardware acceleration than a raw resource level issue.
Anyway, happy to try just about literally anything anyone has to suggest!
Here is a clip of my camera source responding to the issue that seems to be connected to hardware accelerated browser sources. This is also happening on the current stable release and without any plugins either, but I was currently testing the v29 beta to see if having more optimal nvenc settings with StreamFX's beta helped anything.
Here's the log of that stream: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/yStOzBCshtSUmmd-#logURL
I've recently turned HAGS back on because it was allegedly recommended, but I see the log analyzer is recommending I don't use it. I'll try that yet again for good measure but this has been thoroughly toggled on and off many a time. I saw that my stream elements overlay source is constantly complaining about permissions and such, it's just for alerts and some text on screen (latest sub/follow, etc) and I also turned that source off on every scene for good measure, it "helped" by making this problem manifest less aggressively, but still didn't solve it.
I can't imagine that I'm actually having a resource bottleneck with my specs and configuration, I've ordered more RAM because 32gb would definitely be better than 16 in general, but I'd be surprised if this was a fix because it seems to be more of a bug-based bottleneck regarding hardware acceleration than a raw resource level issue.
Anyway, happy to try just about literally anything anyone has to suggest!
serenmew
New Member
Gonna have to agree that browser acceleration seems to have some issues on newer versions of OBS. I run online events and use embeded Twitch streams in my scenes. Never had a problem in the past doing this. Recently went back to this method of using browser sources in my scenes and seemingly randomly all my browser sources will lock up when playing back video. Disabling browser acceleration fixes this lock up but has poor performance overall.
Going to try reverting to OBS 27 and see if that fixes the problem.
Going to try reverting to OBS 27 and see if that fixes the problem.
Tyr808
Member
I wouldn't doubt that, Ryzen has been anything but a flawless experience, but prior to the 27.2 update, running a 5800x cpu and 3080 gpu on windows 11 was capable of running without any of these issues so it shouldn't be a resource limit. I also used to be on 16GB (8gb x2) of 3200mhz CL22 ram, and upgraded to much nicer 32gb (x2 kit again) of 3600mhz cl16 since Ryzen tends to really scale with better memory. I'm going to continue to do some more testing to see if I can't isolate anything, but the 16gb of RAM was the one area where I'd have accepted that the issues could be resource based as 16GB isn't much these days, but it had zero effect on the issues described despite being a nice upgrade in some other situations (such as streaming Forza horizon 5, which was very RAM hungry)
serenmew
New Member
Reverted to OBS 27 and havent had this issue for several days. Not a great long term solution but hopefully this gets acknowledged / resolved so I can go back to the latest build.