Attachments (3)
Change History (11)
by , 15 years ago
Attachment: | screenshot1.png added |
---|
comment:1 by , 15 years ago
Hmm, the shots look perfect?
You should take a digital photo, as the memory content is probably perfect if the driver is responsible...
Can you take a digital photo of some artifacts reasonably close up and upload them here?
Thanks!
Rudolf.
comment:2 by , 15 years ago
Ah, OK, you mean the slightly thicker 'A' ??
This is a 'artifact' the app_server or something does. This is not driver specific. I can tell because you did a system screenshot. Driver faults generally don't show with system screenshots..
Please advice.. Rudolf.
comment:3 by , 15 years ago
I remember, I was so earlier in the bad refreshed but at 59-60 Hz everything was ok, now, unfortunately, each have such strange fonts, it seems to me that the driver error.
comment:4 by , 15 years ago
Component: | Drivers/Graphics/nVidia → Servers/app_server |
---|---|
Owner: | changed from | to
Whatever this is, I agree with Rudolf that this should be an app_server problem. When exactly do you see those problems, as they don't seem to be always there?
comment:5 by , 15 years ago
My immediate guess would be the disabling of the patented bytecode interpreter of FreeType in hrev32577.
comment:6 by , 15 years ago
comment:7 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
As mmlr already wrote, we disabled the patented hinting code in the default images, and this is exactly the reason why the font hinting has slightly changed. Sorry, but you have to build your own images and configure them with --include-patented-code to enable the previous hinting method. The public images cannot be build like this anymore, I should not have enabled this back when I did, but at that time, the non-patented auto-hinter in FreeType was much, much worse than it is today.
In any case, the effects of this change is exactly what you see in the screenshots, but I have to close this as invalid (won't fix).
screen 1