I've confirmed that without D3D_FEATURE_LEVEL_9_3 we instead fail to create the device entirely, which will trigger us to retry without the video support flag and give us the old behaviour. Can we just drop D3D_FEATURE_LEVEL_9_3 from mFeatureLevels to stop this from happening? It really seems like allowing a feature level 9.3 device to be created isn't helpful since we can't use it for anything. * We disable D3D11_HW_ANGLE ("RenderTargetViews need recreating") because of the check at choco download ddu -internalize -version17.0.7.2 -sourcehttps. "Direct3D11 device does not support texture sharing" in the log. Human moderators who give final review and sign off More detail at Security and Moderation. * We fail the check at and disable texture sharing (h/w accelerated video decoding and direct2d). This behaviour is documented for feature level 9 graphics devices here. * When we query the DXGIAdapter for the VendorId it returns 0 ("VendorIDMismatch V 0x10de 0" in the log). From "Dual-source color blend not supported (any SrcBlend or DestBlend with SRC1 in the name)" * We fail to initialize CompositorD3D11 since it doesn't support our component alpha blend mode ("create component blender failed" from the log). So it looks like if we request video support on the d3d11 device when on Windows 7 (< WDDM 1.2), then it forces the device to be created at a 9.x feature level (if specified in the feature level list) - See D3D11_CREATE_DEVICE_VIDEO_SUPPORT on.
0 kommentar(er)
