Doom III: "vertex array range in virtual memory: SOLVED"

[Ken D'Ambrosio]

Hello, all.  Please excuse me for quasi-spamming the list; this is meant
to be both informative and informational.  I recently took the plunge to
64-bit; I'd done it from time to time since '04, but this time was for
real.  And everything worked great... except Doom III.  Every time I
launched it, I'd get

WARNING: vertex array range in virtual memory (SLOW)
signal caught: Segmentation fault
si_code 1
[...]

and it would die.  Googled like crazy, found lots of people with the same
problem, but no resolution.  FINALLY figured out that it was an X library
issue.  While this hack won't fix XF86 machines, it works just fine for
X.org systems.  Specifically, in the doom3 wrapper script, I added:
export LIBGL_DRIVERS_DIR=/usr/lib32/dri

Now, there's a much better place for this tidbit of information: the Doom
III Linux FAQ over at ID Systems.  I e-mailed it to ttimo at idsoftware.com
-- the maintainer of said page -- and his pretty-darn-terse reply was,
a) We don't offer ANY support for community-supported versions,
b) Your X (a stock Ubuntu install) is clearly broken
c) See a.

Since there were many people who'd experienced this ("vertex array range
in virtual memory" gives 10K hits on Google), and, as far as I could tell,
none of them mentioned a solution, I thought that wasn't a real
friendly-like attitude, especially when a couple lines on a FAQ -- that
already existed, AND discussed 64-bit issues -- was all I was asking for. 
I replied saying so, and received nothing in response.

Therefore, I'm sending this e-mail to the list so that, if you ever bump
into this problem, you may be able to get past it, AND so that (hopefully)
Google will work its magick(tm) and help anyone else who has a similar
issue.

-Ken


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.