You connect to the console, the client opens, and instead of your game you get a black window. This is the single most common SysDVR complaint, and it is rarely a broken install. The most likely cause is the simplest one: the video player is still waiting for a keyframe. The console sends a full keyframe roughly every two seconds, and until one arrives the client has nothing to draw.
If the picture never appears at all, the next suspects are a game that blocks video recording, or you are looking at a screen SysDVR can never capture — the Home menu and system UI are not streamed, ever. Go through the causes below in order.
Fix 1: Wait, then move the game camera
After connecting, give the stream a few seconds. Especially in games where the screen is mostly static — 2D platformers are the classic example — a keyframe can take a while to show up. Moving the game camera or character forces the console to emit new frames and usually makes the picture pop in. If video appears after movement, nothing was wrong.
Fix 2: Run the capture-button test
SysDVR streams through the console’s built-in video recording feature, so it can only show games that support it. The test takes five seconds: in the game, long-press the capture button. If the console can record a clip, the game is compatible and the black screen comes from something else on this list. If recording is blocked, SysDVR gets no video from that title — some games only allow capture in certain sections, so streaming works there and goes black elsewhere.
For games that block recording, the author of SysDVR maintains a separate patch set called dvr-patches that can unlock streaming for many of them. It must match your console firmware, and a small number of games still will not work properly. See installing dvr-patches and our game compatibility overview.
Fix 3: Launch a game — the Home menu is never captured
The system UI, Home menu, console settings and homebrew launched as applets are not captured by SysDVR at all; they always show as black or blank. If you connected before starting a game, that is your answer: launch a compatible game and the stream begins. For the technical background, the Settings app explained post covers what the sysmodule can and cannot see.
Fix 4: Homebrew needs title takeover
Homebrew launched through the album applet will not stream. To stream homebrew, use title takeover: hold R while launching a compatible game so the homebrew runs in its place with full permissions — then it is captured like a game.
Fix 5: Match versions and reboot
A console sysmodule and client on different versions can connect oddly or produce no video. Make sure both sides run the same release (the current one is on our download page) and reboot the console after updating, because sysmodules reload only at boot. The full routine is in how to update SysDVR.
Fix 6: If you watch through RTSP or OBS, check the player
In Simple Network mode, some players buffer aggressively or sit on a black frame while filling their cache. mpv with the low-latency flags is the recommended player — see the RTSP mode guide. OBS used as a media source adds its own buffering delay, so a black OBS source for the first seconds is normal; give it time before assuming failure. Also confirm the mode selected in the SysDVR Settings app matches how you are trying to watch.
Only one game is black, the rest are fine
Take that as good news: your install, versions and network are all healthy, and the problem is that specific title. Some games allow video capture only in certain sections — menus, cutscenes or particular modes — so the stream works in one part of the game and goes black in another, in a pattern that repeats exactly. That is the capture restriction working as designed, and the dvr-patches route in Fix 2 is the only lever that changes it. If the same game is black everywhere while others stream, it is simply an unsupported title.
Sound but no picture? That narrows it down
If you can hear the game’s audio while the window stays black, the stream itself is connected and flowing — only the video side is stuck. That rules out discovery, network and version problems and points squarely at the causes above: a keyframe that has not arrived yet, a player holding an empty buffer, or a game section where video capture is blocked while audio still passes. Work Fixes 1, 2 and 6 and ignore the rest.
Mode mismatch: the silent setup error
Finally, confirm the console is in the mode you think it is. If the SysDVR Settings app is set to USB while you open the network client (or the other way around), you can end up staring at a black or empty player with no error anywhere. Switching modes takes seconds in the Settings app and applies to the full build without a reboot. While you are there, glance at the running state: if the sysmodule reports it is not running yet, you are looking at the 20-second startup wait covered in the Settings “not running” guide, not a video problem at all.
Still stuck?
If a capture-compatible game still shows black after a keyframe wait, a version check and a reboot, capture the details (game title, mode, both version numbers) and ask in the project Discord or open a GitHub issue. You will find more symptom-based guides on the troubleshooting hub — including video but no audio and lag and stutter.