Hi again, Scratch that. I tried on Windows and things work just perfectly: correct font size, great FPS, no crash or freeze.
On Mac though, I've problems with or without the font hack... So my persistent crash issue has nothing to do with fonts but, probably, with something else in that branch (one of the newly built lib for Mac?) Still searching... - Merov On Tue, Mar 22, 2011 at 4:44 PM, Philippe (Merov) Bossut < me...@lindenlab.com> wrote: > Hi, > > I received a very good hint from Ov Dos about this font rendering issue: > http://lists.nongnu.org/archive/html/freetype/2011-03/msg00010.html > > I tried using FT_LOAD_FORCE_AUTOHINT (only 1 call to change in > LLFontFreetype::renderGlyph()) and it appears to fix the problem. *However*, > I'm experiencing catastrophic freeze (no crash but the whole Mac is locked, > hard reboot only option) on log in or TP and a terrible frame rate when I > manage to log in. I can't see the relationship between that glyph rendering > change and logging in on a region and the SecondLife.log doesn't give much > hint except for an inordinate amount of: > WARNING: isFeatureAvailable: Feature RenderDeferred not on feature > list! > > Question: Has anyone tried FT_LOAD_FORCE_AUTOHINT on other platform than > Mac? Result? > > Cheers, > - Merov > > On Mon, Mar 21, 2011 at 11:17 PM, Philippe (Merov) Bossut < > me...@lindenlab.com> wrote: > >> Hi, >> >> We identified that moving from freetype 2.3.9 to 2.4.4 in >> viewer-autobuild2010 produces smaller text (roughly 10% smaller). >> >> Looking into this this afternoon, I was able to narrow it down to >> LLFontFreetype::addGlyphFromFont(): tracing the glypth width and height in >> LLFontFreetype::addGlyphFromFont(), one can see that 2.4 sizes are almost >> always 1 pixel smaller in height and sometimes width than the same glyph >> renderer with 2.3. 1 pixel on a 10 pixel high bitmap explains why moving the >> UI sixe rendering to 1.1 in preferences sort of compensate the problem. >> >> The underlying issue as to where this rendering difference comes from is >> unclear. Searching the freetype release notes since 2.3.9 doesn't point to >> anything particularly relevant to this. Diffing freetype.h and ftimage.h is >> not bringing any useful information either, or at least, I haven't found >> any. >> >> If someone has any light to shed on this freetype issue, it would be very >> much appreciated. >> >> For the moment, the plan of record is to downgrade freetype to 2.3.9 >> though, clearly, this is not the best solution. >> >> Cheers, >> >> - Merov >> >> >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
