1383295 - No Direct2D using Remote Desktop Connection with RemoteFX etc....Blocked for your graphics card because of unresolved driver issues.

Status: UNCONFIRMED

(Core :: Graphics, defect, P3)

Description

[MTRX]

Attachment: firefoxd2dfail-RDP.bmp

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161129173726

Steps to reproduce:

logged in to my laptop remotely using WindowsRDP,  opened firefox,  and opened troubleshooting information to check on hardware acceleration.


Actual results:

troubleshooting information reports no direct2d,  no azure direct2d acceleration,  various details marked as blocklist for graphics driver.  o_O

normally the browser has perfect hardware acceleration.  Under WindowsRDP(hardware accelerated),  hardware acceleration fails for firefox,  even though it's working in RDP.  


Features
Compositing	Direct3D 9
Asynchronous Pan/Zoom	wheel input enabled
WebGL Renderer	WebGL creation failed: * Error during native OpenGL init. * Error during native OpenGL init. * Exhausted GL driver options.
WebGL2 Renderer	(no info)
Hardware H264 Decoding	No; Hardware video decoding disabled or blacklisted
Audio Backend	winmm
Direct2D	Blocked for your graphics card because of unresolved driver issues.
DirectWrite	true (6.2.9200.16492)
GPU #1
Active	Yes
Description	RDPDD Chained DD
Vendor ID	0x0000
Device ID	0x0000
Drivers	RDPDD
Subsys ID	00000000
RAM	Unknown
GPU #2
Active	No
Description	Intel(R) HD Graphics 4000
Vendor ID	0x8086
Device ID	0x0166
Driver Version	9.17.10.2849
Driver Date	9-2-2012
Drivers	igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Subsys ID	0000000c
RAM	Unknown
Diagnostics
AzureCanvasAccelerated	0
AzureCanvasBackend	cairo
AzureContentBackend	cairo
AzureFallbackCanvasBackend	none
failures	[GFX1-]: Attempting DWrite without D2D support
Decision Log
HW_COMPOSITING	
force_enabled by user: Force-enabled by pref
D3D11_COMPOSITING	
Blocklisted; failure code BLOCKLIST_FEATURE_FAILURE_UNKNOWN_DEVICE_VENDOR
D3D9_COMPOSITING	
disabled by default: Disabled by default
force_enabled by user: Hardware compositing is force-enabled
Blocklisted; failure code BLOCKLIST_FEATURE_FAILURE_UNKNOWN_DEVICE_VENDOR
DIRECT2D	
unavailable by default: Direct2D requires Direct3D 11 compositing
D3D11_HW_ANGLE	
unavailable by default: D3D11 compositing is disabled
disabled by env: D3D11 compositing is disabled
Failure Log
(#0) Error	Attempting DWrite without D2D support
(#1) 	CP+[GFX1-]: Attempting DWrite without D2D support


Expected results:

firefox trouble shooting should show direct2d and hardware acceleration details enabled and working.

Comment 1

[MTRX]

I did find this article,  but it didn't work.

https://www.poppelgaard.com/mozilla-firefox-40-x-blocks-gpu-acceleration-for-webgl-direct2d-directwrite-with-xenapp-on-windows-2012-r22008-r2

-also the end of the article isn't exactly correct it says if it doesn't work after the adjustments then your hardware doesn't support it.

i know it's not true,  because i have all forms hardware acceleration completely enabled on both the host and client computers.  in their natural environment everything runs perfectly and fully enabled with ff.  it's only when i start an RDP session that this stuff starts happening.

honestly i don't think rdp drivers should be blocked,  because it's not hardware.  and rdp is a very dynamic situation,  and dealing with that should be left to the user in terms of testing it out and seeing if it's gonna work or not.

this guy got d2d and dwrite to work on his rig,  and we have the same setup,  accept different versions ff.  i believe we're running the same OS aswell.  Server 2008 R2.  so the RDP thing is pretty dynamic seeing as it's a totally software environment handing off hardware acceleration off to the client computer.  host computer doesn't even need a GPU in it for hardware accelerated RDP to work.  it can be a headless configuration.  so there's that.

im gonna play with spoofing vars,  and see what happens.  ill follow up once ive done more testing.  in the meantime i have all the hardware stuff set in about:config cuz that's how i run ff normally,  and everything is in perfect working order in terms of my hardware/software configuration.  -but if anyone knows of some unlisted about:config entries ill try anything i experiment with fox 24/7  and im not afraid to crash it.  it's part of the fun.

Comment 2

[MTRX]

Alright check this out.  
I went with the spoof variables and i copied over the driver data from the client machine.
running an nvidia 8400GS.  and everything is working perfectly.

D3D11 kicked in over D3D9,  dwrite is working,  and all i did was spoof the driver.


Compositing	Direct3D 11
Asynchronous Pan/Zoom	wheel input enabled
WebGL Renderer	WebGL creation failed: * Error during native OpenGL init. * Error during native OpenGL init. * Exhausted GL driver options.
WebGL2 Renderer	(no info)
Hardware H264 Decoding	Yes; Using D3D9 API
Audio Backend	winmm
Direct2D	true
DirectWrite	true (6.2.9200.16492)
GPU #1
Active	Yes
Description	RDPDD Chained DD
Vendor ID	0x10de
Device ID	0x06e4
Driver Version	9.18.13.4198
Drivers	RDPDD
Subsys ID	00000000
RAM	Unknown
GPU #2
Active	No
Description	Intel(R) HD Graphics 4000
Vendor ID	0x8086
Device ID	0x0166
Driver Version	9.17.10.2849
Driver Date	9-2-2012
Drivers	igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Subsys ID	0000000c
RAM	Unknown
Diagnostics
AzureCanvasAccelerated	0
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	none
failures	[GFX1-]: VendorIDMismatch V 0x10de 0x8086
Decision Log
HW_COMPOSITING	
force_enabled by user: Force-enabled by pref
D3D9_COMPOSITING	
disabled by default: Disabled by default
force_enabled by user: Hardware compositing is force-enabled
Failure Log
(#0) Error	VendorIDMismatch V 0x10de 0x8086

yeah my variables were a little off,  but as for everything else hardware acceleration is fully working and functional.  it was simply a matter of driver info.
so my guess is that the only reason i was getting all these errors and failures is because the RDP driver was actually blocked??  

I say unblock the RDP driver for Server 2008 R2,  cuz everything's looking good on this side,  and this guy got his working perfectly using the spoofing variables.  it would be nice to get this working without having to pump vars into my config.

hopes this helps.  until the block gets lifted,  for anyone trying this out,  get yer about:config set for hardware acceleration set how you like it,  then spoof over the driver info from your client computer,  or whatever known working config you got running,  and give it a try,  should get your hardware acceleration working on FF over RDP on Server 2008 R2 and win7 running with full hardware acceleration.  i'd goes as far as to say this most likely works on the younger versions of windows as well.  8/8.1 and server 2012,  and win10 and Server 2016.

kudos.

Comment 3

[MTRX]

oh btw all i did was spoof device vendor and driver to match the client machines actual hardware.

so here's a list of the old spoofing vars from back in the day.

SET MOZ_GFX_SPOOF_WINDOWS_VERSION=60001
SET MOZ_GFX_SPOOF_VENDOR_ID=0x8086
SET MOZ_GFX_SPOOF_DEVICE_ID=0x0046
SET MOZ_GFX_SPOOF_DRIVER_VERSION=8.15.10.2302

just changes those ='s to whatever you want.  i just copied and pasted it here.  

-also,  a lot of the spoofing howto's will tell you to do a 
“C:\Program Files (x86)\Mozilla Firefox\firefox.exe” -p -no-remote

-but i didn't.  and my remote is working perfectly.  even getting gpu ram readings in process hacker and everything,  so remote ain't bugging out at all from what i can tell.
if it **** out on you on the first try stick that commandline in your run/console,  and see if disabling remote helps.  you could also just create a shortcut to your ff binary,  and tack on the -p -no-remote.  what ever bloats your goat.

hope this helps.

Comment 4

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

What's the host version here?  We only allow acceleration in these case with Windows 8 and later - is this Windows 7, based on the user agent in comment 0?