[freespace2] More on the text coming and going

[Joshua Menke]

Taylor Richards wrote:

>I don't think it's something with the fonts either since the problem
>goes away if you disable the shaded background behind the text in
>mainhallmenu.cpp.  
>
So if I went through and commented out all calls to gr_shade, the 
problem may go away for Matrox cards, albeit the text won't look as pretty?

-Josh

>I don't know if it's related but from a valgrind log
>on my G400 test system there are a butt load of mga related errors that
>don't show up with NVIDIA drivers or running with software GL.  I didn't
>really look carefully at it (since I don't quite understand it) but I
>think the mga is using a 565 texture format instead of 1555.
>
>==26689== 1253376 errors in context 80 of 80:
>==26689== Invalid write of size 4
>==26689==    at 0x4478CB11: mgaConvertTexture (mgatexcnv.c:117)
>==26689==    by 0x4478D8D8: mgaUploadSubImageLocked (mgatexmem.c:384)
>==26689==    by 0x4478D9A2: mgaUploadTexLevel (mgatexmem.c:422)
>==26689==    by 0x4478DB44: mgaUploadTexImages (mgatexmem.c:509)
>==26689==    Address 0x4932D000 is not stack'd, malloc'd or free'd
>
>I can send you the whole log it you want.  Here are some links to those
>source files if you want to look them over:
>
>http://www.atomised.org/docs/XFree86-4.2.1/mgatexmem_8c-source.html
>http://www.atomised.org/docs/XFree86-4.2.1/mgatexcnv_8c-source.html
>
>
>Taylor
>
>  
>