Bug Report Can't Game Capture Arma3.exe

[BullHorn7]

I've tried anything I could come up with.

Anti-cheat enabled, anti-cheat disabled, run the game as Admin, run the game not as Admin, run OBS as Admin, shutting off Steam overlay and TeamSpeak overlays, etc. It only captures when I use Window Capture but that's very limited (Can't remove overlays like FPS or TeamSpeak names) and can't change brightness.

I contacted Arma's anti-cheat Battleye support and they reported the exact same issue on their side, even after launching Arma with BE disabled...

Nobody on IRC could help me either so I'm going to assume it's a bug/problem.

https://gist.github.com/1b3b7f5a9fdf69cae382

p.s. it works just fine with OBS1

 

[Osiris]

It works fine here, either by manually selecting arma3 or leaving the game capture on "Capture any fullscreen application"

 

[BullHorn7]

I tried all of the above, including changing the Window Match Priority.

I contacted Battleye because I thought it was related but even though both me and the BE representative tried disabling BE entirely, both couldn't Game Capture.

 

[HonorguyXNL]

I tried all of the above, including changing the Window Match Priority.

I contacted Battleye because I thought it was related but even though both me and the BE representative tried disabling BE entirely, both couldn't Game Capture.

I encountered the very same issue 2 days ago. What I did notice is that you might want to try to head in-game and switch sometimes between fullscreen and fullscreen borderless. Eventually I had a new .exe window of arma pop up once I got "in-game" with mostly numbers in the window title. This window does bring Arma 3 up front.

However, the normal Arma 3 window does not respond with indeed both Anti cheat disabled as enabled. This seems to be a new issue. So I am sorry @Osiris but there is a new issue with Arma 3. I only managed to get it "fixed" through stupid luck.

 

[BullHorn7]

I tried that previously and it didn't help.

It works now after I a) uninstalled OBSMP and deleted all the configuration files and b) used the binary .zip instead of the .exe installer.

Something is definitely wrong because all other games were working just fine.

 

[HonorguyXNL]

I tried that previously and it didn't help.

It works now after I a) uninstalled OBSMP and deleted all the configuration files and b) used the binary .zip instead of the .exe installer.

Something is definitely wrong because all other games were working just fine.

Interesting, ah well. We will see what the cause is, but it suddenly just denied Arma 3 for me. I got it working but I can't figure out 'what did it" for me.

 

[grester]

I believe the problem still persists. I've been recording arma in windowed mode (which is a terrible idea as OBS drops frames whenever you zoom or go into grass intensive areas) because I play on borderless and game capture wasn't working. Yesterday when I realized that I switced to game capture and it worked once until I had to shut down arma, the next time it would get black screen too again. I believe it was just outta pure luck that I managed to get it to game capture, like Bullhorn said, fiddling everything doesn't really make any diference, is just a matter of luck.

Update: Actually I might have found something. I believe Raptr is the culprit of my personal problems. I've read in OBS logs that some kind of hook was causing problems and its name was of Raptr. It appears that when I close Raptr and sort of "reset" Arma/OBS via the anti-cheat compatibility it starts working again. I'll try to confirm this in a bit...

Conclusion: Yeah it appears to be that Raptr gametracker hook. However for me using the anti-cheat compatibility mode for game capture seems to fix the issue.

 

[BullHorn7]

Confirmed, this probably definitely still persists. It comes and goes and I find myself fighting everytime I want to capture Arma 3. I'll look into other things that may cause hooking issues (Logitech mouse drivers? that would be enraging)

EDIT: Tried killing Rainmeter (taskbar clocks for multiple monitors), Logitech mouse drivers software, ShareX (image capturing software), TSNotifier (TS3 overlay) and whatever else I had running - no difference. :/

 

[BullHorn7]

Confirmed bug with OBS (possibly known by devs):

When you record a game that runs in Borderless Fullscreen, you will usually disable the option "Capture any fullscreen application" in the source and point it towards the .exe.

HOWEVER if you have ANY OTHER Scene that has the "Capture any fullscreen application" enabled, it will try to capture it instead of the Scene that you actually chose.

Some logs:
doesn't work: https://gist.github.com/anonymous/d68f3b011e4c3fc43f11
works: https://gist.github.com/anonymous/a9f23d8b3b826978d299

 

[Osiris]

That's not a bug though. It's a result of the choice to make every source global. A fully expected result.

 

[Sapiens]

Confirmed: All sources in OBS Studio are still global. :P

 

[BullHorn7]

It doesn't matter that you call it a feature, when you try to capture a game and it just doesn't, without giving any hints or information in the logs. 'It just doesn't work' is the feature.

 

[Osiris]

I don't call it a feature, there is just nothing in place yet, to prevent such a situation. Never said that the way it works now is fine, because it isn't.