[Flightgear-devel] Standby

2002-11-28 Thread David Findlay
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

for /.ing. Flightgear.org is on the front page.

David

- -- 
If you give someone a program, you will frustrate them for a day. If you teach 
them how to program, you will frustrate them for a lifetime.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE95taZZOfFgbBAbXARAgdAAKCDcWOJ/1EjI4AnchFo56Xkqo+h5gCeLZJ0
wWetkwwBG421Lz2Igi8dVkw=
=8m49
-END PGP SIGNATURE-


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Failed assertion in ssg.h

2002-11-28 Thread Geoff Reidy
Curtis L. Olson wrote:



Geoff,

I did some testing at home this weekend and I think there is something
going on here related to the random ground cover objects.

If I run with --disable-random-objects I have never seen a crash.  If
I run with the random objects I do see a similar crash after flying
3000 miles give or take a couple thousand.

So I will say the following:

For long haul flights, consider running without random objects.
Random objects have a couple issues:

- program crash after a few thousand miles.  (To be fair, this may not
  directly be the random object code's fault.  It could be an
  interaction issue with other portions of the program?)

- issues with freeing tiles ... this can lead to substantially reduced
  frame rates while the system is struggling to free memory associated
  with a tile that has just been removed from the cache.

For short hops, training, or any other sort of flight where you aren't
venturing too far from home base, then it should be safe to leave
random objects on.

Regards,

Curt.


Curt,

I still have the "fgfs: ssg.h:302: void ssgBase::deRef(): Assertion 
`refc > 0' failed." error with the random-objects disabled, just tried 
with current cvs. Happens after about the same distance as with them 
enabled.

Regards,
Geoff


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] simgear-cvs compile error (cygwin gcc-3.2)

2002-11-28 Thread ace project

--- Norman Vine <[EMAIL PROTECTED]> wrote:
> William Earnest writes:
> 
> > Norman Vine wrote:
> > 
> > > ace project writes:
> > >
> > > >I'm getting a compile error while compiling the
> latest
> > > >SimGear(CVS) under cygwin(current version/fresh
> > > >install).
> 
> > > >> > >extgl.h:363: `glBlendColor' redeclared as
> different
> > > >kind of symbol /usr/X11R6/include/GL/gl.h:1648:
> > >
> > >
> > > Looks like you have 'X-Windows' installed
> > >
> YIKES -- The *right* way todo this is to just change
> the configure.ac
> files to NOT check for 'X' and NOT include the
> X_Header path when
> WIN32 is defined.
> 
> Obviously this change needs tobe done by someone who
> has the 
> Cygwin X-Server installed
> 
> There is support in the script already to determine
> if this
> is a Windows installation.  
> 
> My WAG is that perhaps changing
> 
> if test "x$HOSTTYPE" != "xmacintosh" -a "x$is_mingw"
> != "xyes"; then
> dnl extra library and include directories
> EXTRA_DIRS="/usr/X11R6"
> 
> if test -d /opt/X11R6 ; then
> EXTRA_DIRS="$EXTRA_DIRS /opt/X11R6"
> fi
> fi
> 
> TO
> 
> if test "x$HOSTTYPE" != "xmacintosh" -a "x$is_mingw"
> != "xyes" -a :x$is_cywin"!="xyes"; then
> dnl extra library and include directories
> EXTRA_DIRS="/usr/X11R6"
> 
> if test -d /opt/X11R6 ; then
> EXTRA_DIRS="$EXTRA_DIRS /opt/X11R6"
> fi
> fi
> 
> Might just work,  but I am not an autoconf guru nor
> do I have X installed
> so I can not test this
> 
> FWIW - I am not sure about the multiple '-a' arg to
> if 'if test'
> 
> Norman

I tryed disabling X (--without-x), that failed. I
removed Cygwin X-windows, that was succesful.

I will try changing the configure.ac file somewhere
next week and post the results (unless William(?) gets
there first...)

Leon

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Compiling problem on latest CVS SimGear

