bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] More or less unresolved problems before an upcoming rele


From: Jonathan Kinsey
Subject: Re: [Bug-gnubg] More or less unresolved problems before an upcoming release
Date: Fri, 22 Feb 2008 08:45:22 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.0

Christian Anthon wrote:
On Thu, Feb 21, 2008 at 10:16 PM, Jonathan Kinsey
<address@hidden> wrote:
Christian Anthon wrote:
 > Hi All,

 > c1) clicking on the 3dboard doesn't always work, especially bad under
 > vista with radeon mobility graphic cards, but I'm suffering from the
 > same problem under Linux. The problem is that the pieces are redrawn
 > to check if they have been clicked and that takes up to 1sec under
 > windows vista with aforementioned cards. I'm not sure if it's needed
 > to redraw the pieces, seems to work fine without.

 The screen isn't redrawn, a simplified scene is rendered off screen to detect
 what was clicked.  That being said it does use the same display list for the
 pieces, a slightly less accurate "piece" could be drawn which would be quicker,
 the reason I didn't bother is because this off screen "drawing" is very quick.

 The fact it occasionally takes a long time to do this is likely a problem with
 the graphics driver, but maybe there is something that could be done in the
 code.  It's difficult for me to try anything as I don't get the problem, maybe
 when I get a machine with Vista on it I might be able to reproduce it.


Yeah, I'm guessing that it's a driver issue as well. In particular as
it happens under both vista and linux with the same card (vista being
far the worst). If I comment out the lines 2262-2269 in drawboard3d.c
everything is working fine as far as I can tell.

It might fix the time problem, but obviously you wouldn't be able to click on any pieces...

What if you try copying drawPiece to drawPiecePick say and calling that in line 2268, the only difference being the glCallList is removed (line 984)? Assuming this line is the problem, it's probably the texture/normal information in this list confusing the driver. I can create another list which only has the shape of the pieces, which may fix the problem.

Jon

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]