> > Has the exact cause > > been determined? If so, what needs to be done to get this working again? > > Or are you speaking of the problem that nwn can't get a visual at > startup and just craps out? Leif Delgass has posted a patch for that > (bug in reporting visuals) but it was decided it needs more testing as > it could possibly trigger some unwanted side effects (works fine here > though). (This problem was indeed introduced by the texmem-merge, as > previously the driver just didn't fail when it couldn't match the > requested buffersize (which is against the spec but possibly there > just to avoid the problem with the wrongly reported visuals).) > > http://sourceforge.net/mailarchive/forum.php?thread_id=2054806&forum_id=7177 > (I think you are aware of that already however, as you've participated > in that thread ;-)). > If you don't want to apply the patch, you could of course start the game > via gdb, set a breakpoint at the code when it searches for a glx visual > and change one variable when it hits the breakpoint ;-)
That is the problem I was talking about. In fact, I didn't even see the patch that Leif posted. I think spamassassin may have labelled it as spam by mistake. Anyway... I'll try out the patch on my end and let everyone know if it works and/or causes any new problems. Adam ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
