why am i getting "Attempting DWrite without D2D support" , it was working perfectly before i upgraded to 44??
i upgraded from 42 to 44. before the upgrade everything worked fine and i had full hardware acceleration. directwrite was enabled, direct2d was my canvas and backends, i had asynchronous pan/zoom.
everything was working perfectly until i installed 44. now i'm getting (#0) Error: Attempting DWrite without D2D support. even though it is says direct write enabled. - true. and i can no longer get direct2d azurecanvasbackend and azurecontentbackend.
NVIDIA GeForce 8400 GS nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
already got: gfx.direct2d.force-enabled true
layers.acceleration.force-enabled true layers.async-pan-zoom.enabled true
anyidea how to fix it back to the way it was??
모든 댓글 (2)
You posted with a weird Firefox 40 version according to the System Detail list next to your question.
- Mozilla/5.0 (Windows NT 6.3; x64; rv:40.0) Gecko/20100101 Firefox/40.1
Are you using an extension to modify the user agent?
Did you check the graphics section on the Help > Troubleshooting Information page?
Are there any special crash-guard prefs (gfx.gfx.crash-guard) that show a problem?
no the question is as posted exactly as is what's mentioned above. im not on that browser or that computer because firefox is acting weird.
this is a different computer running gnightly, which is running perfectly i might add. it's actually a really old gnightly like 32, had to mod the user string so websites leave me alone. so any extension modifying my user agent is irrelevant. which no i'm not. but it interests you can modify general.useragent.override to anything you like.
i did check that graphics section on the help > Troubleshooting information page which is where i saw that direct2d backends weren't working, the error message, "(#0) Attempting DWrite without D2D support", and that all my hardware acceleration was infact enabled....
now what i don't know is what the crash-guard prefs mean, and or how to interpret that information, as 44 is the only version i've ever seen them in before.
they are as follows:
gfx.crash-guard.d3d11layers.appVersion;44.0 gfx.crash-guard.d3d11layers.deviceID;0x06e4 gfx.crash-guard.d3d11layers.driverVersion;9.18.13.4144 gfx.crash-guard.d3d11layers.feature-d2d;true gfx.crash-guard.d3d11layers.feature-d3d11;true gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle;true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11;false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp;false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11;true gfx.crash-guard.status.d3d11layers;2 gfx.crash-guard.status.d3d9video;2 gfx.crash-guard.status.glcontext;2