Bug Report Cannot add minimized game to scene using game capture

[mrpg]

I'm trying to stream Chocolate Doom but cannot add it as a game capture source - as soon as I alt-tab from it to OBS the game minimizes itself automatically (there seems to be no way to disable this), the list in OBS auto-refreshes immediately - and the game is not there. The list visibly refreshes again when I alt-tab back to the game (it's on a different monitor), but I cannot find any way to check what's there while the game is active. I suspect the game destroys and creates its window on demand. Probably this could be an issue for some other games.

The solution, as far as I can see it, would be remembering game windows for this list during each session and not refresh the list from scratch, only add newly discovered ones to it.

 

[AbsenteeSurgeon]

I ran into a similar problem with the program Elpis (as I described here: viewtopic.php?f=6&t=1223)

It seems like the window changes it's "ID" when you minimize/expand it (in the case of Elpis the "ID" changed when the program was exited and restarted). Does re-setting the Game Capture make the game reappear?

I don't know any more than you do about your problem (sorry!), just trying to help further define it.

 

[mrpg]

It's probably a different problem - in my case there is nothing to add from the very beginning, the game never appears in the list. I have high hopes it's in there while the game is in foreground, but I can't confirm it.

 

[paibox]

You are most likely using the wrong version of OBS. In order to capture 32-bit applications you must use the 32-bit version of OBS, and the same goes for 64-bit. Unless Chocolate Doom is a 64-bit application, make sure that you are running the 32-bit version of OBS. When you have issues like this, it's always beneficial to include a log file of when you've tried to stream to simplify troubleshooting.

 

[mrpg]

The game is a 32 bit application, I use 32 bit version of OBS on a 64 bit Windows 7. I tried to use 64 bit version of OBS and it correctly identified the game as 32 bit and refused to capture it. The logs, unfortunately, contain no information about the list of identified game sources, so I didn't include them before. I've attached a test log of an empty scene to this message, just in case.
I don't see any crashes, incompatibilities or other problems here, everything works perfectly, I successfully captured and streamed Starcraft 2 as a test case (using both methods of capture). The problem manifests with this particular application (basically, one of the DOOM source ports that tries to stay as close to the original old-school experience as possible while using DirectX): http://www.chocolate-doom.org/
Further experiments gave a bit more information: the game could be configured to use DirectX or Windows GDI for output and run fullscreen or windowed. I configured it to use DirectX and fullscreen originally and didn't check what would happen if it would be set to run in a window. In a window it doesn't auto-minimize, but, unfortunately, still doesn't appear in the list, even after refreshing it. So, I guess, it uses some mode which is not compatible with game capture plugin - and there is no way to fix it...

Open Broadcaster Software v0.466a - 32bit (´・ω・｀)
-------------------------------
CPU Name: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
CPU Speed: 3005MHz
Physical Memory:  4095MB Total, 2807MB Free
stepping id: 11, model 15, family 6, type 0, extmodel 0, extfamily 0, HTT 1, logical cores 4, total cores 4
Windows Version: 6.1 Build 7600 
Aero is Disabled
------------------------------------------
Adapter 1
  Video Adapter: AMD Radeon HD 6900 Series
  Video Adapter Dedicated Video Memory: 2129346560
  Video Adapter Shared System Memory: 4026068992
------------------------------------------
Adapter 2
  Video Adapter: ATI Radeon HD 5800 Series
  Video Adapter Dedicated Video Memory: 1059696640
  Video Adapter Shared System Memory: 4026068992
=====Stream Start=====================================================================
  Multithreaded optimizations: On
  Base resolution: 1920x1200
  Output resolution: 640x400
------------------------------------------
Loading up D3D10...
------------------------------------------
Using auxilary audio input: Microphone (High Definition Audio Device)
------------------------------------------
Audio Encoding: AAC
    bitrate: 128
------------------------------------------
Video Encoding: x264
    fps: 30
    width: 640, height: 400
    preset: ultrafast
    CBR: no
    max bitrate: 2000
    buffer size: 2000
    quality: 7
------------------------------------------
Total frames rendered: 84, number of frames that lagged: 0 (0.00%) (it's okay for some frames to lag)
=====Stream End=======================================================================

Profiler results:

==============================================================
frame - [100%] [avg time: 5.403 ms] [avg calls per frame: 1] [children: 14.7%] [unaccounted: 85.3%]
| scene->Preprocess - [0%] [avg time: 0 ms] [avg calls per frame: 1]
| video encoding and uploading - [14.7%] [avg time: 0.792 ms] [avg calls per frame: 1] [children: 14.3%] [unaccounted: 0.333%]
| | CopyResource - [0.37%] [avg time: 0.02 ms] [avg calls per frame: 0]
| | conversion to 4:2:0 - [0.074%] [avg time: 0.004 ms] [avg calls per frame: 0]
| | call to encoder - [13.9%] [avg time: 0.75 ms] [avg calls per frame: 0]
| | sending stuff out - [0%] [avg time: 0 ms] [avg calls per frame: 0]
==============================================================

 

[paibox]

Ah, you have two video cards in your computer? There are some known issues with this. If you can disable/remove one of them, OBS should work for you. The problem is (I believe) that both OBS and the application need to be running on the same video card, and if you're using Crossfire, that might caused further issues when identifying which video card the game is running on.

 

[mrpg]

ChocolateDoom cannot be captured with Game Capture

Tried a different machine - with one video card. Still, Chocolate Doom doesn't appear in the list. Sorry for the original error in diagnosing the problem - it seems the game is just not compatible with Game Capture mode.