[Plib-users] Runtime problem after switching from 1.4.2 to 1.6.0

[David L. <Dav...@no...>]

Hi,

After switching from plib-1.4.2 to plib-1.6.0 Flightgear manages to render
the spash-screen but crashes before rendering the main screen with one of
those "instruction at ... referenced memory at... which could not be read"
type errors on my system.  This is with an otherwise identical build of
Flightgear on NT4sp6a with 3Dlabs Oxygen VX1 (32MB) with the very latest
drivers.  This was compiled on Cygwin but other downloaded Flightgear
binaries compiled on MSVC6 and MingW show exactly the same behaviour since
the switch to 1.6.0.  Putting a few couts into Flightgear seems to indicate
that it is dying in ssgCullAndDraw.   It will run fine in software
rendering mode (256 colours) and if --disable-skyblend and
--disable-random-objects are specified  (the tux example runs fine as
well).

Does anyone have any suggestions as to whether this is likely to be a Plib
bug or a 3Dlabs driver bug?  I realise the VX1 is pretty long in the tooth
now and that a new Geforce at a fraction of its original cost will blow it
away performance wise, but it still seems a shame to ditch it when
framerates are still otherwise acceptable...

Cheers - Dave