2002-11-28 Thread ace project
Can you tell me the command line of the compiler you
used and the location of plibnet.
(search it by typing "locate plibnet". It should find
a file name something like "libplibnet.a".

Because I think that you are missing a library include
line somewhere.

--- Roland Häder <[EMAIL PROTECTED]> wrote:
> Hello!
> 
> I have just updated SimGear from CVS.
> 
> Distri: SuSE 8.0 + 3-days-old Online-Updates from
> ftp.gwdg.de
> COmpiler: gcc 2.9.??? (from SuSE)
> 
> I got this message:
> 
> ../../simgear/io/libsgio.a(sg_socket.o): In function
> `logstream_base type_info 
> function':
>
/root/Test/Extract/SimGear/simgear/io/sg_socket.hxx(.text+0x8c):
> undefined 
> reference to `netSocket::netSocket(void)'
>
/root/Test/Extract/SimGear/simgear/io/sg_socket.hxx(.text+0xc6):
> undefined 
etc...

=
My Flight Gear Multiplayer Stuff (work-in-progress):
http://www.kbs.twi.tudelft.nl/People/Students/L.Otte/

OK, I admit it: My girlfriend's just an object to me. 
Unfortunately, there is some information hiding, but 
thankfully, she's fairly encapsulated, nicely modular, and 
has a very well defined interface!

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Segmentation fault on touchdown

2002-11-28 Thread Dave Perry
For the last 2 or 3 CVS updates (or for the last 2 weeks) I have been 
getting regular
Segmentation faults right at touchdown with the dc3.  The last few lines 
of the
terminal output follow.  Is anyone else seeing this?

Updating light parameters.
 Sun angle = 59.873
 ambient = 0.35  diffuse = 0.995051  specular = 0.35  sky = 0.989102
Refreshing timestamps for -122.375 37.5625
scheduling needed tiles for -122.361 37.615
Playing audio after 321.865 sec: rumble
Playing audio after 395.833 sec: squeal
Segmentation fault
[perryd@dadsoffice FlightGear]$

By the way, the improved slowflight charachteristics with the c172p are 
great!
I like the need for increased rudder.
Thanks,
- Dave



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] Terrasync 3rd party util

2002-11-28 Thread Julian Foad
David Luff wrote:



David Luff writes:


Is it likely to work over a 56K modem?



Well, it mostly worked.  After starting in an area with no scenery, it took
a couple of minutes waiting before the appropriate airport came down, and
FlightGear could be restarted properly.  Flying the C172, terrasync mostly
kept up, but in both my tests (one in the bay area, one in the relatively
sparser UK) managed to miss one tile.  I may be mistaken, but it appears to
download a whole 1x1 degree area at once in alphabetical order, and there
were times when nothing was coming down,


I had a very similar experience.  I think the pauses were because the 
rsync server was busy; one or two local rsync processes were always 
active, but often seemed to be waiting for data.  The local TerraSync 
would create another immediately when I killed them.  I then switched 
airports, but it did not cancel the current rsync processes so nothing 
was fetched for the new location until all the outstanding fetches 
completed (or, in fact, were killed by me).

so I think that if the order of
the tile download within a 1x1 chunk was optimised to get the closest
first,


That would be more difficult.  In the normal (intended) scenario, when 
you have already got the current degree chunk, it doesn't matter much in 
what order it fetches the insides of the chunk ahead, so Curt just asks 
rsync to get the whole directory.  Cancelling outstanding rsync 
processes would also be considerably more difficult (to do portably).

and if downloading was continued almost continuously based on
position and heading, then I'm quite sure it could be made to keep up no
problem.


I think that is what it is trying to do already.


Very impressive stuff anyway.


Absolutely.

- Julian



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Compiling problem on latest CVS SimGear

2002-11-28 Thread Roland Häder
Hello!

I have just updated SimGear from CVS.

Distri: SuSE 8.0 + 3-days-old Online-Updates from ftp.gwdg.de
COmpiler: gcc 2.9.??? (from SuSE)

I got this message:

