Kodi Community Forum
WIP Windows DirectX 11 upgrade test thread - Printable Version

Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32)
+--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93)
--- Thread: WIP Windows DirectX 11 upgrade test thread (/showthread.php?tid=218274)



RE: Windows DirectX 11 upgrade test thread - narvatu - 2015-06-14

Yes, it do the job. In Zotac AD02 at least. Tomorrow i see it in Revo.
Thanks

PD: I do not touch these setting or file. Is a normal installation next->next->next->run


RE: Windows DirectX 11 upgrade test thread - Martijn - 2015-06-14

(2015-06-14, 21:49)narvatu Wrote: Yes, it do the job. In Zotac AD02 at least. Tomorrow i see it in Revo.
Thanks

PD: I do not touch these setting or file. Is a normal installation next->next->next->run

That files comes from somewhere as we have never added that.


RE: Windows DirectX 11 upgrade test thread - fritsch - 2015-06-14

This advancedsettings.xml did not have default content. As DR 1 is considered highly unsafe: http://kodi.wiki/view/HOW-TO:Modify_dirty_regions#Settings_explained

3 is default.

But offtopic: DR 1 is broken everywhere.


RE: Windows DirectX 11 upgrade test thread - narvatu - 2015-06-14

mmm
I format HD when install win10
Movies are in NAS with .nfo
I do not understand nothing


RE: Windows DirectX 11 upgrade test thread - Shine - 2015-06-16

(2015-06-10, 22:04)afedchin Wrote: @Ace
Thanks. Unfortunately it seems a driver issue. the log has nothing that might indicate an issue. I'll try to reproduce the issue with my Intel GPU.

Happens here as well (Win7x64, Intel HD4600), but always, not just after resuming from sleep/hibernate. Flickering is only in the GUI. Also, stuttering RSS scroller. No flickering during video playback, but still stuttering. This has been the same ever since I first tried the DX11 builds, ie. for the past at least 2 driver versions. Only tested using SW decode and Pixel Shader rendering (both HQ and LQ). I think I never tried a different setting.
Debug log shows nothing indeed, which is why I didn't report earlier. But now that others report a similar issue, here's my "me too" ;-)


RE: Windows DirectX 11 upgrade test thread - afedchin - 2015-06-16

@Shine
try with disabled 'Use fullscreen window' setting.


RE: Windows DirectX 11 upgrade test thread - Shine - 2015-06-17

I'm always using true full screen. The problem happens when using true full screen as well as full screen window, though.


RE: Windows DirectX 11 upgrade test thread - afedchin - 2015-06-17

@Shine,
But still, can you provide a Debug Log?


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2015-06-17

hi,
i tested today with amd a6 richland apu, catalyst 14.9 and win 8.1 and i noticed two problems:

1) deinterlacing (live tv) didnt work (deinterlacing is greyed out).
2) played some files with 23.976 hz. the info jumps between 23.8x and 24.xx hz. but i didnt noticed any stutter, dropped frames....

here is a debug log
http://pastebin.com/MevHGUhE


RE: Windows DirectX 11 upgrade test thread - afedchin - 2015-06-17

@Ed76,
1. DX11 selects deinterlacing method (if its enabled) automacality. But your drivers for DirectX 11 has no support any deinterlacing method.
Code:
18:59:44 T:3016  NOTICE: DXVA::CProcessorHD::InitProcessor - Supported deinterlace methods: Blend:no, Bob:no, Adaptive:no, MoComp:no.
2. frame rate is calculated not accurate. If there are no dropped frames then all work fine.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2015-06-17

yes, i have also seen that entry in the log files. but what does it mean exactly? what can i do? are you sure amd cards doesnt support deinterlacing with dx11? i cant believe. i played a little with deinterlacing setting within catalyst but without success.


RE: Windows DirectX 11 upgrade test thread - Shine - 2015-06-17

(2015-06-17, 12:17)afedchin Wrote: @Shine,
But still, can you provide a Debug Log?

Thanks for requesting that log, since it made me test a little more. I've actually found something in the log now.
  • Apparently, the flickering happens on secondary monitor (ie. TV) only
  • Happens in "full screen window" mode only - your guess was spot on!
  • In my case, Kodi fails to switch to true full screen mode (most of the time, not always) and therefore keeps whatever resolution and refresh rate was currently set on the secondary screen (1080p50 in my case)
  • When this happens, manually changing resolution in Kodi settings does not work either
  • Moving Kodi to screen #1 and back to screen #2 usually fixes it - until I restart Kodi

Only log excerpt for now, as in the past half hour while I was testing, I wasn't able to reproduce this using a clean profile to get you an uncluttered log...

