Bug Report Game Crash when trying to Capture (Wolfenstein: The New Order)

Air Gaming

New Member
I have been trying to capture wolfenstein but every time I do the game simply closes itself.
The only way it seems to work is to run it in a window and do a Monitor capture through the game capture source.
If i try and do a monitor capture, it shows a black screen when I try to maximize the game. Window capture brings up only a black screen. Game capture crashes it. I tried running the 32bit and 64 bit versions of OBS and both do the same. Run as admin did nothing as well. Any help would be appreciated.
 

Krazy

Town drunk
This is the one that just came out today, right?

If you play in borderless windowed mode and use Window Capture with Aero enabled, it should work quite well. Monitor Capture and Window Capture cannot capture fullscreen games. The game might be doing something silly, requiring Jim to change the Game Capture code or something...again. I'll make sure he knows about it.
 

Air Gaming

New Member
Yes its the one that just came out today. I tried doing borderless window with same result. The window capture is black.
Window capture also crashes the game if not in borderless window mode.
 

paibox

heros in an halfshel
Borderless windowed mode + window capture will not work with OpenGL games, because if OpenGL detects a borderless window being the same resolution as the screen, it switches to fullscreen mode. It should actually be capturing the game when you're alt+tabbed out, but that's not very helpful, I know.
 

dwyrin

New Member
Same. It crashes game mode and borderless window comes up black. A really awful way to get this captured is to run the game in a window and use monitor capture with a sub region. I think it has to due with this game being 64bit? I recall another game obs had trouble capturing the 64 bit version of...
 

paibox

heros in an halfshel
dwyrin, do you have an ATI video card, by any chance? So far, it seems to be working perfectly fine for people with NVIDIA cards but crashing for people with ATI, which would indicate some sort of issue with their OpenGL drivers.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
Hm, thanks for letting me know guys, I'll check it out, if I'm lucky I can fix it tonight before the next update (which I was planning on making tonight)
 

Yezirael

New Member
Hey,
i've the same problem using an AMD GPU (R9 290) / Driver 14.4 on NT 6.3 AMD64

I spent a few minutes to locate the 'bug'
it seems that glBlitFramebuffer will always 'kill' the game.

Which may be caused by:
OBS's code will raise any GL Error which wont be cleared, so the ID-Tech5 engine will catch it next time it calls glGetError() .. (or it has a debug callback set ->
GL_ARB_debug_output / GL_AMD_debug_output, so any error raised by obs will be reported to the engine immediately..)

OR

Rage/Wolfenstein checks the address of some gl-proc's periodicly (in order to detect hooks/cheats/hacks..)


Luckily they've distributed the pdb with wolfenstein so we'll be able to debug the game properly ..

Maybe i'll spent more time in investigating this later when i've more time ^^
 
Last edited:

Lain

Forum Admin
Lain
Forum Moderator
Developer
Actually the function is misleading. It only crashes when the interop functions are in use and you call it. Otherwise, it'll never crash. I know this code works otherwise because it works fine with every GL game except idtech games. It's possible I'm missing something, but it works on nvidia cards so I'm not sure what else could be going on.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
Thank you very much John, yea, if the game can be run in borderless/windowed mode that's definitely another option for AMD adapter users.

Though let me just correct one thing, on windows 7, due to performance issues with monitor capture, the ideal way is to use window capture (with aero enabled) on the windowed game. On windows 8+ however both monitor and window capture are fine. EDIT: This doesn't work on OpenGL games, which wolfenstein is, argh, what a nightmare.

Also, game capture can capture the monitor via the dropdown, which is also another ideal option for windows 7, though also requires aero enabled. The fullscreen crash only affects people with AMD graphics adapters right now.

Aero is that glass theme for windows 7. If the glass theme is active, then aero is on. Otherwise, aero is disabled. Important distinction.
 
Last edited:

dacoder

Member
Thank you very much John, yea, if the game can be run in borderless/windowed mode that's definitely another option for AMD adapter users.

Though let me just correct one thing, on windows 7, due to performance issues with monitor capture, the ideal way is to use window capture (with aero enabled) on the windowed game. On windows 8+ however both monitor and window capture are fine.

Also, game capture can capture the monitor via the dropdown, which is also another ideal option for windows 7, though also requires aero enabled. The fullscreen crash only affects people with AMD graphics adapters right now.

Aero is that glass theme for windows 7. If the glass theme is active, then aero is on. Otherwise, aero is disabled. Important distinction.

Is this an issue only with OBS, iD tech, AMD, or the game capture? I would like to post on it further, but dont want to post in the wrong forum / irc...
 

paibox

heros in an halfshel
It's an issue with iD Tech 5 in combination with AMD's OpenGL drivers. I'm not quite sure what you're going to post further on it, but do feel free.
 

ThraxxMedia

New Member
Unfortunately, the latest version of OpenGL drivers in Catalyst 14.6 beta didn't fix this issue. Maybe they're not even aware of it, or don't care at all.

@Jim
As far as I know, window capture doesn't work since all you get to see in OBS then is a black screen. The only working method seems to be monitor capture with sub region, but alas, this brings the aforementioned performance issues. Game capture with monitor source works, too, but there's no way to remove the window borders or task bar in that case. Switching to either fullscreen or windowed fullscreen again just gives a black screen.
 
Last edited:

Lain

Forum Admin
Lain
Forum Moderator
Developer
Ah yes, this is because it's opengl. Window capture doesn't capture opengl games when aero is on. Very annoying. Ugh. Unfortunately there may not be many easy options for you guys on AMD cards right now. Game capture is working with the game on nvidia cards, but AMD cards are definitely crashing, and I know exactly where it's crashing, but the problem is it definitely seems to be a driver issue with this specific engine.

On windows 7, borderless mode in the game and then using game capture's DWM monitor capture drop-down (with aero enabled) would probably be the ideal way, but it does indeed capture the entire monitor. Not sure what else to suggest for the time being, I can't really fix AMD's drivers for them, and I unfortunately have tried just about every code combination to work around the issue.
 
Top