../../simgear/io/libsgio.a(sg_socket.o): In function `logstream_base type_info 
function':
/root/Test/Extract/SimGear/simgear/io/sg_socket.hxx(.text+0x8c): undefined 
reference to `netSocket::netSocket(void)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.hxx(.text+0xc6): undefined 
reference to `netInit(int *, char **)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.hxx(.text+0x4e1): undefined 
reference to `netSocket::~netSocket(void)'
../../simgear/io/libsgio.a(sg_socket.o): In function 
`SGSocket::~SGSocket(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:69: undefined reference to 
`netSocket::~netSocket(void)'
../../simgear/io/libsgio.a(sg_socket.o): In function 
`SGSocket::make_server_socket(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:76: undefined reference to 
`netSocket::open(bool)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:83: undefined reference to 
`netSocket::bind(char const *, int)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:87: undefined reference to 
`netSocket::close(void)'
../../simgear/io/libsgio.a(sg_socket.o): In function 
`SGSocket::make_client_socket(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:98: undefined reference to 
`netSocket::open(bool)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:105: undefined reference 
to `netSocket::connect(char const *, int)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:109: undefined reference 
to `netSocket::close(void)'
../../simgear/io/libsgio.a(sg_socket.o): In function 
`SGSocket::open(SGProtocolDir)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:189: undefined reference 
to `netSocket::listen(int)'
../../simgear/io/libsgio.a(sg_socket.o): In function `SGSocket::read(char *, 
int)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:221: undefined reference 
to `netSocket::recv(void *, int, int)'
../../simgear/io/libsgio.a(sg_socket.o): In function `SGSocket::readline(char 
*, int)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:256: undefined reference 
to `netSocket::recv(void *, int, int)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:279: undefined reference 
to `netSocket::recv(void *, int, int)'
../../simgear/io/libsgio.a(sg_socket.o): In function `SGSocket::write(char 
const *, int)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:324: undefined reference 
to `netSocket::send(void const *, int, int)'
../../simgear/io/libsgio.a(sg_socket.o): In function `SGSocket::close(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:354: undefined reference 
to `netSocket::close(void)'
../../simgear/io/libsgio.a(sg_socket.o): In function 
`SGSocket::nonblock(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:367: undefined reference 
to `netSocket::setBlocking(bool)'
../../simgear/io/libsgio.a(sg_socket.o): In function `SGSocket::poll(void)':
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:382: undefined reference 
to `netSocket::select(netSocket **, netSocket **, int)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:388: undefined reference 
to `netSocket::accept(netAddress *)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:390: undefined reference 
to `netAddress::getPort(void) const'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:390: undefined reference 
to `netAddress::getHost(void) const'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:391: undefined reference 
to `netSocket::netSocket(void)'
/root/Test/Extract/SimGear/simgear/io/sg_socket.cxx:392: undefined reference 
to `netSocket::setHandle(int)'
collect2: ld returned 1 exit status
make[3]: *** [socktest] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1

Roland
(-;


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] hsi and cockpit photo-link

2002-11-28 Thread David Luff
On 11/23/02 at 6:11 PM paul mccann wrote:

>Hi All
>
>Here is where I am at on the hsi 
>http://members.verizon.net/~vze3b42n/fgfs-screen-027.jpeg
>is any one interested in this?

Well, speaking for myself, I'm always interested in what people are doing
with Flightgear and always look any screenshot links posted to the list.
The HSI looks good :-)

In fact, I got round to having a good play with Flightgear for the first
time in ages the other day and apart from the obvious (rwy lights, 3d
clouds etc) found loads of cool stuff I hadn't used before.  In particular
the full screen hi-res panel, the Cub, and the 3D cockpits with clickable
instruments are all very impressive.  Great stuff to everyone involved!

Cheers - Dave


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Terrasync 3rd party util

2002-11-28 Thread David Luff
On 11/25/02 at 3:27 PM Tony Peden wrote:
>> OK, I'll give it a go.  I've a slight problem though in that I'm on
>> Linux/GeForce3 at home, and the nVidia drivers will only work if I do 
>> $/sbin/telinit 1
>> $root passwd
>> $make install in kernel and GLX nVidia directories
>> $edit XFConfig-4
>> $/sbin/telinit 2
>
>Odd, the X-server usually runs setuid root (it runs as root no matter
>who starts it) so permissions shouldn't be an issue.

Its not a permissions thing AFAICT, but an X tries to start but fails
thing.  To be quite honest I've sort of given up on fixing it properly
given that I'm about the upgrade the thing anyway.  I will be keeping the
graphics card though so I'm fingers crossed it works better next time :-)

Cheers - Dave

>
>> 
>> Unfortunately this leaves sound unworking, and I suspect probably net
>> access as well.  On a normal reboot X fails to start and I have to put
>the
>> old XFConfig-4 back.



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Terrasync 3rd party util

2002-11-28 Thread David Luff
On 11/25/02 at 10:11 AM Curtis L. Olson wrote:

>David Luff writes:
>> Is it likely to work over a 56K modem?
>
>David,
>
>First of all I will say that that I haven't tried it.  But, I
>encourage you to try it yourself since I want to know the answer
>too. :-)
>
>I suggest that you start out in the C172 and fly with that.  If you
>have good luck there, then you can try faster planes.
>
>I'm fortunate enough to have a DSL connection at home (they finally
>got service to my area) and with the latest tweaks to terrasync I've
>been able to sustain upwares of 2000 kts. with 32km visibility.
>(That's in the a4, time accelerated either 2x or 3x ...)
>
>So, if you are flying at 1/10 the speed, you might do just fine with
>1/10 the bandwidth.
>
>Let us know ... :-)
>

Well, it mostly worked.  After starting in an area with no scenery, it took
a couple of minutes waiting before the appropriate airport came down, and
FlightGear could be restarted properly.  Flying the C172, terrasync mostly
kept up, but in both my tests (one in the bay area, one in the relatively
sparser UK) managed to miss one tile.  I may be mistaken, but it appears to
download a whole 1x1 degree area at once in alphabetical order, and there
were times when nothing was coming down, so I think that if the order of
the tile download within a 1x1 chunk was optimised to get the closest
first, and if downloading was continued almost continuously based on
position and heading, then I'm quite sure it could be made to keep up no
problem.

Very impressive stuff anyway.

Cheers - Dave


___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel