Bug Report DX12 Game capture crashes TW:Warhammer when used.

R

RytoEX

Forum Admin
Forum Moderator
Developer
Your post title and log show "Total War: Warhammer", but your post says Battlefield 1. I assume these are two separate scenarios?

As for Battlefield 1, it's unclear if you're saying the error message came from OBS or from Battlefield. If it came from Battlefield, you might want to report it to them.

Have you tried with the "anti-cheat compatibility hook" enabled? Your log shows it disabled.
 
G

Gaudium

New Member
Title says Warhammer and the log is Warhammer, then you got the "Update" and the msg i got from the game when turned the game capture of OBS on.
These two games can run with DX12, running them with DX12 works fine, streaming them with DX11 works fine, running and streaming on DX12 doesn't work.
OBS DX12 support is fresh since last patch so i figured it might have a problem.

Tried, fullscreen, windowed, vsynce on\off, anticheat on\off..obs crashes both of these game when running them with DX12.

Why would i contact game developer if it crashes when i try to "hook" it with DX12 game capture to stream? :)
 
Last edited:
R

RytoEX

Forum Admin
Forum Moderator
Developer
Gaudium said:
Title says Warhammer and the log is Warhammer, then you got the "Update" and the msg i got from the game when turned the game capture of OBS on.
These two games can run with DX12, running them with DX12 works fine, streaming them with DX11 works fine, running and streaming on DX12 doesn't work.
OBS DX12 support is fresh since last patch so i figured it might have a problem.

Tried, fullscreen, windowed, vsynce on\off, anticheat on\off..obs crashes both of these game when running them with DX12.

Why would i contact game developer if it crashes when i try to "hook" it with DX12 game capture to stream? :)
Click to expand...

If I recall correctly, Battlefield 1's DX12 support was pretty terrible for a while. Some users and testers even reported that they got better performance out of DX11 anyway. I don't know if that has changed (I don't play BF1), which is why I suggested that you might want to contact the developer, especially since the error message comes from BF1 and not OBS. Correlation is not causation, after all.

That said, the lead OBS developer did say not to completely rule out an issue with DX12 game capture, as the feature is new and somewhat experimental. For now, if you need rock-solid no interruptions game capture, and DX12 is not doing that, then I'd switch to DX11 when able.
 
G

Gaudium

New Member
I guess we both can be like broken records and i'll repeat that BF1 crashes when i turn on the hook from OBS game capture on DX12.

There is no relation between DX11 Performance and DX12 performance to the fact it is being crashed by OBS.
DX11 performance is better then DX12 on btoh BF1 and TW:W.

Point of the post was to report a bug, i guess there is no point..maybe later on when more people report it and more games will support DX12 the'll be a point of fixing it :)

Thanks at least for your time RytoEX :)
 
R

RytoEX

Forum Admin
Forum Moderator
Developer
Given the new information in your latest reply, I believe we have a misunderstanding. Sorry about that. Please allow me the opportunity to clear up this misunderstanding.

I pointed out that correlation (that BF1 crashes when OBS's game cap hook starts) does not imply causation (OBS game cap hook causes the crash). What I mean by that is that the occurrence of both events happening does not, by itself, mean that one directly causes the other. It could be a bug in the DX12 implementations of either game, or a driver bug, that is exacerbated or brought to light by OBS beginning a game capture while not directly caused by OBS itself, like the Windows 10 AU driver issues. That's all I was pointing out - the possibility that two seemingly linked events may not actually be linked. Given the history of BF1's DX12 woes (and TW:W's), I felt it was worth the time to point out that possibility.

I don't deny that it's possible that there is a bug in DX12 game capture in OBS, which is why I'd asked the lead developer about it before replying (which is partly why it took me so long to reply). The game capture code is a bit beyond me, at present.

I did not understand that your intent was simply to report a bug and not that you needed DX12 to work. Since I took your intent to be that you wanted/needed game capture to work on these games, I recommended that you switch the games to DX11 both for game capture stability and for performance reasons. I did not realize that you were not looking for recommendations, but rather reporting a bug.

Thank you for reporting the bug. As previously mentioned, I have brought it up to the lead developer. I hope that this clears everything up, and once again, I apologize for the misunderstanding.
 
Last edited:
G

Gaudium

New Member
I actually didn't think that both games could have a problem in their DX12, now that you mention it, it could be actually the case for both games having the issue from the development side.

Yeah, i'll be sticking to DX11 it works great, not a single reason to switch at the moment.

Thanks again for your time!
 
G

Gaudium

New Member
Well another game to the list, Ashes of the Singularity can be played on DX12, obs crashes it with its capture.
I'm getting convinced that OBS DX12 support is broken and not 3 games that have different development teams screwed their DX12 thingy..
 
ensi

ensi

New Member
For me, capture DX12 on TW:WH startred working after 0.16.5, but somewhere around 5fps.
More than that, OBS studio crashes during recording/streaming TW using DX11.
During stream - rarely. Once in a few hours. During recording, very often (NVENC or CPU). Once in 15-30 minutes.
This has been so since the game release.
 
G

Gaudium

New Member
Can you share your log?
Does it say "oops something went wrong"? that is an OBS crash if anything else then it is a game crash.
 
Last edited:
ensi

ensi

New Member
I don't recall right now, I'll check it a bit later today to make sure. I think it was the "device_texture_create (D3D11): Failed to create 2D texture (887A0005)" thing but I got to make sure. OBS stays in "recording" state when it happens. Used to be stuck in this state with the only option to close OBS by force. Now they have fixed the button so I can force stop it and the video before hang is 100% working. However why this happens is a mystery. I am just sitting here, praying, waiting for it to be fixed with some OBS/WH:TW/WIN10 update. It happened to me in No man's sky as well and once they patched some performance stuff it started happening much much less. Unfortunately, that game is too shitty for me to keep testing on it :D
 
You must log in or register to reply here.
Top