Hello Adam,

You need to disable compiled vertex arrays, and multitexturing in your q3config.cfg
file. Q3 should be very playable, with a couple of glitches.


Hmmm... I made those changes. The game started up and loaded a level without problems. Unfortunately, within a few seconds Q3A had locked up. I could still ssh in and reboot though. I'm really quite thrilled that complete system lockups seem to be a thing of the past.

Anyone want to comment on if we will see a day when an application which locks up can just be killed and X returns to normal? :-)

Is the Q3A lockup repeatable 100% of the time? I've been attempting to find the
source of a lockup Vladimir reported, which seems to be related to mouse
movement, but I haven't been able to reproduce it yet.


No problems.  I have a few others I can try (ie. doom3, ut2004), too.
Adam

ut2004 demo will start after messing with the config file options a bit, and disabling the
multitexture fallback (ut2004-demo doesn't seem to respect it's MaxTextureUnits option).
However, it seems to be horribly corrupted in game, much the same as quake3 is when
r_ext_compiled_vertex_array is set.


I haven't tried doom3 yet, and won't be able to now until there is a 64-bit version, or the
drm has support for 32-bit clients.


Thanks again!
Ben Skeggs.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to