This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

have problems with hardware acceleration of rendering: fonts looks terrible

  • 3 răspunsuri
  • 10 au această problemă
  • 8 vizualizări
  • Ultimul răspuns de cor-el

an.authentic
an.authentic
more options

have problems with hardware acceleration of rendering (integrated gpu: amd 760g) from one of latest nightly updates - font looks terrible http://i.imgur.com/kWnySVv.png

have problems with hardware acceleration of rendering (integrated gpu: amd 760g) from one of latest nightly updates - font looks terrible http://i.imgur.com/kWnySVv.png

Soluție aleasă

Note that the gfx.content.azure.enabled pref no longer has effect and you can try to disable Direct2D by setting the gfx.direct2d.disabled pref to true on the about:config page and leave hardware acceleration otherwise enabled.

See also comment 414 in bug 812695:

That way you still have the benefit from hardware acceleration, but may not suffer from rendering issues.

Citește acest răspuns în context 👍 3

Toate răspunsurile (3)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Is this the first time font rendering has not worked well with hardware acceleration enabled? It might be a regression in the latest nightly that will be remedied, or it might be a change that would be hard to undo. I'm not sure of the best way to determine that. If it doesn't clear up in a few days, you could file a bug indicating which nightly started the problem.

an.authentic
an.authentic Deținătorul întrebării
more options

ok, ty for answer. waiting for fix )

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Soluție aleasă

Note that the gfx.content.azure.enabled pref no longer has effect and you can try to disable Direct2D by setting the gfx.direct2d.disabled pref to true on the about:config page and leave hardware acceleration otherwise enabled.

See also comment 414 in bug 812695:

That way you still have the benefit from hardware acceleration, but may not suffer from rendering issues.