Norman Vine <[EMAIL PROTECTED]> said:
> David Megginson writes:
> >
> > David Megginson writes:
> >
> > > Here's what I think is the offending PLIB code, at the top of
> > > src/ssg/ssgOptimiser.cxx:
> > >
> > > static float optimise_vtol [3] =
> > > {
> > > 0.01f, /* DISTANCE_SLOP = One centimeter */
> > > 0.04f, /* COLOUR_SLOP = Four percent */
> > > 0.004f, /* TEXCOORD_SLOP = One texel on a 256 map */
> > > } ;
> > >
> > > Unfortunately, this array is not accessible from outside, so we cannot
> > > simply modify it -- we'll have to patch. Try changing the first one
> > > (DISTANCE_SLOP) to something like 0.001f and see if most of the
> > > problems disappear.
> >
> > Yep, that did it. I just tried rebuilding with the patched plib, and
> > my own problems with small mangled objects vanished: just change 0.01f
> > (1 cm) to 0.001f (1 mm), or even smaller, if you prefer. If this
> > change works for everyone else as well, let's start bugging Steve to
> > apply our patch and put out a new plib release.
>
>
> Probably better to do something like this
>
> void ssgStripify ( ssgEntity *ent, float *vtol )
> {
> current_vtol = vtol? vtol: optimise_vtol ;
> .......
>
> }
Yes that is better. To be useful vtol should really come in as an optional
parameter of the loader functions.
Best,
Jim
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
