Bug Report Game Capture not working since update

C

crispyraccoon

New Member
I installed the auto-update to .6.3.5b and lost the ability to use the Game Capture option to capture games. I then installed the .6.3.5b version from the actual installer and have the same issue. It will let me see the game for about 2 seconds as an option under the Game Capture properties. When I select it and go to the game, the preview shows a stationary image. I confirmed that my broadcast on twitch is also showing a still image. if I go back to the Game Capture properties, and change the display option to something else and try to go back, the game is no longer an option. This is all while the game is running and I am in game. I had 0 issues before this update I was using version .6.2.2
Please Help!
 
C

crispyraccoon

New Member
Code: 
Last game capture log:
2014-09-17, 13:45:10: we're booting up:
13:45:10: CaptureThread: attached to process Gunpoint.exe
13:45:10: GL Present
13:45:10: DirectDraw Present
13:45:10: SwapBuffers(1627459799) Called
13:45:10: (half life scientist) everything..  seems to be in order
13:45:10: NV Capture available
13:45:10: FBO available
13:45:10: setting up gl data
13:45:11: share device: 206592916
13:45:11: share texture: 205718392
13:45:11: share device handle: 193847424
13:45:11: share texture handle: 393740360
13:45:11: DoGLGPUHook: success
13:45:11: wglSwapBuffers(1627459799) Called
13:46:02: stop requested, terminating gl capture
13:46:02: ---------------------- Cleared OpenGL Capture ----------------------
13:46:02: wglSwapBuffers(1627459799) Called
13:46:02: setting up gl data
13:46:02: SwapBuffers(1627459799) Called
13:52:36: wglDeleteContext Called
13:52:36: ---------------------- Cleared OpenGL Capture ----------------------
7: stop requested, terminating d3d10 capture
13:52:17: ---------------------- Cleared D3D10 Capture ----------------------
13:53:24: DoD3D10Hook: success
13:53:24: successfully capturing d3d10 frames via GPU
13:53:42: stop requested, terminating d3d10 capture
13:53:42: ---------------------- Cleared D3D10 Capture ----------------------
13:54:02: ---------------------- Cleared D3D10 Capture ----------------------
13:54:02: DXGI: Found D3D 10
13:54:02: setting up d3d10 data
13:54:02: ---------------------- Cleared D3D10 Capture ----------------------
20:50:00: ---------------------- Cleared D3D10 Capture ----------------------
20:50:00: DXGI: Found D3D 10
20:50:00: setting up d3d10 data
20:50:00: ---------------------- Cleared D3D10 Capture ----------------------
20:50:05: ---------------------- Cleared D3D10 Capture ----------------------
20:50:05: DXGI: Found D3D 10
20:50:05: setting up d3d10 data
20:50:05: ---------------------- Cleared D3D10 Capture ----------------------
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
That log file is actually incomplete -- I need a full log file. You can get a full log file by just using the options in the help menu to 'upload last log file'
 
C

crispyraccoon

New Member
Well, no need apparently. For the time being at least, it appears to be working again. If it acts up I will start a new post. I guess you can dump this one...
 
D

Dem

New Member
I'm actually more or less in the same boat as racoon here. Since the update video capture can't handle streaming for me. If it's capturing something that has little changes to it, then it'll do fine. But generally when I'm streaming gameplay, it's not going to be that way.

https://gist.github.com/8299512dd2efd67ccf13



It also did this earlier for me.

OBS has encountered an unhandled exception and has terminated. If you are able to
reproduce this crash, please submit this crash report on the forums at
http://www.obsproject.com/ - include the contents of this crash log and the
minidump .dmp file (if available) as well as your regular OBS log files and
a description of what you were doing at the time of the crash.

This crash appears to have occured in the 'c:\windows\syswow64\kernelbase.dll' module.

**** UNHANDLED EXCEPTION: 80000003
Fault address: 75143226 (c:\windows\syswow64\kernelbase.dll)
OBS version: Open Broadcaster Software v0.635b
Windows version: 6.1 (Build 7601) Service Pack 1
CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz

