Bug Report OBS Recording Crashes with Besiege & Blender (Solved)

[Skeletonbane]

I don't know why, but whenever I try to record Besiege or the Blender Player my recording crashes. Both programs are completely fine, just the recording stops. It doesn't matter whether I'm using the Game Capture, Window Capture, or Monitor Capture.

Here's the log for Besiege:

Spoiler: Besiege Log

Last game capture log:
2015-09-25, 16:02:10: we're booting up:
16:02:10: CaptureThread: attached to process Besiege.exe
16:02:10: D3D9 Present
16:02:10: D3D9EndScene called
16:02:10: D3DPRESENT_PARAMETERS {
16:02:10: BackBufferWidth: 1280
16:02:10: BackBufferHeight: 720
16:02:10: BackBufferFormat: D3DFMT_A8R8G8B8
16:02:10: BackBufferCount: 1
16:02:10: MultiSampleType: D3DMULTISAMPLE_NONE
16:02:10: MultiSampleQuality: 0
16:02:10: SwapEffect: D3DSWAPEFFECT_DISCARD
16:02:10: hDeviceWindow: 2164104
16:02:10: Windowed: true
16:02:10: EnableAutoDepthStencil: false
16:02:10: AutoDepthStencilFormat: D3DFMT_D24S8
16:02:10: Flags: None
16:02:10: FullScreen_RefreshRateInHz: 0
16:02:10: PresentationInterval: 2147483648
16:02:10: };
16:02:10: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:11: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:11: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:11: successfully set up d3d9 hooks
16:02:11: D3D9Present called
16:02:11: WARNING: Another hook is already present while trying to hook opengl32.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:11: GL Present
16:02:11: DirectDraw Present
16:02:11: (half life scientist) everything.. seems to be in order
16:02:11: DoD3D9GPUHook: success
16:02:11: D3DSURFACE_DESC {
16:02:11: Format: D3DFMT_A8R8G8B8
16:02:11: Type: D3DRTYPE_SURFACE
16:02:11: Usage: D3DUSAGE_RENDERTARGET
16:02:11: Pool: D3DPOOL_DEFAULT
16:02:11: MultiSampleType: D3DMULTISAMPLE_NONE
16:02:11: MultiSampleQuality: 0
16:02:11: Width: 1280
16:02:11: Height: 720
16:02:11: };
16:02:11: successfully capturing d3d9 frames via GPU
16:02:54: D3D9Reset called
16:02:54: ---------------------- Cleared D3D9 Capture ----------------------
16:02:54: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:54: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:54: WARNING: Another hook is already present while trying to hook d3d9.dll, hook target is unknown. If you experience crashes, try disabling the other hooking application
16:02:54: successfully set up d3d9 hooks
16:02:54: D3D9EndScene called
16:02:54: D3D9Present called
16:02:54: DoD3D9GPUHook: success
16:02:54: D3DSURFACE_DESC {
16:02:54: Format: D3DFMT_A8R8G8B8
16:02:54: Type: D3DRTYPE_SURFACE
16:02:54: Usage: D3DUSAGE_RENDERTARGET
16:02:54: Pool: D3DPOOL_DEFAULT
16:02:54: MultiSampleType: D3DMULTISAMPLE_NONE
16:02:54: MultiSampleQuality: 0
16:02:54: Width: 1280
16:02:54: Height: 720
16:02:54: };
16:02:54: successfully capturing d3d9 frames via GPU
16:03:39: ---------------------- Cleared D3D9 Capture ----------------------
16:03:39: received restart event, capturing
16:03:39: DoD3D9GPUHook: success
16:03:39: D3D9EndScene called
16:03:39: D3D9Present called
16:03:40: D3DSURFACE_DESC {
16:03:40: Format: D3DFMT_A8R8G8B8
16:03:40: Type: D3DRTYPE_SURFACE
16:03:40: Usage: D3DUSAGE_RENDERTARGET
16:03:40: Pool: D3DPOOL_DEFAULT
16:03:40: MultiSampleType: D3DMULTISAMPLE_NONE
16:03:40: MultiSampleQuality: 0
16:03:40: Width: 1280
16:03:40: Height: 720
16:03:40: };
16:03:40: successfully capturing d3d9 frames via GPU
16:04:00: ---------------------- Cleared D3D9 Capture ----------------------
16:04:00: received restart event, capturing
16:04:01: DoD3D9GPUHook: success
16:04:01: D3D9EndScene called
16:04:01: D3D9Present called

Here's the log from Blender:

Spoiler: Blender Log

Last game capture log:
2015-09-25, 16:09:10: we're booting up:
16:09:10: CaptureThread: attached to process blenderplayer.exe
16:09:10: GL Present
16:09:10: DirectDraw Present
16:09:10: (half life scientist) everything.. seems to be in order
16:09:10: SwapBuffers(1224808643) Called
16:09:10: NV Capture available
16:09:10: FBO available
16:09:10: setting up gl data
16:09:10: share device: 202726024
16:09:10: share texture: 194149168
16:09:10: share device handle: 3630210238
16:09:10: share texture handle: 3754664674
16:09:10: DoGLGPUHook: success
16:09:10: wglSwapBuffers(1224808643) Called
16:09:13: stop requested, terminating gl capture
16:09:13: ---------------------- Cleared OpenGL Capture ----------------------
16:09:13: wglSwapBuffers(1224808643) Called
16:09:13: setting up gl data
16:09:13: SwapBuffers(1224808643) Called
16:09:15: wglDeleteContext Called
16:09:15: ---------------------- Cleared OpenGL Capture ----------------------

I'm not sure if these are related, but the result is the same.

 

[Harold]

And the obs crashlog?

 

[Skeletonbane]

OBS never crashed, just the recording.

Unless that counts, in which case where do I find that?

 

[Skeletonbane]

I'm no expert (or even a novice), but looking at the logs seems to indicate that something other than me called for the recording to stop. Is there something that would do this normally?

 

[R1CH]

Those are incomplete logs, please include the full OBS log, not just the game capture log.

 

[Skeletonbane]

Too many characters for a message, uploading as an attachment.

 

[Skeletonbane]

Oh right, should probably mention which is which.

2015-09-25-1600-58 is Besiege.

2015-09-25-1608-49 is Blender.

 

[Skeletonbane]

Nevermind, I've solved the problem myself. By looking over the logs, I guessed that something in the recorded program was triggering my "stop recording" hotkey. By removing the hotkey, the recording continued without any problems.