Also if I'm not mistaken, the current version of the Bravo alters the startup field-of-view from default of 55 to 60; would that make it more prone to problems in this area? -R.
Robert M. Shearman, Jr. Transit Operations Supervisor, University of Maryland Department of Transportation also known as rm...@umd.edu ________________________________ From: James Turner <zakal...@mac.com> To: FlightGear developers discussions <flightgear-devel@lists.sourceforge.net> 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 > 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/znear. Just ran into this with Bravo. A value of 0.2 works, but 0.3 causes some minor clipping of the cockpit roof, and 0.4 causes nearly the entire side-pillar to be clipped. I wonder if part of this is about camera position placement in the models, but my ignorance of such matters is vast, so I'll say no more. James ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