log excerpt when working:
Code:
22:04:21 T:1856  NOTICE: Checking resolution 17
22:04:21 T:1856   DEBUG: CWinEventsWin32::WndProc: window resize event
22:04:21 T:1856   DEBUG: CWinEventsWin32::WndProc: window move event
22:04:21 T:1856   DEBUG: CWinSystemWin32::ResizeInternal - resizing due to size change (0,0,1920,1080 fullscreen)->(1920,0,3840,1080 fullscreen)
22:04:21 T:1856   DEBUG: CWinEventsWin32::WndProcWindow is active
22:04:21 T:1856   DEBUG: CWinEventsWin32::WndProc: window move event
22:04:21 T:1856   DEBUG: CRenderSystemDX::InitRenderSystem - Initializing D3D11 Factory...
22:04:22 T:1856   DEBUG: CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY2 output.
22:04:22 T:1856   DEBUG: CRenderSystemDX::SetMonitor - Selected Intel(R) HD Graphics 4600 adapter.
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateDevice - on adapter Intel(R) HD Graphics 4600 (VendorId: 0x8086 DeviceId: 0x412) with feature level 0x9300.
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_DXT
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_NPOT
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_DXT_NPOT
22:04:22 T:1856   DEBUG: CD3DVertexShader::CreateInternal - Create the vertex shader.
22:04:22 T:1856   DEBUG: CD3DVertexShader::CreateInternal - create the input layout.
22:04:22 T:1856   DEBUG: CD3DPixelShader::CreateInternal - Create the pixel shader.
22:04:22 T:1856   DEBUG: Previous line repeats 10 times.
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateWindowSizeDependentResources - (Re)Create window size (1920x1080) dependent resources.
22:04:22 T:1856   DEBUG: CRenderSystemDX::CreateWindowSizeDependentResources - Creating swapchain in Mono mode.
22:04:22 T:1856   DEBUG: CWinSystemWin32::SetFullScreenEx (true fullscreen) on screen 1 with size 1920x1080, refresh 50.000000
22:04:22 T:1856   DEBUG: CRenderSystemDX::SetFullScreenInternal - Current display mode is: [email protected]
22:04:22 T:1856   DEBUG: CRenderSystemDX::SetFullScreenInternal - Found matched mode: [email protected]

log excerpt when not working:
Code:
22:00:48 T:4296  NOTICE: Checking resolution 17
22:00:49 T:4296   DEBUG: CWinEventsWin32::WndProc: window resize event
22:00:49 T:4296   DEBUG: CWinEventsWin32::WndProc: window move event
22:00:49 T:4296   DEBUG: CWinSystemWin32::ResizeInternal - resizing due to size change (0,0,1920,1080 fullscreen)->(1920,0,3840,1080 fullscreen)
22:00:49 T:4296   DEBUG: CWinEventsWin32::WndProcWindow is active
22:00:49 T:4296   DEBUG: CWinEventsWin32::WndProc: window move event
22:00:49 T:4296   DEBUG: CRenderSystemDX::InitRenderSystem - Initializing D3D11 Factory...
22:00:49 T:4296   DEBUG: CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY2 output.
22:00:49 T:4296   DEBUG: CRenderSystemDX::SetMonitor - Selected Intel(R) HD Graphics 4600 adapter.
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateDevice - on adapter Intel(R) HD Graphics 4600 (VendorId: 0x8086 DeviceId: 0x412) with feature level 0x9300.
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_DXT
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_NPOT
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateDevice - RENDER_CAPS_DXT_NPOT
22:00:49 T:4296   DEBUG: CD3DVertexShader::CreateInternal - Create the vertex shader.
22:00:49 T:4296   DEBUG: CD3DVertexShader::CreateInternal - create the input layout.
22:00:49 T:4296   DEBUG: CD3DPixelShader::CreateInternal - Create the pixel shader.
22:00:49 T:4296   DEBUG: Previous line repeats 10 times.
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateWindowSizeDependentResources - (Re)Create window size (1920x1080) dependent resources.
22:00:49 T:4296   DEBUG: CRenderSystemDX::CreateWindowSizeDependentResources - Creating swapchain in Mono mode.
22:00:49 T:4296   DEBUG: CWinSystemWin32::SetFullScreenEx (true fullscreen) on screen 1 with size 1920x1080, refresh 50.000000
22:00:49 T:4296   DEBUG: CRenderSystemDX::SetFullScreenInternal - Switching swap chain to fullscreen state.
22:00:49 T:4296   ERROR: CRenderSystemDX::SetFullScreenInternal - Failed switch full screen state: 887A0022 - DXGI_ERROR_NOT_CURRENTLY_AVAILABLE (The requested functionality is not supported by the device or the driver.).
22:00:49 T:4296   DEBUG: CRenderSystemDX::SetFullScreenInternal - Current display mode is: [email protected]
22:00:49 T:4296   DEBUG: CRenderSystemDX::SetFullScreenInternal - Found matched mode: [email protected]

Hope this helps.


RE: Windows DirectX 11 upgrade test thread - afedchin - 2015-06-17

@Ed76,
The log entry contains information about what the driver reports to the application (Kodi in our case). This means that the driver doesn't support these methods of deinterlacing. That's all. You can belive or not, it's your right. There is a difference between Direct3D9 API and D3D11 API and drivers support these APIs in different ways. I suggest you try Windows 10 Insider Preview and as a result the new drivers.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2015-06-17

ok, maybe i try the newest beta driver for win 8.1. win10 is to experimental/unsafe for me at the moment because this is the htpc in our living room. i will report the results.


RE: Windows DirectX 11 upgrade test thread - afedchin - 2015-06-17

@Shine
Please upload full logs to pastebin.com or xbmclogs.com in any case.

There are many reasons why DXGI_ERROR_NOT_CURRENTLY_AVAILABLE error occurs:
* Another application is already in fullscree.
* The application window does not have focus.
* The application window is occluded.

Perhaps this occurs because you use second display. Try to setup your TV as primary display.