Re: [pygame] More DirectX related problems

To: pygame-users@xxxxxxxx

Subject: Re: [pygame] More DirectX related problems

From: Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx>

Date: Tue, 3 Feb 2009 16:07:54 -0800

Delivered-to: archiver@xxxxxxxx

Delivered-to: pygame-users-outgoing@xxxxxxxx

Delivered-to: pygame-users@xxxxxxxx

Delivery-date: Tue, 03 Feb 2009 19:07:57 -0500

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=XEwdn1mSrIHmyxPO/gfxywH8TA7iq6qw+JJ7DklZiP8=; b=pcGCSTkqYSC5+6yy6KBtnl063mlblyaaijRJjwPKH+r9tj/hqRcMtVatvOFmg8Rm6C 1HV8870TlahurGV3g9VHqnFxKoNbDbiqNpaGepi76ueoz5hUd0U4gpybU9kcmJ8eGLPy 3O8ypCmfsreVrLkrj2d/vC06Vm8xXvoOA84RQ=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=wikgHXRiR3q4ntdvdfXVzMvo+7pLIcMpeZPbgQ2qSCgUdpx9hbxbs59eWy9Lb9AIHB 36t0w3neeEUrAdgnyK5jGt+m1IVLF+vN0i4YZNdCjdS+IM6Ih6UAuOMAougim+KTXeDN csdVPcQ3DK0GLJzaJYiohA9FnUzfofrjtTlLk=

In-reply-to: <64ddb72c0902031601re392257y55ccc6fe88b47362@xxxxxxxxxxxxxx>

References: <4988D473.4040504@xxxxxxxxx> <e55f7e400902031557r1dd4f83eh6b0195fb1ce2c478@xxxxxxxxxxxxxx> <64ddb72c0902031601re392257y55ccc6fe88b47362@xxxxxxxxxxxxxx>

Reply-to: pygame-users@xxxxxxxx

Sender: owner-pygame-users@xxxxxxxx

On Tue, Feb 3, 2009 at 4:01 PM, René Dudfield <renesd@xxxxxxxxx> wrote:

hi,

On many older computers directx is quite a lot faster -- even without
HWSURFACE. Even on newer computers directx can be faster with XP.

For this reason, and the other reasons mentioned in the previous
threads about this I think we should stay with directx as the default
on older computers.

cheers,

On Wed, Feb 4, 2009 at 10:57 AM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
> I agree with going with windib as default. I may be wrong, but I think
> directx backend is inferior if you are not using HWSURFACE.
>
> I suppose the best mix would be to use directx if and only if using
> HWSURFACE, but it's too late by the time the display mode is set to make
> that call on the backend.
>
> On Tue, Feb 3, 2009 at 3:34 PM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
>>
>> I just had personal confirmation that SDL, maybe with the help of Pygame,
>> does have DirectX issues. After repeated runs of surfarray_test.py and
>> related programs my antiquated system(*) reached the point that a simple
>> pygame.init() call would segfault. I confirmed it was DirectX by changing
>> the video driver to windib. That worked. And to further confirm it was a
>> corrupted DirectX and not Python I tried the dxdiag.exe video tests. They
>> failed. Only a system reboot cleared the problem. At that point I also
>> confirmed that non of the other programs I was using depended on DirectX.
>> Only Python/Pygame caused ddraw.dll and dsound.dll to be loaded and kept
>> alive by that suspicious ddhelp.exe character. Apparently DirectX has a
>> memory.
>>
>> So what to do. Maybe it is time to defer to the judgment of the SDL
>> developers and just let windib be the default Windows video driver. The
>> documentation can suggest that anyone experiencing performance problems try
>> directx.
>>
>> Lenard
>>
>>
>> (*) Windows 98, DirectX 8.0 (And no, I don't want to see what DX 9 or
>> higher will do for me. It would probably break something).
>>
>> --
>> Lenard Lindstrom
>> <len-l@xxxxxxxxx>
>>
>
>