search

other6 / gdipp

Automatically exported from code.google.com/p/gdipp
0 stars 0 forks source link

GDiPP doesn't inject its AA with Firefox 4 #117

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Which program triggers the problem? Specify the filename if possible.
GDiPP doesn't inject its AA with Firefox 4
when I turn on "Use hardware acceleration when available"

What is the expected output? What do you see instead?
just the plain windows jagged fonts. it looks like the whole
page is processing within the GPU and not in software rendering 

What version of gdipp (including renderer)? On which operating system?
version 0.9.0 64bit

Original issue reported on code.google.com by naliceg...@yahoo.co.jp on 12 Sep 2010 at 3:13

GoogleCodeExporter commented 8 years ago 
Reference: DirectWrite COM hooking.

Original comment by crendk...@gmail.com on 13 Sep 2010 at 8:27

GoogleCodeExporter commented 8 years ago 
I realized that the DW/D2D hooking of Firefox is different from IE9 and Visual 
Studio 2010.

Original comment by crendk...@gmail.com on 28 Sep 2010 at 8:52

GoogleCodeExporter commented 8 years ago 
Issue 55 has been merged into this issue.

Original comment by crendk...@gmail.com on 28 Sep 2010 at 8:52

GoogleCodeExporter commented 8 years ago 
The current code in the repository is able to replace all the text in Firefox 
4.0 Beta 6 with nothing.

Original comment by crendk...@gmail.com on 28 Sep 2010 at 9:00

GoogleCodeExporter commented 8 years ago 
This affected me as well, in Firefox 5. I disabled hardware acceleration, and 
gdipp is now working Firefox beautifully.

Original comment by sean.gil...@gmail.com on 7 Jul 2011 at 3:43

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Sorry if anyone got my comment about it working on Nightly; I was installing 
GPU drivers and something probably went wrong.

Original comment by transist...@gmail.com on 14 Oct 2011 at 6:11

GoogleCodeExporter commented 8 years ago 
Firefox uses its own font renderer style when HA is set. In order to allow 
gdipp to perform rendering, you have to disable HA. It's like Chrome's sandbox: 
there isn't anything you can do about it.

Original comment by netomend...@gmail.com on 16 Oct 2011 at 12:57

GoogleCodeExporter commented 8 years ago 
I think I've found a partial workaround in the current stable release of FF 
(11) - turn off hardware acceleration in the options menu, restart Firefox, 
then go to about:config and set the following values:

Toggle gfx.direct2d.disabled to true
Make sure layers.acceleration.disabled is false
Make sure gfx.direct2d.force-enabled is false

Then restart FF, go back to about:config, and toggle 
layers.acceleration.force-enabled to true. Restart FF

Hardware accel should now be enabled in the options menu, and pages should 
scroll without the old horrendous choppiness, but gdipp will render the text. 
Obviously the first toggle is the main thing, since direct2d is the culprit. 
The other two toggles are possibly optional, but they seem to have helped speed 
up page rendering without forfeiting gdipp font smoothing.

Does this make sense? I know those toggles seem to contradict one another, but 
it definitely produces the desired effect. This is possibly an obvious 
solution, but it might help another novice out there.

Original comment by ed.g...@gmail.com on 6 Apr 2012 at 1:58

GoogleCodeExporter commented 8 years ago 
@up

It's works. Thanks!

Original comment by sobier...@gmail.com on 23 Apr 2012 at 11:24