MPC Video Renderer 0.7.0 dev not supporting DXVA2 in Direct3D11 mode

After upgrading to K-Lite Codec Pack 17.7.5, I noticed that H/W acceleration doesn't work on DXVA2 Native when using the MPC Video Renderer, in which Direct3D11 mode is turned on in its settings. Copy-back works fine as well as D3D11VA. After some troubleshooting, I noticed the renderer itself might be the culprit, so I submitted an issue here: https://github.com/Aleksoid1978/VideoRenderer/issues/96

Now the thing is that if MPC VR 0.7.0 gets released officially (and the latest version of the codec pack uses the nightly builds of it), it will be the first version dropping support for the DXVA2 (Native) decoder in Direct3D11 mode, so you have to use D3D11VA for that. (MPC-BE's video decoder has some sort of a hybrid hardware decoder option selected by default - D3D11VA/DXVA2. It works seamlessly when [de]selecting Direct3D11 mode in the renderer settings. If it's on - then it uses D3D11VA. If it's off - it uses DXVA2.)

---

I was wondering if a notice can be added to the Help documents during setup, or on the setup itself (as you choose the video renderer before choosing the hardware decoder) that DXVA2 (Native) isn't supported with the renderer if one enables Direct3D11 in the renderer settings. Direct3D9Ex mode works fine, but I don't really like waiting a few moments when entering/exiting fullscreen. (which I don't experience while using Direct3D11 mode).

The installer already tries to match it up correctly. Either DXVA2+D3D9 or D3D11.

D3D11 is preferred on modern GPUs (that support HEVC).

Admin wrote:The installer already tries to match it up correctly. Either DXVA2+D3D9 or D3D11.

D3D11 is preferred on modern GPUs (that support HEVC).

I see. I assume the matching affects both MPC-HC and other DirectShow apps config alike?
Nevertheless, I manually set to D3D11VA myself for my HD Graphics 4600. Seems to perform the same, didn't see any perf hits when compared to dxva2n/mpc-vr, so I assume I should be fine with this config.