Bug Report Black Screen in OBS for LOL Main Menu
- Thread starter SViper
- Start date
You should always post a log file for bug reports. https://obsproject.com/forum/threads/problem-make-sure-to-post-a-log-and-or-crash-dump-howto.97/
SViper
New Member
It supported Windows 10 normally till some kinda OBS update.
Code:
Last game capture log:
2015-03-25, 15:52:21: we're booting up:
15:52:21: CaptureThread: attached to process League of Legends.exe
15:52:21: D3D9 Present
15:52:21: DXGI Present
15:52:21: GL Present
15:52:21: DirectDraw capture: Windows 8 not supported yet
15:52:21: (half life scientist) everything.. seems to be in order
15:52:21: D3D9EndScene called
15:52:21: D3DPRESENT_PARAMETERS {
15:52:21: BackBufferWidth: 1366
15:52:21: BackBufferHeight: 768
15:52:21: BackBufferFormat: D3DFMT_X8R8G8B8
15:52:21: BackBufferCount: 1
15:52:21: MultiSampleType: D3DMULTISAMPLE_NONE
15:52:21: MultiSampleQuality: 0
15:52:21: SwapEffect: D3DSWAPEFFECT_DISCARD
15:52:21: hDeviceWindow: 3213780
15:52:21: Windowed: false
15:52:21: EnableAutoDepthStencil: true
15:52:21: AutoDepthStencilFormat: D3DFMT_D24S8
15:52:21: Flags: D3DPRESENTFLAG_DISCARD_DEPTHSTENCIL
15:52:21: FullScreen_RefreshRateInHz: 60
15:52:21: PresentationInterval: 0
15:52:21: };
15:52:21: successfully set up d3d9 hooks
15:52:21: D3D9Present called
15:52:21: DoD3D9CPUHook: success
15:52:29: D3D9Reset called
15:52:29: ---------------------- Cleared D3D9 Capture ----------------------
15:52:29: successfully set up d3d9 hooks
15:52:29: D3D9EndScene called
15:52:29: D3D9Present called
15:52:29: DoD3D9CPUHook: success
15:52:29: DirectDraw capture: Windows 8 not supported yet
15:52:29: successfully capturing d3d9 frames via CPU
15:52:54: D3D9Reset called
15:52:54: ---------------------- Cleared D3D9 Capture ----------------------
15:52:54: successfully set up d3d9 hooks
15:52:54: D3D9EndScene called
15:52:54: D3D9Present called
15:52:54: DoD3D9CPUHook: success
15:52:55: successfully capturing d3d9 frames via CPU
15:52:58: DirectDraw capture: Windows 8 not supported yet
15:53:02: ---------------------- Cleared D3D9 Capture ----------------------
15:53:02: D3D9EndScene called
15:53:02: D3D9Present called
15:53:02: DirectDraw capture: Windows 8 not supported yet
15:53:04: D3D9Reset called
15:53:04: ---------------------- Cleared D3D9 Capture ----------------------
15:53:04: successfully set up d3d9 hooks
15:53:04: D3D9EndScene called
15:53:04: D3D9Present called
15:53:06: DirectDraw capture: Windows 8 not supported yet
15:54:18: received restart event, capturing
15:54:18: DoD3D9CPUHook: success
15:54:49: D3D9Reset called
15:54:49: ---------------------- Cleared D3D9 Capture ----------------------
15:54:49: successfully set up d3d9 hooks
15:54:49: D3D9EndScene called
15:54:49: D3D9Present called
15:54:49: DoD3D9CPUHook: success
15:54:49: successfully capturing d3d9 frames via CPU
15:54:52: DirectDraw capture: Windows 8 not supported yet
15:56:58: ---------------------- Cleared D3D9 Capture ----------------------
15:56:58: D3D9EndScene called
15:56:58: D3D9Present called
15:57:02: DirectDraw capture: Windows 8 not supported yet
Sapiens
Forum Moderator
Well, no, if it happened to work in Windows 10 then that's great, but that isn't the same as being supported. You should expect problems like this to crop up with a preview build of an OS, and not expect timely fixes to problems like this until much closer to release (unless you or someone else wants to contribute the fixes of course).
SViper
New Member
Roger that.:):P