plib-users

[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 

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

[Steve B. <sjb...@ai...>]

David Luff wrote:

> 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...

Well, firstly, this is probably (initially at least) a question for the
FlightGear mailing list.

I'd need a stack backtrace so I can see the function and linenumber where
we were dying...I stand no chance of fixing it (even assuming it *is* a
PLIB bug) unless I have a *TON* more information.

----------------------------- Steve Baker -------------------------------
Mail : <sjb...@ai...>   WorkMail: <sj...@li...>
URLs : http://www.sjbaker.org
        http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net
        http://prettypoly.sf.net http://freeglut.sf.net
        http://toobular.sf.net   http://lodestone.sf.net

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

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

On 10/9/02 at 12:57 PM Steve Baker wrote:
>Well, firstly, this is probably (initially at least) a question for the
>FlightGear mailing list.
>
>I'd need a stack backtrace so I can see the function and linenumber where
>we were dying...I stand no chance of fixing it (even assuming it *is* a
>PLIB bug) unless I have a *TON* more information.
>

OK, thanks, I sort of figured this might be the case, and posted more in
hope than expectation.  If I manage to get a backtrace before I ditch the
card I'll post it.

Cheers - Dave