hi, As more games work, keeping the directx driver default for older machines is fine.
Remember there were a bunch of problems caused by the switch away from the directx driver as well, and more reports that we've gotten so far about the directx problem. I think this particular use case is also uncommon, since it does a lot of manual locking/unlocking of the screen surface. It's just something that you really should do, and most 99% of people don't do. So most games won't run into this issue at all. Emmanuel: Do the other programs cause a reboot? Or just this one program? The benefits are: - more compatibility with older machines. - faster, lower latency input - a lot faster graphics. - less cpu used in graphics. Remember that the older machines that this is enabled on can not play some games without the directx driver -- since then the graphics would likely be too slow. cheers, On Fri, Aug 22, 2008 at 9:58 AM, Brian Fisher <[EMAIL PROTECTED]> wrote: > Since 1.8.1's release, there have already been 2 problems fixed with forcing > VIDEODRIVER back to the SDL default of windib, one of which is a driver > crash resulting in a reboot another is a keyboard input thing - it makes me > wonder if SDL made the right choice for the default, and pygame shouldn't be > messing with the default VIDEODRIVER on XP after all? > > On Thu, Aug 21, 2008 at 4:17 PM, Emmanuel Kanter <[EMAIL PROTECTED]> > wrote: >> >> Lenard Lindstrom wrote: >>> >>> Though I am unfamiliar with the book I can still make on suggestion. Try >>> setting the SDL_VIDEODRIVER environment variable to windib before running >>> any examples. From the dos prompt: >>> >>> set SDL_VIDEODRIVER=windib >>> >>> Lenard >> >> for my complete confusion, this worked. >> where can I read more about it, so I'll understand what I just did? >> >> Thanks! >> Emi > >
