Question / Help OBS only captures some of the selected window

[LiterallySL]

Hi.

This happens with almost every window I try to capture with OBS: http://i.gyazo.com/a2bf9c452977e81414a5958773d8c004.mp4

As you can see, only a portion of the window is actually displayed. I tried messing with my resolution settings but nothing worked. Neither did changing from "Inner Window" to "Entire Window".

Here's my log; the ending doesn't look like any fun and that might be where the problem is: http://pastebin.com/xk5GpG7E

 

[Felix941]

Hey LiterallySL,

I literally have no idea of Log files because nobody ever read me into them or tought me to read them.

One thing I saw tho:

"Bad resolution / FPS / bitrate combination
The combination of settings you are using will likely lead to a low quality stream with artifacting and other problems. Consider either raising your bitrate or lowering your resolution / FPS (qval: 0.019)"

Also how u can see in second 3 of ur video, try "compatibility mode", if that doesnt work try capturing "entire window".

regards, Felix

 

[LiterallySL]

Hi, Felix941.
Unfortunately that didn't seem to solve anything; I still get the same result.

 

[Felix941]

Okay, thats is very interessting. Try run OBS in admin mode and in 32/64bit, maybe that will help or do anything

 

[Modem]

You should also make sure to double click on your window capture and make sure that the sub region box is not checked. That's how it usually looks for me if I crop the capture for something and switch it to something else using the same window capture.

 

[FerretBomb]

Weird. Try right-clicking on the Source in the list, and 'reset size'. It's been known to fix wrong-size issues in the past, and it takes only a few seconds so it's worth a shot.

I'm going to guess that it may be related to this line: "DoGLGPUHook: wglDXOpenDeviceNV failed" as something is interfering with OBS' ability to hook the GPU directly for capture; could be an overlay program (Razer Synapse, MSI Afterburner, Gyazo, Overwolf, etc) so I'd try killing those off if any are running and giving it another shot.

Does this only happen with Chrome, or other programs as well? I ask because Chrome has been having some GPU-accellerated glitches in recent patches, and this could be a symptom of that, if it only happens with Chrome.

On a side note, do hope you realize that 750kbps really isn't anywhere close to enough for an 864p@30fps stream, and that the settings in the log are for testing purposes only.

 

[LiterallySL]

Weird. Try right-clicking on the Source in the list, and 'reset size'. It's been known to fix wrong-size issues in the past, and it takes only a few seconds so it's worth a shot.

I'm going to guess that it may be related to this line: "DoGLGPUHook: wglDXOpenDeviceNV failed" as something is interfering with OBS' ability to hook the GPU directly for capture; could be an overlay program (Razer Synapse, MSI Afterburner, Gyazo, Overwolf, etc) so I'd try killing those off if any are running and giving it another shot.

Does this only happen with Chrome, or other programs as well? I ask because Chrome has been having some GPU-accellerated glitches in recent patches, and this could be a symptom of that, if it only happens with Chrome.

On a side note, do hope you realize that 750kbps really isn't anywhere close to enough for an 864p@30fps stream, and that the settings in the log are for testing purposes only.

Nice. Chrome just doesn't capture properly for some reason. Any way to fix that?

 

[FerretBomb]

Quick Googling for 'chrome disable hardware acceleration' brings up this:
http://www.sevenforums.com/tutorials/271264-chrome-gpu-hardware-acceleration-turn-off.html

It's a setting under chrome://flags (put that in your address bar and hit enter) partway down. Disable GPU compositing on all pages, and relaunch.

Not sure if this will do it, but if the problem is restricted to Chrome, may need to find alternate methods if it's misbehaving. In your example vid it looks like you're trying to cap a Twitch video stream. Assuming you have permission from the original author/caster (remember, livestreams fall under automatic copyright), might try Livestreamer with VLC, and cap the VLC window instead. If that's not an option, may need to use something like Firefox for on-stream webpage display (assuming the CLR browser plugin doesn't work for your purposes) until Google fixes their code again.