Fred wrote > Hi Durk, > > my intention is to post a win32 binary update as soon as the issues > reported by Vivian and you are addressed. I don't think the new commited > code requires a data update. > > -Fred > > -- message original -- > Sujet: Re: [Flightgear-devel] Big black box > De: Durk Talsma <[email protected]> > Date: 31.12.2008 10:36 > > Hi, > > > On Wednesday 31 December 2008 11:11:16 Frederic Bouvier wrote: > > An early 1.9.1 ? > > > > -Fred > > > > -- message original -- > > Sujet: Re: [Flightgear-devel] Big black box > > De: Stuart Buchanan <[email protected]> > > Date: 31.12.2008 09:51 > > > > Tim Moore wrote: > > > Yeah, the lack of frame buffer object support turned out to be the > common > > > denominator for users seeing the problem. I checked in code tonight > that > > > should resolve the issue when frame buffer objects aren't available. > > > > Great stuff - thanks Tim. > > > > I wonder whether it would be worthwhile merging these bug fixes into a > 1.9 > > patch release. > > > > I guess that as long as the updated binary is still compatible with the > base > package, we could just release a quick source / binary only release. If > incompatibilities have already been introduced, we should consider doing a > full 1.9.1 bugfix release soon. I'd like to get some more feedback, but > perhaps early next week would be good. > > In any case: Happy new Year everyone! >
The new default near-field value causes clipping problems in many, if not most, cockpits. I've already checked in a fix for the Camel, but this needs checking for all the data package models. Vivian ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
