Further testing (Windows 0.9.6 binaries, ATI Mobility Radeon 9700)
reveals that this problem seems only to occur where a moving object
passes between the panel and the viewer; in the case of the wing, where
the flaps are in the flaps up position (note, however, that you can
still see the artefact with the flaps down), and the elevators, which
obviously move. Also, the moving yoke, if rotated, passes under, not
over, the panel. This effect is much more pronounced in the 182 - it is
easy to move the yolk right under the tachometer.

Is this a draw-order problem relating to moving surfaces?

Giles Robertson

-----Original Message-----
From: Giles Robertson 
Sent: 13 October 2004 23:54
To: FlightGear user discussions
Subject: RE: [Flightgear-users] transparent wing with 0.9.6

I recall seeing this around 0.9.3, but it happened with a lot of
programs on my Intel card, so I never wrote about it, because I couldn't
isolate it as an fgfs problem. 

Giles

-----Original Message-----
From: Chris Metzler [mailto:[EMAIL PROTECTED] 
Sent: 13 October 2004 20:41
To: FlightGear user discussions
Subject: Re: [Flightgear-users] transparent wing with 0.9.6

On Wed, 13 Oct 2004 20:25:55 +0100
Lee Elliott <[EMAIL PROTECTED]> wrote:
>
> I noticed that it occurs when the object that should block the 
> view of the panel instruments is an enclosing volume.  In the 
> case of the wings, the panel instruments are visible through 
> both upper and lower wing surfaces.  You can see the instruments 
> through the struts too and the same applies here - you're 
> viewing the instruments through two opposite facing surfaces 
> that are part of the same object.
> 
> With objects that don't seem to be transparent to the 
> instruments, such as the fuselage, there's only a single surface 
> of any particular object between the viewer and the instruments.
> 
> I don't know what would happen if the surfaces were split i.e. 
> upper and lower wing surfaces, but that isn't really a solution 
> to the problem and it wouldn't work well with the struts.
> 
> Quite a curious problem.

Could this be caused by the recent patches?  I dunno anything about
OpenGL so I don't know whether that's a stupid question.  But I've
flown the c172 a lot lately and did not see this before updating
from CVS and applying Matthias' plib patch.

-c

P.S.  I'd back them out to test but I'm off to see my first WC
qualifier, woo hoo!

-- 
Chris Metzler                   [EMAIL PROTECTED]
                (remove "snip-me." to email)

"As a child I understood how to give; I have forgotten this grace since
I
have become civilized." - Chief Luther Standing Bear

_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to