> BTW, your post made it the first time.  I was hoping someone more
> knowledgable would answer your questions, but I guess you're stuck with
> me!  ;-p
 
..aouch!  ;-)   which first post? (message id?)
 
> * [EMAIL PROTECTED] [2001.07.25 21:32]:
> > ..the first time I had FG-0.7.8 (w/ plib 1.4.1 and SimGear 0.0.16) 
> > up and running, X v4.0.3 ran away with about 97% cpu. 
> > FG appeared rock solid at 7 frames per minute in its window. 
> > As the same thing happened on my first FElt compile, 
> > I threw out X v4.0.3 in favor of X v4.1.0, and rebuilt FG accordingly.
> > Since then, ./runfgfs dies "Cannot locate FG root directory (data)".
> 
> Did you recompile plib, simgear, and flightgear?
 
..yep, yep, yep.  Now on 1.4.2, 0.0.17 and 0.7.8.
 
> > ..'runfgfs, and preferences.xml was hand copied from 
> > /usr/local/source/FlightGear-0.7.8/src/Main.  Makefile bug?  
> > 
> > [arnt@Lena FlightGear]$ ./runfgfs
> > Cannot locate FG root directory (data)

..how do I _make_ (as in force/hardcode/threathen) 
FG to find its root  ($FGROOT?) data directory?
I thought I could set this with a ./configure option?
Sez so in the docs.   
Is this error related to the valid OpenGL context"?
 
> I would suggest doing a fresh plib, simgear, and flightgear install
> *without* messing with runfgfs and preferences.xml.
 
.. see above.  Tried both.  Also tried messing with 
preferences.xml to fly in my area, which worked when 
X v4.0.3 spun down in flames.
 
> > [arnt@Lena FlightGear]$ ./bin/fgfs
> >  
> >   Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
> > <[EMAIL PROTECTED]>
> > FlightGear:  Version 0.7.8
> >  
> > Scanning for root: command line
> > fg_root = /usr/local/FlightGear/lib/FlightGear
> > Reading global preferences
> > Reading properties from
> > /usr/local/FlightGear/lib/FlightGear/preferences.xml
> > Error reading property list from file
> > /usr/local/FlightGear/lib/FlightGear/pref
> > erences.xml
> > Failed to read global preferences from
> > /usr/local/FlightGear/lib/FlightGear/pre
> > ferences.xml
> > Processing command line arguments
> > Opening a window: 800x600
> > Mesa GLX Indirect
> > Max texture size = 2048
> > Depth buffer bits = 16
> > FATAL: ssgInit called without a valid OpenGL context.

..in FG and ssgInit context, what _is_ "a valid OpenGL context"?
I use:
rpm -qi Mesa
Name        : Mesa                         Relocations: /usr
Version     : 3.4.2                             Vendor: Red Hat, Inc.
Release     : 3                             Build Date: Tue 10 Jul 2001
11:38:22 AM CEST
Install date: Sat 21 Jul 2001 01:27:07 PM CEST      Build Host:
stripples.devel.redhat.com
Group       : System Environment/Libraries   Source RPM:
Mesa-3.4.2-3.src.rpm
Size        : 2574821                          License: GPL
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://www.mesa3d.org
Summary     : A 3-D graphics library similar to OpenGL.
Description :
The Mesa 3-D graphics library is a powerful and generic toolset for
creating hardware assisted computer graphics.  To the extent that Mesa
utilizes the OpenGL command syntax or state machine, it is being used
with authorization from Silicon Graphics, Inc.  However, the author
(Brian Paul) makes no claim that Mesa is in any way a compatible
replacement for OpenGL or associated with Silicon Graphics, Inc. Those
who want a licensed implementation of OpenGL should contact a licensed
vendor.  However, Mesa is very similar to OpenGL, and you might find
Mesa to be a valid alternative to OpenGL.
> > 
> > ..ok, what do I do now?
> 
> I'm not sure how this should be fixed, but there is a post by a user
> about how he fixed this.  I think he basically had a GL lib conflict
> that he had to work around.  See:
> 
>   http://www.geocrawler.com/lists/3/SourceForge/11854/125/6095982/

..told me he'd been succesful using Redhat's gcc v2.96-85, 
which I threw out as part of the X upgrade.  gcc v2.96-94.
I see nothing in the changelog that should cause failure of FG.
 
> Thanks
> -- 
> Cameron Moore

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)

  Scenarios always come in sets of three: 
  best case, worst case, and just in case.


_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to