Kodi Community Forum

(2015-02-25, 21:51)thecYrus Wrote: [ -> ]drag & drop the kodi window from one GPU to another crashes it. (it's a 3 screens setup with 2 GPUs)

log: http://1drv.ms/1LEdiqP
crashlog: http://1drv.ms/1BVBfu3
stacktrace: http://1drv.ms/1BVBlBN

Thanks but your log is not a Debug Log. Please enable debug logging then try to reproduce issue.

(2015-02-25, 22:22)thecYrus Wrote: [ -> ]It's just that the current build doesn't handle GPU "remove" events. (DXGI_ERROR_DEVICE_REMOVED)

It does but this scenario is not tested. I have no possibility to test it.

(2015-02-25, 23:01)afedchin Wrote: [ -> ]

(2015-02-25, 21:51)thecYrus Wrote: [ -> ]drag & drop the kodi window from one GPU to another crashes it. (it's a 3 screens setup with 2 GPUs)

log: http://1drv.ms/1LEdiqP
crashlog: http://1drv.ms/1BVBfu3
stacktrace: http://1drv.ms/1BVBlBN

Thanks but your log is not a Debug Log. Please enable debug logging then try to reproduce issue.

yeah sorry, debug wasn't enabled anymore. file updated. (http://1drv.ms/1LEdiqP)

22:15:22 T:9124 DEBUG: CWinEventsWin32::WndProc: window move event
22:15:22 T:9124 DEBUG: Previous line repeats 54 times.
22:15:22 T:9124 ERROR: CGUIFontTTFDX::CreateVertexBuffer - Failed to create vertex buffer.
22:15:22 T:9124 ERROR: Previous line repeats 3 times.
22:15:22 T:9124 DEBUG: CRenderSystemDX:resentRenderImpl - device removed
22:15:22 T:9124 ERROR: DXGI_ERROR_DEVICE_REMOVED

New build:

Fixed:

• Fixed resurrection on device changing.
  
• GUIFontTTFDX: properly release buffers at destroying font.
  

Download link in the first post.

@thecYrus
Please try reproduce issue with new build. Thanks.

Not so good
http://pastebin.com/Rw2d2ama

Quote:18:39:13 T:5004 DEBUG: CWinSystemWin32::ResizeInternal - resizing due to size change (0,0,809,482)->(228,241,1053,761)
18:39:13 T:5004 DEBUG: CWinEventsWin32::WndProcWindow is active
18:39:13 T:5004 DEBUG: CWinEventsWin32::WndProc: window move event
18:39:13 T:5004 DEBUG: CWinEventsWin32::WndProc: window resize event
18:39:13 T:5004 DEBUG: CRenderSystemDX::InitRenderSystem - Initializing D3D11 Factory...
18:39:13 T:5004 DEBUG: CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY2 output.
18:39:13 T:5004 DEBUG: CRenderSystemDX::SetMonitor - Selected NVIDIA GeForce GTX 275 adapter.
18:39:13 T:5004 DEBUG: CRenderSystemDX::CreateDevice - First try to create device failed with error: 80070057 - E_INVALIDARG (De parameter is onjuist.

).
18:39:13 T:5004 DEBUG: CRenderSystemDX::CreateDevice - Trying to create device with lowest feature level (1).
18:39:13 T:5004 DEBUG: CRenderSystemDX::CreateDevice - on adapter NVIDIA GeForce GTX 275 with feature level 37632
18:39:13 T:5004 ERROR: CRenderSystemDX::CreateDevice - Creating swap chain failed with error: 8007000E - E_OUTOFMEMORY (Onvoldoende opslagruimte beschikbaar om deze bewerking te voltooien.

).
18:39:13 T:5004 FATAL: CApplication::Create: Unable to init rendering system

(2015-02-26, 15:38)afedchin Wrote: [ -> ]New build:

Fixed:

• Fixed resurrection on device changing.
  
• GUIFontTTFDX: properly release buffers at destroying font.
  

Download link in the first post.

@thecYrus
Please try reproduce issue with new build. Thanks.

it works. No crash while changing the screen anymore. But it freezes for a couple of seconds. I've updated the logfile again. Maybe you can see something. But thanks anyway!

http://1drv.ms/1LEdiqP

just found another thing. switching to fullscreen-mode (alt+enter on windows) moves kodi to the screen which is set as primary in windows. it doesn't stay on the screen where it's active.

@Martijn
Strange. Nothing critical changed in this part. Does issue exist with prev build?

@thecYrus
In your log device was changing three times within three seconds: from initial 9800GT to GF210 (at 19:14:27), then back to 9800GT (at 19:14:28), then again to GF210 (at 19:14:30). I know what Kodi freezes during recreating all resources but I can do nothing with this. DX11 implementation uses much more resources (textures, buffers, states) which require recreating after changing adapter.

Edit:

(2015-02-26, 20:32)thecYrus Wrote: [ -> ]just found another thing. switching to fullscreen-mode (alt+enter on windows) moves kodi to the screen which is set as primary in windows. it doesn't stay on the screen where it's active.

You can change monitor in fullscreen-mode in the Kodi settings.

Last one that worked was from 20th

@Martijn
Can you try with current branch? If issue is resolved I'll publish new build.

All fine now.

Playback on the one that wouldn't start before (and now does) http://pastebin.com/xc6BhMGF
Playback on the one that had no video in fullscreen (and now has) http://xbmclogs.com/pzjmla4vs

@Martijn,
Not all so good. I saw in your first log what the dxva not works in general (decoding and rendering). Please can you check what your video driver is WDDM1.2?

(2015-02-27, 08:37)afedchin Wrote: [ -> ]@Martijn,
Not all so good. I saw in your first log what the dxva not works in general (decoding and rendering). Please can you check what your video driver is WDDM1.2?

If you can tell how, sure. Finding out seems a real bitch.

The win7 computer with NIVIA GTX275 using the \ key for switching fullscreen mode switches my screen to a lower res.
http://pastebin.com/jTJcicqk

CWinSystemWin32::SetFullScreen (windowed) on screen 0 with size 635x374, refresh 0.000000

Using new build from this morning

(2015-02-27, 19:23)Martijn Wrote: [ -> ]

(2015-02-27, 08:37)afedchin Wrote: [ -> ]Please can you check what your video driver is WDDM1.2?

If you can tell how, sure. Finding out seems a real bitch.

dxdiag.exe should be able to tell that. Check the second tab. http://i.imgur.com/WfHNfwI.png (image is from Finnish version)

it's WDDM 1.1 (Seems like that's almost standaard for Win7).