1260574 - New and unexpected Windows 10 configuration - let's make sure we understand what this is

Status: NEW

(Core :: Graphics, defect, P3)

Description

[Milan Sreckovic [:milan] (needinfo for best results)]

In bug 1256728 comment 12, the user shows about:support with some unexpected values.  Vendor ID mismatch between Nvidia and Microsoft, ANGLE reporting Microsoft Basic Render Driver Direct3D11, and we get D2D1.1 and D3D11 OMTC.
Is this WARP under a different name?

> Adapter Description: Adaptador de pantalla básico de Microsoft
> Adapter Drivers: Unknown
> Adapter RAM: 0
> Asynchronous Pan/Zoom: none
> Device ID: 0x01d3
> Direct2D Enabled: true
> DirectWrite Enabled: true (10.0.10586.0)
> Driver Date: 6-21-2006
> Driver Version: 10.0.10586.0
> GPU #2 Active: false
> GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
> Subsys ID: 00000000
> Supports Hardware H264 Decoding: No; Failed to create D3D11 device for decoder; CheckDeviceFormatConversion failed with error 8876086A
> Vendor ID: 0x10de
> WebGL Renderer: Google Inc. -- ANGLE (Microsoft Basic Render Driver Direct3D11 vs_5_0 ps_5_0)
> windowLayerManagerRemote: true
> AzureCanvasAccelerated: 0
> AzureCanvasBackend: direct2d 1.1
> AzureContentBackend: direct2d 1.1
> AzureFallbackCanvasBackend: cairo
> (#0) Error: VendorIDMismatch V 0x10de 0x1414

Comment 1

[Milan Sreckovic [:milan] (needinfo for best results)]

According to :jgilbert, this is the WARP rendering string.

Comment 2

[Kelsey Gilbert [:jgilbert]]

This is my WARP GL_RENDERER string: "Google Inc. -- ANGLE (Microsoft Basic Render Driver Direct3D11 vs_5_0 ps_5_0)", so this is probably WARP.

Note that WARP is broken on Nightly48 right now: Bug 1260944.

Comment 3

[Trevor Rowbotham [:rowbot]]

I thought that accelerated layers were blacklisted on all drivers that aren't Intel, Nvidia, or AMD, has that changed? If it hasn't, then I guess they are forcing accelerated layers on to get D3D11 (OMTC), which seems like a very broken configuration when combined with the generic Microsoft Display Driver.  The last driver released for that card was February 24, 2015 and didn't support anything above Windows 8 (not 8.1).