Crashing thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
0030F3D8 75143226 00000FF8 00007532 0000138B 00071106 kernelbase.dll!0x75143226
0030F3E8 003B7DAD 00000000 75026FB6 0030F578 003DC5C3 obs.exe!OBS::Stop+0x19d
0030F430 003B5795 00000000 003DB820 3F800000 00000000 obs.exe!OBS::ToggleCapturing+0x35
0030F440 003DC5C3 75016D51 0030F5A4 750162FA 0006112E obs.exe!OBS::OBSProc+0xda3
0030F574 75016D91 003DB820 0006112E 00000111 0000138B user32.dll!0x75016d91
0030F5AC 75016D3A 00000000 003DB820 0006112E 00000111 user32.dll!0x75016d3a
0030F624 7501965E 00A13F90 00000000 003DB820 0000138B user32.dll!0x7501965e
0030F668 750196C5 0006112E 00000111 0000138B 00071106 user32.dll!0x750196c5
0030F68C 71EF4601 009420D0 00000000 00071106 009420D0 comctl32.dll!0x71ef4601
0030F6AC 71EF4663 54010000 00000001 00000000 71E7B495 comctl32.dll!0x71ef4663
0030F6C8 71EF44ED 00071106 00000202 00000000 000C0057 comctl32.dll!0x71ef44ed
0030F728 750162FA 71E7B495 00071106 00000202 00000000 user32.dll!0x750162fa
0030F754 75016D3A 00000000 71E7B495 00071106 00000202 user32.dll!0x75016d3a
0030F7CC 750177C4 71E7B495 00000000 0030F860 7503C81F user32.dll!0x750177c4
0030F82C 7501788A 0030F904 009349E0 40FD0E65 750178E2 user32.dll!0x7501788a
0030F83C 7503C81F 0006112E 00000000 00000000 00000001 user32.dll!0x7503c81f
0030F868 003A9CC2 00360000 00000000 008E310D 00000001 obs.exe!WinMain+0x972
0030FD38 003F92DA FFFDE000 0030FDC8 773C9F72 FFFDE000 obs.exe!__tmainCRTStartup+0xfd
0030FD84 7519338A FFFDE000 63DFE8E7 00000000 00000000 kernel32.dll!0x7519338a
0030FD90 773C9F72 003F91D3 FFFDE000 00000000 00000000 ntdll.dll!0x773c9f72
0030FDD0 773C9F45 003F91D3 FFFDE000 00000000 00000000 ntdll.dll!0x773c9f45

Video thread stack trace:
Stack EIP Arg0 Arg1 Arg2 Arg3 Address
0030FDD0 773C9F45 003F91D3 FFFDE000 00000000 00000000 ntdll.dll!0x773c9f45

A minidump was saved to C:\Users\Daniel\AppData\Roaming\OBS\crashDumps\OBSCrashDump2014-09-21_1.dmp.
Please include this file when posting a crash report.

List of loaded modules:
Base Address Module
 
C

Chris_802

New Member
I'm in the same boat here, came here looking for a solution. Even the most recent update hasn't fixed the issue.
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
Dem - there was no sign of game capture in the log, and that crash appears unrelated.

Chris_802 - you didn't include a log file.
 
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
Jerricho - We did not change the usage of graphics adapters for any of the recent updates at all. Nor did we change the capture stuff. If you get a black screen and you have multiple video adapters, the most likely explanation is that the game is running on one adapter, and OBS is running on another adapter. If that happens OBS cannot "see" the texture on the other graphics adapter. What exactly is happening on your end I don't know, but I feel very wary of blaming it on the update when we didn't actually really change anything in relation to that.
 
K

Karga

New Member
I didn't use OBS for a few weeks. Today I just updated the software, and it seems it doesn't catch Dota2 anymore. I tried to delete the source and add it again a few times. I also tried to run the game in windowed mode, but It just doesn't capture any movement in my screen. A few times I had a blank blackscreen, once I had dota2 screen but it had no motion in it. It was just as same as when I re-added the game as a new source.
the log files are added .

I also tried to create new profiles, and scenes. Once I added another profile, it capture the game just as a still image. NO problem with the voice, I can hear the in-game sound without problems. It is just the video.
 

Attachments

  • 2014-09-26-0157-20.log
    30.2 KB · Views: 16
  • 2014-09-26-0219-58.log
    8.1 KB · Views: 13
Last edited:
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
For some reason the encoder is stalling for you Karga. You have a good computer so there's probably no real reason to use NVenc when you can use x264 instead, which is typically higher quality.
 
C

Chris_802

New Member
Jim, here's my recent log files.
 

Attachments

  • 2014-09-25-1155-59.log
    3.4 KB · Views: 12
  • 2014-09-25-1210-21.log
    3.6 KB · Views: 12
  • 2014-09-25-1212-21.log
    9.8 KB · Views: 13
K

Karga

New Member
Jim said:
For some reason the encoder is stalling for you Karga. You have a good computer so there's probably no real reason to use NVenc when you can use x264 instead, which is typically higher quality.
Click to expand...
thanks for your answer. Changing the encoding type worked for me. But I prefer the onboard encoding feature to make sure capturing doesn't effect my game performance.
The Nvec feature worked pretty well before, what might be the reason? I updated my Graphic card drivers but that didn't solve the issue?
Thanks!
 
K

Karga

New Member
Jim, I tested the SHadowPlay feature itself, using the GEforece experience sowftware of my gtx 780. I wanted to make sure the codec-adapter or whatever hardware support the graphic card has is working properly and didnt burn out or something. Using the desktop capture feature, It just worked fine.

I guess there is something wrong between OBS and my NVidia. As I said, It was working properly for months. I recorded hundreds of videos that way.
 
You must log in or register to reply here.
Top