also known as rm...@umd.edu
From: James Turner
To: FlightGear developers discussions
Sent: Monday, December 29, 2008 6:46:47 PM
Subject: Re: [Flightgear-devel] problems with z-buffer
On 29 Dec 2008, at 08:40, Tim Moore wrote:
> .4 meters seemed
> suffi
On Tue, Dec 30, 2008 at 10:46 AM, James Turner wrote:
>
> On 29 Dec 2008, at 08:40, Tim Moore wrote:
>
>> .4 meters seemed
>> sufficient to me, but others don't agree, so perhaps we can settle
>> on some value
>> larger than .1. The near plane value is settable, both in the camera
>> configuration
Hi,
I tried this change on my MacBook Pro with ATI Radeon X1600.
Setting .1 to znear increases a chance of flickering 3D clouds as Tim
mentioned. Changing it to .4 reduces the flicker but not enough on my
Mac. .7 will be sufficient to eliminate flicker in most of views but
you cannot see ve
On 29 Dec 2008, at 08:40, Tim Moore wrote:
> .4 meters seemed
> sufficient to me, but others don't agree, so perhaps we can settle
> on some value
> larger than .1. The near plane value is settable, both in the camera
> configuration and as a "live" property in /sim/rendering/camera-
> group/z
Alex Romosan wrote:
> the latest commit to src/Main/CameraGroup.cxx changed the value of
> zNear from .1 to .4 and this causes strange artifacts to show up when
> panning around (like holes in the cockpit, etc.). the following patch
> changes it back:
>
> --- src/Main/CameraGroup.cxx27 Dec 200
the latest commit to src/Main/CameraGroup.cxx changed the value of
zNear from .1 to .4 and this causes strange artifacts to show up when
panning around (like holes in the cockpit, etc.). the following patch
changes it back:
--- src/Main/CameraGroup.cxx27 Dec 2008 14:35:33 - 1.9
+++ sr
6 matches
Mail list logo
