Question / Help Stream freezes when in game

Invisobel

New Member
I'm having this same problem with BF1. Preview freezes. Stream/Local Recording stops but OBS isn't frozen. And then I get a ton of this.

19:03:32.231: device_texture_create (D3D11): Failed to create 2D texture (887A0005)
19:03:32.251: device_texture_create (D3D11): Failed to create 2D texture (887A0005)
19:03:35.606: device_resize (D3D11): Failed to resize swap buffers (887A0005)
19:03:35.607: device_set_render_target (D3D11): texture is not a render target
19:03:35.608: device_set_render_target (D3D11): texture is not a render target
19:03:35.626: device_resize (D3D11): Failed to resize swap buffers (887A0005)
19:03:35.629: device_set_render_target (D3D11): texture is not a render target
19:03:35.651: device_set_render_target (D3D11): texture is not a render target

If I hit Stop Stream/Recording it just says shutting down and I have to Exit it to close it. Sounds similar to your issue?
 

RytoEX

Forum Admin
Forum Moderator
Developer
I'm having this same problem with BF1. Preview freezes. Stream/Local Recording stops but OBS isn't frozen. And then I get a ton of this.

19:03:32.231: device_texture_create (D3D11): Failed to create 2D texture (887A0005)
19:03:32.251: device_texture_create (D3D11): Failed to create 2D texture (887A0005)
19:03:35.606: device_resize (D3D11): Failed to resize swap buffers (887A0005)
19:03:35.607: device_set_render_target (D3D11): texture is not a render target
19:03:35.608: device_set_render_target (D3D11): texture is not a render target
19:03:35.626: device_resize (D3D11): Failed to resize swap buffers (887A0005)
19:03:35.629: device_set_render_target (D3D11): texture is not a render target
19:03:35.651: device_set_render_target (D3D11): texture is not a render target

If I hit Stop Stream/Recording it just says shutting down and I have to Exit it to close it. Sounds similar to your issue?
You're having a different issue, which, assuming you're on Windows 10 Anniversary Update (Version 1607), is detailed here.

Since @Colesslawzz says that the their capture/stream returns to normal, they're having a different issue.
 
Top