Question / Help Open Broadcaster Doesn't Recognizes Just Cause 3

As the title says, I've tried recording Just Cause 3 and it just doesn't work, I've tried with the game capture and selected the application Just Cause 3 , it was the only one in the list, but the screen is black, I've put the game as the top layer, even tried to see if the game is recognized in window mode and still doesn't work.

Any help ?
 
You are not alone i am also having the same problem not sure if this is due to the update or what but i never had this problem before i hope some one can help us?
 
Running v0.657b - 64bit how do i revert to older version? Just install older version over it? What version are you guys running?
 
Well i am using obs for Twitch i never used dxtory there before so i really need a work around i am thinking they screwed the pooch on the new update if anyone finds a fix please post it thanks.
 
I'm having this same issue. Been using monitor capture, but I tend to get a bit less of an FPS drop when using game capture. Is there anything I can do to fix this, or will I have to wait for an update?

Edit: Anti cheat compatibility checkbox does not help. Still black screen.
 
Last edited:
Add me to the list of users that can't get it working. Compatibility Hook doesn't do anything either. First thing I tried.
 
If game capture works with other games, contact the game developer to get OBS whitelisted in their anti-cheat blocking software.
 
I tried monitor capture as well as window capture both modes do not work it is always just a black screen. The only way obs works for me with this game is start obs then star game but do not click outside the game or it goes black screen and never comes back which is unacceptable while streaming.

I was in hope the new nvidia drivers would fix it but it did nothing to help with it as i just tried the new ones that came out today version 359.06 not sure if any of this would help but here is my system specs

Windows 7 x64

Monitor: ASUS VG248QE Black 24" 144Hz 1ms (GTG) HDMI Widescreen LED Backlight LCD 3D Monitor + NVIDIA G-SYNC Technology Installed

Second Monitor: Acer S Series S230HL Abd Black 23" 5ms Widescreen LED Monitor

Corsair Obsidian 750D Black ATX Full Tower Computer Case

ASUS MAXIMUS VII HERO LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard

GIGABYTE GV-N980WF3OC-4GD GeForce GTX 980 4GB 256-Bit DDR5 PCI Express 3.0 WINDFORCE 3X GAMING Graphics Card

SeaSonic M12II 620 Bronze 620W ATX12V V2.3 / EPS 12V V2.91 SLI Ready 80 PLUS BRONZE Certified Full Modular Active PFC Power Supply

Intel Core i7-4790K Haswell Quad-Core 4.0GHz LGA 1150 Desktop Processor BX80646I74790K

CPU Fans & Heatsink: Noctua NH-U14S 140x150x25 ( NF-A15 PWM) SSO2-Bearing ( Self-stabilising oil-presure bearing ) CPU Cooler

CORSAIR Vengeance 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model CMZ8GX3M2A1600C9B

SAMSUNG 840 EVO MZ-7TE120BW 2.5" 120GB SATA III TLC Internal Solid State Drive (SSD) WD BLACK SERIES WD1003FZEX 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive

SAMSUNG 840 EVO MZ-7TE250BW 2.5" 250GB SATA 6Gb/s 1x nm Samsung Toggle DDR 2.0 3-Bit MLC NAND Flash Memory (400Mbps) Internal Solid State Drive (SSD)
 
Last edited:
And how many of you have asked the game developer about getting OBS whitelisted?
I don't think this is an issue of OBS being blacklisted or being blocked by any kind of anti-cheat or anything--it's a singleplayer game. That just wouldn't make any sense.

My best guess is that the game is doing something significantly different than other games in their rendering pipeline/DirectX context that OBS hasn't specifically accounted for. I can confirm that other game capture programs like Dxtory and Fraps are working fine (and possibly others too), so this would seem to be a problem with OBS.
 
Last edited:
https://gist.github.com/154f757d56efcea85932

I'm certain this can be easily reproduced on any configuration, as it seems to be a problem with the way that OBS interacts with this specific game, rather than some isolated issue or user error, which this is neither. I'm unsure where the hostility is coming from.

Just to keep it simple, for this log I started a local file recording, hit the game capture key, saw a black screen with only my cursor in it, then stopped the recording. The exact same results occur when using the "anti-cheat compatibility" checkbox, as well as just selecting the application from the dropdown instead of using the hotkey and switching between fullscreen and windowed mode in the game.
 
The game is being incorrectly detected as DX10, when it's actually DX11. The same thing used to happen with Just Cause 2, though apparently a different workaround/fix seems to be required this time around. (Since Just Cause 2 still works properly with Game Capture.)

Edit: Yeah, it was just as I thought. It's attempting to hook DX10 before DX11. If you can can compile OBS-MP yourself, you can fix it by moving the D3D11 capture init above the DX10 stuff in dxgi-capture.cpp, line 41.

You can also add an exception to the list above it, like this:
if (_strcmpi(process_name, "iw6sp64_ship.exe") == 0 ||
_strcmpi(process_name, "iw6mp64_ship.exe") == 0 ||
_strcmpi(process_name, "justcause3.exe") == 0) {
ignore_d3d10 = true;
}

But I'm sure a fix will be added for this soon enough. A hackfix, if nothing else.
 
Last edited:
Back
Top