Hardware Acceleration no longer provides font smoothing

UNCONFIRMED
Unassigned

Status

()

Core
Graphics: Text
P3
normal
UNCONFIRMED
2 years ago
5 months ago

People

(Reporter: Tandy, Unassigned)

Tracking

({fonts})

44 Branch
x86_64
Windows 7
fonts
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

Attachments

(5 attachments)

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822

Steps to reproduce:

I moved from FF 41.0.2 to 44.0.2 (clean install, not update).  With 44.0.2, I discovered that enabling Hardware Acceleration no longer provides font smoothing as it has for many versions.

As a result, many websites no longer display fonts properly.  On some sites, they will simply look skinny, while on others, they look heavily rasterized.

It should be noted that I have ClearType *disabled*, as I can't stand what it does.  If I enable ClearType, it addresses the issues in Firefox, but then makes everything else look horrible.  Having the Hardware Acceleration setting enable font smoothing specifically and only in FF was the perfect solution - but that no longer works.

Also note that this is on Win 7 x64.
(Reporter)

Updated

2 years ago
Keywords: fonts
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
(Reporter)

Comment 1

2 years ago
Created attachment 8726100 [details]
Case 1 - Problem (FF v44.0.2)
(Reporter)

Comment 2

2 years ago
Created attachment 8726101 [details]
Case 1 - Correct (FF v41.0.2)

This is how this sample looks on FF 41.0.2 (with Hardware Acceleration on).
(Reporter)

Comment 3

2 years ago
Created attachment 8726102 [details]
Case 2 - Problem (FF v44.0.2)
(Reporter)

Comment 4

2 years ago
Created attachment 8726103 [details]
Case 2 - Correct (FF v41.0.2)

This is how this sample looks on FF v41.0.2 (with Hardware Acceleration on).

Updated

2 years ago
Component: Untriaged → Graphics: Text
Product: Firefox → Core

Comment 5

2 years ago
Type about:support in the location bar and paste here the section "graphics", please.
Flags: needinfo?(thatch)
(Reporter)

Comment 6

2 years ago
Graphics
Adapter Description:			NVIDIA GeForce GTX 550 Ti
Adapter Drivers:			nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM:				1024
Asynchronous Pan/Zoom:			none
ClearType Parameters:			D [ Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50 ] D [ Gamma: 2200 Pixel Structure: R ]
Device ID:				0x1244
DirectWrite Enabled:			false (6.1.7600.16972)
Driver Date:				5-20-2011
Driver Version:				8.17.12.7533
GPU #2 Active:				false
GPU Accelerated Windows:		3/3 Direct3D 11 (OMTC)
Subsys ID:				089c196e
Supports Hardware H264 Decoding:	Yes
Vendor ID:				0x10de
WebGL Renderer:				Google Inc. -- ANGLE (NVIDIA GeForce GTX 550 Ti Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote:		true
AzureCanvasBackend:			skia
AzureContentBackend:			cairo
AzureFallbackCanvasBackend:		cairo
AzureSkiaAccelerated:			0
Flags: needinfo?(thatch)

Comment 7

2 years ago
Your Nvidia drivers are too old, you need to update them to the latest version (362.00 WHQL Release Date: 2016.3.1):
http://www.nvidia.com/download/driverResults.aspx/99196/en-us
(Reporter)

Comment 8

2 years ago
We're not talking about cutting edge gaming graphics, we're only talking about font smoothing.  Did something change since v41.0.2 regarding the technique being used?

Comment 9

2 years ago
The issue is surely due to the old drivers, HWA is regularly patched in Firefox and 2011 is too old for drivers, especially with a fairly recent GPU like yours.
(Reporter)

Comment 10

2 years ago
I just updated to the latest version in order to test the issue.  The problems are all still there, so the drivers had nothing to do with it.



--------------------------------------
Graphics

Adapter Description:			NVIDIA GeForce GTX 550 Ti
Adapter Drivers:			nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM:				1024
Asynchronous Pan/Zoom:			none
ClearType Parameters:			D [ Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50 ] D [ Gamma: 2200 Pixel Structure: R ]
Device ID:				0x1244
DirectWrite Enabled:			false (6.1.7600.16972)
Driver Date:				2-23-2016
Driver Version:				10.18.13.6200
GPU #2 Active:				false
GPU Accelerated Windows:		4/4 Direct3D 11 (OMTC)
Subsys ID:				089c196e
Supports Hardware H264 Decoding:	Yes
Vendor ID:				0x10de
WebGL Renderer:				Google Inc. -- ANGLE (NVIDIA GeForce GTX 550 Ti Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote:		true
AzureCanvasBackend:			skia
AzureContentBackend:			cairo
AzureFallbackCanvasBackend:		cairo
AzureSkiaAccelerated:			0

Comment 11

2 years ago
Did you enable HWA in Firefox? DirectWrite is disabled in your profile.
(Reporter)

Comment 12

2 years ago
Created attachment 8726255 [details]
Confirmation of HWA setting

This shows that HWA is indeed enabled, and the background window shows the pixelated font issue remaining.
(Reporter)

Comment 13

2 years ago
Could this be the issue?  That the HWA setting isn't changing what it should?

Comment 14

2 years ago
Did you restart your computer after upgrading the drivers?
(Reporter)

Comment 15

2 years ago
Of course.

Comment 16

2 years ago
Could you make a test with a fresh profile, maybe there is a pref modified in your current profile:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
(Reporter)

Comment 17

2 years ago
I did you one better.  I recreated a fresh install of FF portable (same version - 44.0.2).  So everything is brand new, no add-ons, no changes whatsoever, and HWA is enabled by default.

But the same problem persists.

Comment 18

2 years ago
If you set about:config > gfx.font_rendering.cleartype_params.rendering_mode=2 (restart FF), does it change the font smoothing?
(Reporter)

Comment 19

2 years ago
I just tried it - no difference.

Comment 20

2 years ago
DirectWrite version 6.1.7600.16972 is too old.
I think you missed "Windows 7 with Platform Update KB2670838" and further updates from MS.
Whiteboard: [gfx-noted]
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.