Skip to main content

OBS Black/Frozen Screen Issue

Recently I went back to streaming and tried to improve my setup and use Streamlabs OBS (SLOBS), a variant of the popular Open Broadcaster Software (OBS) which includes a really nice app for iOS and Android which lets you control you broadcast.

My only issue about SLOBS (and/or OBS) in general is when you stream some games, its a hit or miss experience. Most of the reported issues include a black screen (but with audio) or in my experience, frozen frames as I transition from one part of a game to another.

I had the time to do some trial and error testing yesterday and listed below is the pre-requisites and some quick summary of my setup. Take note of the terminologies used throughout this post.

Terminologies
  • SLOBS/OBS - Streaming software, liberally used interchangeably in this post. 
  • Source - This is where an input of OBS is coming from. This can be a webcam, computer screen, full screen application, a webpage, an image, etc.
  • Display Capture - Captures your whole screen regardless of what application you are running
  • Game Capture - Captures several types of game windows, any full screen application, target app, etc.
  • Overlay - Any software that puts information on top of a window (ie. stats, readings, quick controls, etc)
  • Anti-cheat hook - An option in SLOBS/OBS where the window listener will mimic user behaviour to avoid triggering anti-cheat applications
  • Blizzard games - Anything launched within the Battle.net launcher. This includes Diablo 3, Overwatch, Starcraft, World of Warcaft, etc.
  • Other games - Any other game outside of Battle.net titles.
Pre-requisites
  1. Run as Administrator - Run SLOBS as Administrator
  2. New game, new stream - If you are changing a game, it is advisable to stop the stream, close the game, start the new game and start a new stream. I had issues where OBS failed to capture the new full screen application after relaunching, at times even the display capture fails to stream it properly.
  3. Disable overlays you don't use - The only overlay I want is the MSI Afterburner so that I can track my CPU/GPU usage and temp when I'm watching my recording. The NVidia game stream overlay and the Windows 10 Game Mode should be disabled since OBS tends to panic with so much overlays.
  4. Disable anti-cheat hook - Disable the anti-cheat hook for game capture. This is one of the recommendations found from scouring the forums about black screen issues. 
Setup your SLOBS/OBS

Below is my SLOBS/OBS desktop app setup which has 4 scenes:

  • Stand By - For the standby image, the source is just an image
  • Blizz (Game; No Overlay) - Which includes a Game Capture source with overlay unchecked, anti-cheat hook unchecked
  • Other Games (Disp Cap) - For all other games with a Display Capture source
  • Other Games (Game Cap) - For all other games with a Game Capture source with overlay checked and anti-cheat hook unchecked
In my SLOBS app, I start with the Stand By scene and just toggle to the other scenes as needed. 


Final Notes

Please keep in mind that the tests performed here is not a complete and exhaustive test on what works for what games all the time. It is always better to preview your OBS using a second monitor or hope that the SLOBS mobile app would include a feature to preview your stream before hitting that "Go Live" button. 

The combination of SLOBS desktop and mobile app completely removes the need for an expensive device like an Elgato Stream Deck. While it is lacking in some of the aspects like: Why cant it properly handle overlays? Why does it panic if you have too many of the same sources in too many scenes? For a free application, I'm not one to complain. I do feel that at times it is disappointing to go back to my stream and see that nothing was captured. 

Here are Some of my TLDRs;
  • Blizzard games doesnt like overlay (and display capture)
  • Other games is ok with overlay using Display Capture
  • PUBG doesnt like Game Capture (with or w/o overlay)
  • Use Display Capture as much as possible

Comments

Post a Comment

Popular posts from this blog

Moving to a New Linux Web Based Torrent Client

For years, I have been using TorrentFlux (url here) as my primary torrent client situated in my Ubuntu download server. But as time went on, the developers completely abandoned the development of TorrentFlux which led to several forks which I think is still insufficient for my needs. Main GUI of TorrentFlux Ive checked several options which runs on a GUI-less environment. Since my Ubuntu server is just running on command line to save precious memory, I needed something bare, simple and is packed with features. Installing uTorrent Server is pretty straight forward. Download. Uncompress. Run. This is better than the approach of TorrentFlux which you need to setup LAMP server and create a database. More often than not, it happens to me that some of the data in the DB gets corrupted. I normally just reinstall the whole thing again. Main GUI of uTorrent Server To further elaborate on the setup process, I've gotten an excerpt from this thread which, quite simply discusses ho

LTE and the Unlocked iPhone 5

So heres the deal, theres a new iPhone out there and its got the new blazing LTE. If you're planning to get one buying from countries which have unlocked options (Canada, Singapore, Hong Kong) doesnt necessarily merit that you'll get LTE compatibility wherever you go. In the iPhone 5 website, theres a little asterisk there. Pretty sneaky if you ask me, that they have created 2 different models probably using 2 different LTE chips. GSM model A1428*: UMTS/HSPA+/DC-HSDPA (850, 900, 1900, 2100 MHz); GSM/EDGE (850, 900, 1800, 1900 MHz); LTE (Bands 4 and 17)  GSM model A1429*: UMTS/HSPA+/DC-HSDPA (850, 900, 1900, 2100 MHz); GSM/EDGE (850, 900, 1800, 1900 MHz); LTE (Bands 1, 3, 5) - From: http://www.apple.com/iphone/specs.html So what does this mean? If you're planning to get an unlocked unit from other country, LTE speeds might not be compatible with yours. From Wikpedia , theres a working list of LTE bands per country. With me residing in the Philippines it seems t

Ive Messed Up My Master Boot Record

I got too overly excited in refreshing my OS installation in my old Inspiron 640m that I just cleaned off the Linux partition through the Drive Management Snap-in of Microsoft while I was still booted in XP. I completely forgot that the GRUB was the bootloader managing my OS selection in the Master Boot Record of my drive. In plain English, I wanted to clear out my old Linux installation and merge the partition with the old XP partition when I run the Windows 7 install. It was a mistake to use the Drive Management Snap-in rather than having the Windows 7 installation take care of the partition clearing. This caused problems because the bootloader (GRUB) or the one which asks which OS are you going to boot is in the partition I wiped out. Therefore, I cannot go into the Linux partition (obviously, since it has already been wiped out) nor the Windows XP partition. There is a quick fix with this by using the XP install CD and fixing the MBR by going to the command prompt and typing fi